How do I install the Cs Frontend Review skill?

Run npx skillmds add nous-hermeshub/cs-frontend-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cs Frontend Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cs Frontend Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cs Frontend Review free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Cs Frontend Review?

nous-hermeshub (@nous-hermeshub) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cs Frontend Review by nous-hermeshub

Name: Cs Frontend Review
Rating: 4.666666666666667 (3 reviews)
Author: nous-hermeshub

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-prof...

nous-hermeshub 3aec59d 3.2 KB Updated Sep 8, 2026 1 repo stars

File contents

/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).

Primary device + network (desktop-fiber / mobile-4G / low-end Android / corporate)
LCP target on primary device (milliseconds)
Server Components vs SPA vs SSR vs SSG
JS bundle budget per route (KB gzipped)
SEO-dependent or auth-walled
Design-system location (Figma + tokens / ad-hoc Tailwind / headless UI)
WCAG target (AA / AAA / best-effort) + accessibility owner

Routing protocol

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.
Surface kill criteria — e.g., "SEO-dependent + SPA-only" trips. STOP and resolve.

Run the deterministic profile picker:

python engineering-team/skills/senior-frontend/scripts/frontend_decision_engine.py \
  --primary-device <mobile-4g|desktop-fiber|low-end-android|corporate-network> \
  --lcp-target-ms <N> --seo-dependent <true|false> \
  --auth-walled <true|false> --team-size <N>

Surface the matched profile + runner-up tradeoff (if within 15%).
Fork into specialists (one at a time, depth-first):
- a11y-audit for WCAG baseline (always)
- performance-profiler for CWV baseline + bundle audit
- epic-design only for astro-or-static marketing surfaces
- apple-hig-expert only for Apple-platform-native surfaces
- dependency-auditor before any major release
- cs-karpathy-reviewer before any commit

Output expectations (≤ 200-word digest)

Matched profile + reason
Three CWV targets (LCP, INP, CLS) at p75 on the primary device
Per-route JS bundle budget in KB-gzip
Named a11y owner
List of specialists invoked + artifact paths
Recommended next sub-skill

Anti-patterns

❌ Recommending Next App Router as a universal default. Device + SEO + auth decide rendering.
❌ Setting "fast" as a target. Pick a number in ms.
❌ Skipping a11y-audit on customer-facing surface.
❌ Reimplementing perf-profiling logic. Fork into performance-profiler.

Customization

Profiles live at engineering-team/skills/senior-frontend/profiles/. Four built-in: next-app-router, remix-or-sveltekit, vite-spa, astro-or-static. Copy one to <your-org>.json and adjust to add your org's defaults.

Related commands

/cs:fullstack-review — full-stack lens (parent)
/cs:backend-review — for API contract on the consumer side
/cs:engineer-grill — cross-role 21-question grill
/karpathy-check — Karpathy 4-principle review

---name: cs-frontend-reviewdescription: 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-prof...license: MIT---# /cs:frontend-review — Frontend engineering reviewUse the `cs-frontend-engineer` agent (uses `context: fork`) to handle this inquiry:**$ARGUMENTS**## Forcing-question libraryCanonical 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 SSG4. JS bundle budget per route (KB gzipped)5. SEO-dependent or auth-walled6. Design-system location (Figma + tokens / ad-hoc Tailwind / headless UI)7. WCAG target (AA / AAA / best-effort) + accessibility owner## Routing protocol1. **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.3. **Run the deterministic profile picker:** ```bash python engineering-team/skills/senior-frontend/scripts/frontend_decision_engine.py \ --primary-device <mobile-4g|desktop-fiber|low-end-android|corporate-network> \ --lcp-target-ms <N> --seo-dependent <true|false> \ --auth-walled <true|false> --team-size <N> ```4. **Surface the matched profile + runner-up tradeoff** (if within 15%).5. **Fork into specialists** (one at a time, depth-first): - `a11y-audit` for WCAG baseline (always) - `performance-profiler` for CWV baseline + bundle audit - `epic-design` only for `astro-or-static` marketing surfaces - `apple-hig-expert` only for Apple-platform-native surfaces - `dependency-auditor` before any major release - `cs-karpathy-reviewer` before any commit## Output expectations (≤ 200-word digest)- Matched profile + reason- Three CWV targets (LCP, INP, CLS) at p75 on the primary device- Per-route JS bundle budget in KB-gzip- Named a11y owner- List of specialists invoked + artifact paths- Recommended next sub-skill## Anti-patterns- ❌ Recommending Next App Router as a universal default. Device + SEO + auth decide rendering.- ❌ Setting "fast" as a target. Pick a number in ms.- ❌ Skipping `a11y-audit` on customer-facing surface.- ❌ Reimplementing perf-profiling logic. Fork into `performance-profiler`.## CustomizationProfiles live at `engineering-team/skills/senior-frontend/profiles/`. Four built-in: `next-app-router`, `remix-or-sveltekit`, `vite-spa`, `astro-or-static`. Copy one to `<your-org>.json` and adjust to add your org's defaults.## Related commands- `/cs:fullstack-review` — full-stack lens (parent)- `/cs:backend-review` — for API contract on the consumer side- `/cs:engineer-grill` — cross-role 21-question grill- `/karpathy-check` — Karpathy 4-principle review

Frequently asked questions