builder
Skill1 starsChanged 3 months agoMITView on GitHub
Implement reviewed specifications as portable, accessible, source-controlled systems. Use for websites, applications, integrations, schemas, tests, migration work, and deployment packages that require acceptance checks, data boundaries, and rollback paths.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- inkatze/planwrighttheir own version, first seen Nov 4, 2026
- grimoire-rs/grimoiretheir own version, first seen Oct 27, 2026
- simota/agent-skillstheir own version, first seen Oct 23, 2026
- fredhead88/do-ittheir own version, first seen Oct 20, 2026
- soreavis/ai-docenttheir own version, first seen Oct 13, 2026
- SVerITG/Metistheir own version, first seen Oct 8, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- dralgorhythm/claude-agentic-framework★ 118same name
- simota/agent-skills★ 96same name
- grimoire-rs/grimoire★ 15same name
- inkatze/planwright★ 4same name
- SVerITG/Metis★ 4same name
- flywheel-product/ai-build-skills★ 2same name
- atgreen/hackinator★ 1same name
- SVerITG/Metis_PH★ 1same name
- fredhead88/do-it★ 0same name
- qmertesdorf/GameForge★ 0same name
1 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 repository5 other files it gives its agents.
- growerSkill
- maintainerSkill
- prototypeSkill
- sweeperSkill
- ux-ui-cx-market-intelligenceSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
Distinctive
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 8
Use this skill to turn an approved specification into maintainable implementation.
- Distinctive: line 19
Add automated checks proportionate to risk.
- Distinctive: line 20
Document dependencies, configuration, upgrade and rollback procedures, validation results, and known limitations.
- Distinctive: line 28
Do not store secrets in source, introduce hidden vendor lock-in, deploy data-bearing or risky changes without named approval, silently …
“Common” is measured: kept by at least 6 in 10 of the 10 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
Builder
Use this skill to turn an approved specification into maintainable implementation. Prefer portable standards, documented dependencies, minimal architecture, and explicit separation between public content, private data, and operational systems.
Intake
Require an approved specification, property role, acceptance criteria, security and data boundary, source and asset rights, deployment target, rollback path, reviewer, and public-claim review status. Do not build an unbounded system from an unreviewed ambition.
Workflow
- Inspect existing conventions, dependencies, and interfaces before adding new dependencies or abstractions.
- Choose the smallest portable architecture that meets the acceptance criteria and keeps ownership clear.
- Implement accessible semantics, descriptive media, responsive behavior, visible error states, and safe defaults.
- Add automated checks proportionate to risk. Test invalid input, error and recovery paths, permissions, link integrity, and build output—not only the happy path.
- Document dependencies, configuration, upgrade and rollback procedures, validation results, and known limitations.
Deliverable
Provide source-controlled implementation, validation evidence, dependency inventory, deployment instructions, rollback instructions, and a maintainer handoff. State the acceptance criteria met, residual risk, release owner, and reviewer.
Boundaries
Do not store secrets in source, introduce hidden vendor lock-in, deploy data-bearing or risky changes without named approval, silently change a property’s role or identity, or make unverified public claims.
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.