frontend-implementation
Skill1 starsChanged 26 days agoMITView on GitHub
Inspect existing codebase conventions, framework, routing, and styling, and implement accessible, reusable UI components handling loading, empty, error, and success states without architectural rewrites.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- mae616/ai-templatetheir own version, first seen Aug 22, 2026
- Twigpine/openclaude-skillstheir own version, first seen May 14, 2026
- yiweiwan/skillstheir own version, first seen May 12, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Twigpine/openclaude-skills★ 19same name
- mae616/ai-template★ 9same name
- yiweiwan/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- rules/AGENTS.mdAGENTS.md
- accessibility-performance-auditSkill
- browser-visual-qaSkill
- design-system-extractionSkill
- visual-reconstructionSkill
- visual-refinement-loopSkill
- visual-regression-triageSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill when implementing UI components from visual reconstruction specs and design token maps, ensuring alignment with the host …
- Distinctive: line 15
State Completeness: Follow the Component State Matrix to implement default, loading, empty, error, and hover/focus states.
- Distinctive: line 23
Run the inspection script to identify active frameworks, TypeScript usage, and component paths:
- Very specific: line 29
Use semantic HTML tags (<nav>, <header>, <main>, <article>, <button>).
- Very specific: line 38
Focus Rings: Ensure interactive elements have visible high-contrast focus rings (focus-visible:ring-2).
- Very specific: line 41
Run existing linter or build commands (npm run lint, npm run build, npm test).
- Distinctive: line 42
Ensure no console syntax errors or hydration mismatches are introduced.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend Implementation Skill
Use this skill when implementing UI components from visual reconstruction specs and design token maps, ensuring alignment with the host codebase architecture.
Core Responsibilities
- Codebase Discovery: Inspect target frameworks and styling setup using inspect-codebase.js.
- Semantic & Accessible Markup: Implement semantic HTML with proper ARIA attributes, keyboard focus states, and color contrast.
- State Completeness: Follow the Component State Matrix to implement default, loading, empty, error, and hover/focus states.
- Architectural Respect: Adhere to the Framework Adaptation Guide to preserve existing project patterns.
Step-by-Step Procedure
1. Audit Existing Codebase Conventions
Run the inspection script to identify active frameworks, TypeScript usage, and component paths:
node skills/frontend-implementation/scripts/inspect-codebase.js [path-to-workspace]2. Implement Component Structure
- Use semantic HTML tags (
<nav>,<header>,<main>,<article>,<button>). - Apply design tokens or Tailwind utility classes extracted in
design-system-extraction. - Support responsive viewport constraints (mobile-first layout).
3. Handle Lifecycle States
Implement each state defined in state-matrix-template.md:
- Loading State: Provide skeleton placeholders or spinner indicators.
- Empty State: Show friendly fallback text and clear call-to-action when data arrays are empty.
- Error State: Render accessible error alert messages with retry actions.
- Focus Rings: Ensure interactive elements have visible high-contrast focus rings (
focus-visible:ring-2).
4. Verify Local Implementation
- Run existing linter or build commands (
npm run lint,npm run build,npm test). - Ensure no console syntax errors or hydration mismatches are introduced.
- Hand off to
browser-visual-qafor rendering verification.
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
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.