← all publishers

vannifr

@vannifr source repo

Report this profile Claim this profile

• 8 skills
• 0 followers
• 5 hours ago last updated

1. ▌
   Production Cwv Review · vannifr bundle

   Compares real-user field performance data (Chrome UX Report / CrUX, GA4 Web Vitals, Cloudflare Web Analytics, or any RUM tool already in place) against lab data (Lighthouse) to find where they diverge — a page can score well in Lighthouse and still be slow for real users. Works on any public website with enough traffic for CrUX (free, no setup required), or any site with its own RUM/analytics tool already wired in. Trigger on "check real Core Web Vitals", "how is this actually performing for users", "field vs lab performance", or as a sanity check after a Lighthouse-only performance pass. NOT a replacement for the Lighthouse/lab baseline (e.g. nfr-gap-audit's Phase 2) — this is a follow-up cross-check against it. NOT for setting up RUM/analytics from scratch — that's implementation work; flag the absence as a finding and hand it off. NOT for synthetic load/stress testing (use load-test-bootstrap).
   0 installs
2. ▌
   Responsive Visual Review · vannifr

   Baseline-free, Playwright-driven visual/layout review of a live or local website across breakpoints (mobile/tablet/desktop) — catches layout breaks, overflow, broken images, and inconsistent spacing without a hosted visual-regression service (Percy/Chromatic/Storybook) or an existing screenshot baseline. Works on any website, any stack. Trigger on "check responsiveness", "visual review", "does this look right on mobile", "review the layout across breakpoints", or before/after a CSS/template change that could shift layout. NOT for CRO/conversion/copy review (use landing-page-audit), new UI design work (use frontend-design), automated pixel-diff regression gating in CI (use Percy/Chromatic/Storybook-visual-regression skills, or the project's own Playwright toHaveScreenshot baseline if it has one), or accessibility/contrast auditing (use web-accessibility-essentials/axe).
   0 installs
3. ▌
   Third Party Script Audit · vannifr bundle

   Inventories every third-party script and resource a website loads (analytics, fonts, chat widgets, ads, embeds) and checks what each one can access, whether Subresource Integrity (SRI) is present and correct, and whether the site's CSP allowlist actually matches what's really loaded — no more, no less. Works on any website. Trigger on "audit third-party scripts", "what data are we leaking to vendors", "check SRI", "review our CSP allowlist", or before/after adding a new embedded widget or script. NOT a full penetration test or server-side dependency-vulnerability scan (use npm audit/pip-audit/a security-baseline skill for that — this is about what loads IN THE BROWSER from external origins, not server-side packages). NOT a standalone GDPR/consent-banner completeness check (pair with gdpr-test-patterns for the legal-basis/consent angle — this skill supplies the factual inventory a GDPR review needs, it doesn't make the legal judgment itself).
   0 installs
4. ▌
   Cross Browser Render Check · vannifr

   Systematic multi-engine (Chromium/Firefox/WebKit) rendering comparison for a website — catches browser-specific CSS/layout/JS bugs that a single-engine review misses. Works on any website, any stack. Trigger on "check cross-browser", "does this work in Safari/Firefox", "browser compatibility review", or before shipping a CSS/JS change that uses a newer or engine-specific feature. NOT for viewport/breakpoint layout review (use responsive-visual-review — same engine, different widths, a different axis entirely), NOT for functional/interaction E2E testing across browsers (use playwright-testing — this skill is visual/rendering-only, no click-throughs), NOT for designing a polyfill/feature-detection fix (flag the gap with a suspected cause, don't architect the remedy).
   0 installs
5. ▌
   Translation Quality Review · vannifr bundle

   Reviews actual translation quality across a multi-language site's locales — not whether every key exists (most i18n setups already automate that) but whether the translation itself is correct, natural, and consistent — literal phrasing, broken placeholders, untranslated leftovers, terminology drift, and length-driven layout risk. Works on any multi-language website, any i18n mechanism (client-side JSON, per-locale pages, CMS). Trigger on "review our translations", "check the French/German/Dutch copy", "is this correct in language X", or after updating locale content. NOT a substitute for a professional translator or native-speaker sign-off on launch-critical copy — flag uncertainty rather than assert fluency the model doesn't have. NOT a key-parity check — confirm the project's own parity check is green first; this assumes every key exists and asks whether the translation is any good.
   0 installs
6. ▌
   Nfr Gap Audit · vannifr bundle

   Use when running a systematic, self-directed skill-and-NFR audit on a website/web-app project — discovering skills from Tessl and VoltAgent, identifying non-functional-requirement gaps (performance, accessibility, security, SEO, testing, privacy, i18n, ...), and planning/implementing improvements in small, verified, committed phases. Trigger on "skill audit", "NFR audit", "audit this project for skills/gaps", "what skills am I missing", or before starting a multi-phase quality-improvement effort on a site.
   0 installs
7. ▌
   CI Local Parity · vannifr bundle

   Use when setting up or auditing a project's CI/CD pipeline together with local verification — ensures pnpm/npm verify (or equivalent) actually covers everything CI checks, adds pre-commit/pre-push git hooks that enforce this locally, and keeps trunk-based development honest (small commits, frequent pushes, CI checked per push not per batch). Load before building a new .woodpecker.yml/.github/workflows, before adding SonarQube/coverage, or when "it passed locally but failed in CI" comes up.
   0 installs
8. ▌
   Load Test Bootstrap · vannifr

   Scaffolds and runs a minimal, real load/stress test (k6 by default, Artillery as an alternative) against a site's or API's critical endpoints — the "performance budget test" that NFR checklists ask for but that a Lighthouse-only audit never actually exercises, since Lighthouse simulates exactly one user. Works on any HTTP-reachable site or API, static-front or backend. Trigger on "load test this", "how does this hold up under traffic", "stress test the API", "set up performance budget tests", or when an NFR audit flags load-testing as unverified. NOT for browser-rendering performance (Lighthouse/CWV — use nfr-gap-audit's baseline or production-cwv-review). NOT something to run against production without explicit, scoped authorization — generating real load against a live site has real cost and risk (rate limits, real infra bills, false alerts, genuine degradation for real visitors); always confirm target, intensity, and time window with the user first, and prefer a staging environment when one exists.
   0 installs