react-fsd-poc
Skill0 starsChanged 2 months agoMITView on GitHub
Build a React + TypeScript + FSD production-oriented POC.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decisionSkill
- developer-handoffSkill
- backendSkill
- component-designSkill
- databaseSkill
- devopsSkill
- prototypeSkill
- supabaseSkill
- testingSkill
- acceptance-criteriaSkill
- product-definitionSkill
- product-discoverySkill
- project-analysisSkill
- user-storySkill
- ux-flowSkill
- validationSkill
- security-reviewSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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
- Distinctive: line 10
Use when the task matches: react-fsd-poc, POC, React prototype.
- Distinctive: line 14
Create a reusable prototype with clear ownership for developer continuation.
- Distinctive: line 26
Use React and TypeScript strictly with FSD ownership.
- Distinctive: line 28
Stop for Product clarification on material business gaps.
- Distinctive: line 40
Keep Product validation and engineering verification distinct.
- Distinctive: line 41
Do not claim completion without evidence.
- Distinctive: line 46
Do not introduce Vue, Angular, Svelte, or multi-framework generators.
- Distinctive: line 47
Do not broad-refactor unrelated code.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
react-fsd-poc
When to use
Use when the task matches: react-fsd-poc, POC, React prototype.
Purpose
Create a reusable prototype with clear ownership for developer continuation.
Inputs
- Acceptance criteria
- UX flow
- Architecture Decision Record
- Change scope
Process
- Implement only inside ADR locations.
- Use React and TypeScript strictly with FSD ownership.
- Mark mocks and integration boundaries explicitly.
- Stop for Product clarification on material business gaps.
Outputs
- Runnable React POC
- Setup notes
- Mock inventory
- Implementation summary
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Forbidden: src/components business dumps, src/utils businessLogic, global dumping folders.
- Do not introduce Vue, Angular, Svelte, or multi-framework generators.
- Do not broad-refactor unrelated 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.