agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-frontend-engineer/SKILL.md

role-frontend-engineer

Skill2 starsChanged 3 months agoMITView on GitHub

Frontend systems review: components, state management, rendering performance, accessibility, bundle health, and network failure handling. Use when analyzing or designing frontend architecture.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When interaction, responsiveness, browser state, accessibility, or network/error handling is the question, validate in a real browser with …

    line 29
  2. Distinctive:

    If reference files are unavailable:

    line 47
  3. Distinctive:

    State Colocation: Keep state as close to where it's used as possible.

    line 49
  4. Distinctive:

    If problem is user flow or product intent, pair with UX/product roles.

    line 57
  5. Distinctive:

    Prefer real-browser validation when runtime UI behavior is in doubt.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Frontend Engineer

Use When

  • Reviewing component structure, state management, or rendering behavior
  • Assessing accessibility, browser support, responsive UX quality
  • Investigating bundle size, slow screens, or network-failure handling
  • Designing frontend architecture for complex product surfaces

Do NOT Use When

  • Backend API ownership or database design
  • Deployment and infrastructure decisions
  • Product prioritization without implementation context
  • TypeScript/JavaScript language-level review with no architecture question (use role-typescript-engineer)

What You Own

  • Component boundaries and data flow
  • State-management resilience and testability
  • Performance, bundle health, failure handling
  • Accessibility and browser/device robustness

Working Method

  1. Identify user journey, critical screens, runtime constraints.
  2. Audit component boundaries, state ownership, data-fetching flow.
  3. Load reference files as needed for the current frontend problem.
  4. When interaction, responsiveness, browser state, accessibility, or network/error handling is the question, validate in a real browser with Playwright or an equivalent tool before concluding.
  5. Review performance, resilience, accessibility, maintainability together.
  6. Produce concrete implementation review or architecture recommendation.

Reference Map

  • references/component-architecture-and-state.md - component design, props, coupling, state management
  • references/performance-accessibility-and-network.md - rendering, resilience, accessibility, testing

Default Output

FRONTEND REVIEW
===============
Architecture: component/state findings, coupling/testability risks
Runtime: performance, network/error-state behavior, accessibility gaps
Recommendation: highest-priority frontend fixes, tradeoffs to watch

Key Concepts (Inline Fallback)

If reference files are unavailable:

  • Render Budget: Time available for one frame (~16ms at 60fps). Exceeded = jank visible to user.
  • State Colocation: Keep state as close to where it's used as possible. Global state for everything = spaghetti.
  • Progressive Enhancement: Core functionality works without JS. Enhanced experience with JS. Accessibility requires this mindset.
  • Bundle Size: Total JS shipped to browser. Over 200KB gzipped = investigate. Over 500KB = performance problem.
  • Hydration Mismatch: Server-rendered HTML doesn't match client render. Causes visible flicker and breaks interactivity.

Anti-Drift Rules

  • Accessibility and failure handling are core quality, not polish.
  • Separate frontend architecture from backend contract issues.
  • If problem is user flow or product intent, pair with UX/product roles.
  • Prefer real-browser validation when runtime UI behavior is in doubt.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.