component-managing-state
Skill1 starsChanged 19 days agoNo licenceView on GitHub
Use whenever designing, implementing, modifying, reviewing, or refactoring component-based UI development (React, Vue, Angular, Svelte, SolidJS, Astro, Flutter widgets, SwiftUI views, etc.). Guides decisions about state ownership, lifting state up, avoiding prop drilling, passing children and slots, Containment and Specialization.
In this repository14 other files it gives its agents.
- agentic-tddSkill
- engineering-cost-reviewSkill
- frontend-layered-architectureSkill
- git-worktreesSkill
- orca-handoffSkill
- shhSkill
- think-before-codingSkill
- tidy-testsSkill
- business-logic-in-componentsSkill
- good-testsSkill
- you-dont-need-react-custom-hooksSkill
- genuine-questionSkill
- jdiSkill
- to-ideaSkill
The file
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.