add-project-guide
Skill2 starsChanged 9 months agoMITView on GitHub
Create a new projects/ language-stack guide with templates
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-core-guideSkill
- bootstrapSkill
- evolveSkill
- refactor-docsSkill
- releaseSkill
- researchSkill
- setupSkill
- sync-skillsSkill
- update-readmeSkill
- verify-docsSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Create a new projects/{stack}/ directory with guide and templates for the language/stack specified in $ARGUMENTS.
- Very specific: line 20
Study existing project guide: Read the contents of one existing project directory (prefer projects/python/ or projects/typescript/) to …
- Distinctive: line 26
Follow the same structure as the reference guide
- Distinctive: line 29
Add cross-references to relevant core guides
- Very specific: line 33
Use <!-- CUSTOMIZE --> markers for project-specific values
- Distinctive: line 35
Follow the structure from the reference template
- Distinctive: line 40
All JSON must be valid — no comments, no trailing commas
≈ “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
Add Project Guide
Create a new projects/{stack}/ directory with guide and templates for the language/stack specified in $ARGUMENTS.
Steps
- Validate: Confirm
projects/$ARGUMENTS/does not already exist. If it does, report and stop. - Study existing project guide: Read the contents of one existing project directory (prefer
projects/python/orprojects/typescript/) to extract the pattern:guide.md— stack-specific tooling, conventions, common commands, tipsCLAUDE.md.template— project instructions template with<!-- CUSTOMIZE -->markerssettings.json.template— settings with stack-appropriate permissions and hooks
- Generate
projects/$ARGUMENTS/guide.md:- Follow the same structure as the reference guide
- Include stack-specific: package manager, test runner, linter, formatter, build tool
- Include common commands and conventions for the stack
- Add cross-references to relevant core guides
- Keep under 300 lines
- Generate
projects/$ARGUMENTS/CLAUDE.md.template:- Use
<!-- CUSTOMIZE -->markers for project-specific values - Include stack-appropriate sections: commands, code style, testing conventions
- Follow the structure from the reference template
- Use
- Generate
projects/$ARGUMENTS/settings.json.template:- Include stack-appropriate permission patterns (test, lint, format, build commands)
- Include appropriate hooks (format-on-save using the stack's formatter)
- All JSON must be valid — no comments, no trailing commas
- Verify: Re-read all generated files and confirm valid JSON, correct structure, under 300 lines each.
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.

