new-component
Skill0 starsChanged 2 months agoMITView on GitHub
Scaffold a new store.ts operation (function stub + test stub) from a name, then implement it. Tool-running — runs a script, then writes real code in a forked context.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- robritacca-dotcom/rift-dstheir own version, first seen Nov 1, 2026
- Crawford-Young/claude-configtheir own version, first seen Oct 25, 2026
- ricci-labs/twisetheir own version, first seen Oct 20, 2026
- violacase/Nuxt4-testtheir own version, first seen Oct 13, 2026
- fangyuting/skillstheir own version, first seen Oct 11, 2026
- mark2685/agent-toolstheir own version, first seen Jun 12, 2026
Used with
Projects with it also use new-page.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kkhh26864Skillnew-page
Vue 2 page creation specialist. Auto-triggers when user wants to: create new page, add page, build page, new vue page, create vue component page. Handles: page structure, routing, Vant components, Tailwind styling, mobile optimization. Works with Vue 2.6.11, Vant 2.13.2, Tailwind CSS, Vue Router.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- harunkurtdev/ros2-claude-code-template★ 214same name
- robritacca-dotcom/rift-ds★ 9same name
- kartikmanimuthu/agentfork★ 5same name
- fangyuting/skills★ 1same name
- Crawford-Young/claude-config★ 0same name
- mark2685/agent-tools★ 0same name
- ricci-labs/twise★ 0same name
- violacase/Nuxt4-test★ 0same 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 repository3 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- commit-msgSkill
- review-securitySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
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
- could be automatic: a setting could enforce it
- Very specific: line 14
Run node .claude/skills/new-component/scaffold.mjs $ARGUMENTS to print a starting stub.
- Very specific: line 15
Read src/store.ts and test/store.test.ts to match existing conventions (named exports, InvalidTaskError for bad input, an injectable clock …
- Very specific: line 17
Write the real implementation into src/store.ts and a real test into test/, replacing the TODOs from the stub.
- Very specific: line 19
Run npm test and report the result before finishing.
“Common” is measured: kept by at least 6 in 10 of the 7 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
/new-component
- Run
node .claude/skills/new-component/scaffold.mjs $ARGUMENTSto print a starting stub. - Read
src/store.tsandtest/store.test.tsto match existing conventions (named exports,InvalidTaskErrorfor bad input, an injectable clock for anything time-based). - Write the real implementation into
src/store.tsand a real test intotest/, replacing theTODOs from the stub. - Run
npm testand report the result before finishing.
Runs in a forked context so this exploration doesn't consume the parent session's context window — only the final diff and test result need to come back.
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.