Command
/cs-frontend-review
Frontend engineering review — walks the 7 Matt Pocock forcing questions (device, LCP target, rendering, bundle budget, SEO vs auth, design system, WCAG), picks the framework + rendering profile, forks into specialists (a11y-audit, performance-profiler, epic-design). Invokes the
One command from claude-skills.
shell
$ npx -y skills add alirezarezvani/claude-skills --agent claude-codeShips with claude-skills. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/cs-frontend-review
Context preview
What this command does when you run it.
Frontend engineering review — walks the 7 Matt Pocock forcing questions (device, LCP target, rendering, bundle budget, SEO vs auth, design system, WCAG), picks the framework + rendering profile, forks into specialists (a11y-audit, performance-profiler, epic-design). Invokes the
Stats
Stars23,056
Forks3,139
LanguagePython
LicenseMIT
Ships with claude-skills
Command definition
cs-frontend-review.md
--- description: Frontend engineering review — walks the 7 Matt Pocock forcing questions (device, LCP target, rendering, bundle budget, SEO vs auth, design system, WCAG), picks the framework + rendering profile, forks into specialists (a11y-audit, performance-profiler, epic-design). Invokes the cs-frontend-engineer agent with context fork. argument-hint: "<problem or surface to review>" --- # /cs:frontend-review — Frontend engineering review Use the `cs-frontend-engineer` agent (uses `context: fork`) to handle this inquiry: **$ARGUMENTS** ## Forcing-question library Canonical source: `engineering-team/skills/senior-frontend/references/forcing_questions.md` (7 questions, one-per-turn, recommendation + canon citation per question). 1. Primary device + network (desktop-fiber / mobile-4G / low-end Android / corporate) 2. LCP target on primary device (milliseconds) 3. Server Components vs SPA vs SSR vs SSG 4. JS bundle budget per route (KB gzipped) 5. SEO-dependent or auth-walled 6. Design-system location (Figma + tokens / ad-hoc Tailwind / headless UI) 7. WCAG target (AA / AAA / best-effort) + accessibility owner ## Routing protocol 1. **Walk the 7 forcing questions** in `engineering-team/skills/senior-frontend/references/forcing_questions.md`. One per turn. Recommend with cited canon. Track in `/tmp/frontend-grill-<date>.md`. 2. **Surface kill criteria** — e.g., "SEO-dependent + SPA-only" trips. STOP and resolve.
