project-bootstrap
Skill0 starsChanged 50 days agoMITView on GitHub
Integrate this governance kit into an existing or new project while preserving its code, Git identity and authoritative documents.
40 other projects use a version of this.
Adopted by
Most recently taken up by
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 15, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 15, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 12, 2026
- NoobyGains/godmodetheir own version, first seen Nov 1, 2026
- jerseycheese/agent-skillstheir own version, first seen Oct 28, 2026
- alfonsusenrico/pakemtheir own version, first seen Oct 25, 2026
Used with
Projects with it also use delivery-planning, diagnose and 4 more.
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.
lzx-BillSkilldelivery-planning
Use when breaking work into tasks, planning milestones, mapping dependencies, sequencing implementation, or maintaining backlog and in-progress views. Trigger when user says "task breakdown", "milestone", "dependencies", "backlog", "sprint", "implementation plan", "delivery plan", or asks to "break this down into tasks". Coordinate with prompt-authoring for task-to-prompt mapping and with acceptance-design for task-to-acceptance mapping.
Also in 3 projects that use this
MicrosoftSkilldiagnose
Use to systematically diagnose why scenarios fail — identifies root causes by analyzing agent traces, codebase, and behavioral patterns
Also in 3 projects that use this
MicrosoftSkillapi-design
Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
- +1 more from google
Other versions40 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 40
- NoobyGains/godmode★ 120same name
- ice-lfernandes/claude-spring-architect★ 11same name
- nerviz-ai/nerviz★ 11same name
- Mozurok/fhorja.dev★ 10same name
- m16khb-org/issueops★ 6same name
- Eydenn/loomy★ 4same name
- fortmort/jeltz★ 4same name
- jerseycheese/agent-skills★ 4same name
- Cure-Consulting-Group/ProductEngineeringSkills★ 3same name
- hams-ollo/zen-agent-skills★ 2same name
30 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- api-contract-checkSkill
- bugfix-workflowSkill
- handoff-updateSkill
- issue-triageSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
1
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
Read the source kit's integration guide.
“Common” is measured: kept by at least 6 in 10 of the 32 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
project-bootstrap
Read the source kit's integration guide. Identify the user's actual target project independently of the directory used to download the source.
Inspect the target's existing instructions, changes and fact sources. Reuse equivalent documents through a mapping; generate only missing governance. Run the source script's read-only plan, inspect it, then apply within the user's existing authorization. Preserve business content, uncommitted work, history and remotes. Never fill target facts with the source kit's own status.
Populate requirements, assumptions and observed facts from the target's evidence. Run the local checker and an independent recovery exercise from the trial guide. Report measured outcomes and what remains untested. Ask only if a target or substantive conflict remains unresolved; do not introduce a confirmation round for routine additive changes already requested.
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.

