frontend-development
Skill131 starsChanged 6 months agoMITView on GitHub
Required context for all frontend work. Loads frontend standards (conventions, React Query patterns, adapter testing requirements) before any code changes. Use when modifying anything under components/frontend/. Triggers on: any frontend code change, UI component work, React Query hooks, API adapter work, frontend bug fix, frontend refactor.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- lubusIN/frappe-skillstheir own version, first seen Nov 4, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- liushikuan63/Qoder-Optimizationtheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- taichuy/1flowbasetheir own version, first seen Oct 23, 2026
- typv/nest-turbo-startertheir own version, first seen Oct 8, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- All-Hands-AI/OpenHands★ 93ksame name
- OpenHands/OpenHands★ 93ksame name
- taichuy/1flowbase★ 292same name
- typv/nest-turbo-starter★ 224same name
- avibebuilder/claude-prime★ 119same name
- lubusIN/frappe-skills★ 68same name
- aws-solutions/konductor★ 11same name
- Ampli-Group/agentic-mobile-blueprint★ 4same name
- liushikuan63/Qoder-Optimization★ 2same name
- dhslegen/digital-delivery-team★ 1same name
3 more not listed
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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- alignSkill
- amber-reviewSkill
- workflowSkill
- ambient-pr-testSkill
- ambientSkill
- dev-clusterSkill
- deploySkill
- devflowSkill
- discoverSkill
- cypress-demoSkill
- grpc-devSkill
- unleash-flagSkill
- memorySkill
- pr-fixerSkill
- scaffoldSkill
- ambient-api-serverSkill
- specSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before writing or changing any frontend code, load the project's frontend standards.
- Very specific: line 24
Read all files in specs/standards/frontend/ before proceeding:
- Very specific: line 43
Zero
anytypes: Use proper types or unknown. - Distinctive: line 44
Shadcn UI components only: No custom buttons, inputs, dialogs.
- Very specific: line 45
React Query for all data fetching: No manual fetch() in components.
- Very specific: line 46
typeoverinterface: Always. - Distinctive: line 47
All adapters must be tested: No adapter merged without unit tests using recorded responses.
“Common” is measured: kept by at least 6 in 10 of the 11 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 Development
Before writing or changing any frontend code, load the project's frontend standards. These are non-negotiable constraints — not suggestions.
User Input
$ARGUMENTSRequired Reading
Read all files in specs/standards/frontend/ before proceeding:
ls specs/standards/frontend/At minimum, this includes:
specs/standards/frontend/conventions.spec.md— zero-tolerance rules (noany, Shadcn only, React Query for all data,typeoverinterface, colocated components, feature flags)specs/standards/frontend/react-query.spec.md— file structure (ports/adapters/queries), data fetching patterns, testing requirements, validation checklist
Also read the API adapter spec if working on the services layer:
specs/frontend/api-adapter.spec.md— port interface contract, canonical types, 30 API domains, testability requirements
Key Constraints
These apply to every frontend change, no exceptions:
- Zero
anytypes. Use proper types orunknown. - Shadcn UI components only. No custom buttons, inputs, dialogs.
- React Query for all data fetching. No manual
fetch()in components. typeoverinterface. Always.- All adapters must be tested. No adapter merged without unit tests using recorded responses.
- All hooks must be tested. Hook tests use mock adapters, not real backends.
- Port interfaces, not raw API calls. React Query hooks consume ports, not
services/api/directly.
After Reading
Confirm you have loaded the standards, then proceed with the task. If any of your changes would violate these constraints, stop and discuss with the user before writing code.
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.