agentleFS
mikeparcewskimikeparcewski/wicked-garden/skills/engineering/frontend/SKILL.md

wicked-garden-engineering-frontend

Skill9 starsChanged 7 months agoMITView on GitHub

Frontend engineering specialist for React, CSS, browser APIs, component design, accessibility, and performance. This skill should be used when the user asks about UI implementation, component review, or frontend-specific questions.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use comprehensive checklists for:

    line 66
  2. Distinctive:

    Use semantic HTML before reaching for ARIA

    line 89
  3. Distinctive:

    Test with keyboard navigation and screen readers

    line 90

≈ “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 Skill

Specialized frontend engineering guidance for React, CSS, and browser-based applications.

When to Use

  • Building React components
  • CSS and styling questions
  • Browser API usage
  • Frontend performance optimization
  • Accessibility (a11y) guidance
  • User says "frontend", "React", "CSS", "component", "UI"

Key Focus Areas

React Patterns

  • Component composition and single responsibility
  • Hook usage (useState, useEffect, custom hooks)
  • State management (context, props, lifting state)
  • Performance (memo, useMemo, useCallback)
  • Error boundaries

CSS & Styling

  • Responsive design (flexbox, grid, media queries)
  • Modern CSS (custom properties, container queries)
  • Animations (GPU-accelerated)
  • Theming and design systems

Browser APIs

  • Fetch API and async operations
  • Local/Session Storage
  • Event handling
  • Performance API

Accessibility

  • Semantic HTML elements
  • ARIA labels and roles
  • Keyboard navigation
  • Screen reader compatibility
  • WCAG color contrast

Performance

  • Code splitting and lazy loading
  • Bundle optimization
  • Image optimization
  • Virtual scrolling
  • Debouncing and throttling

Review Process

Use comprehensive checklists for:

  • Component quality (responsibility, props, composition)
  • React best practices (hooks, effects, state)
  • Styling (responsiveness, consistency)
  • Accessibility (semantic HTML, keyboard nav, ARIA)

See refs/checklists.md for detailed checklists, anti-patterns, and output templates.

Code Patterns

Common React and CSS patterns for:

  • Component structure with TypeScript
  • Custom hooks (debounce, etc.)
  • Responsive design
  • Accessibility patterns
  • Performance optimization

See refs/patterns.md for code examples and best practices.

Notes

  • Prioritize accessibility from the start
  • Mobile-first responsive design
  • Use semantic HTML before reaching for ARIA
  • Test with keyboard navigation and screen readers

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.