create-project-instructions
Skill12 starsChanged 4 months agoMITView on GitHub
Create project-context AGENTS.md files using phased discovery, required operational sections, and session-state modeling.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- LuisUrrutia/skillstheir own version, first seen Oct 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- LuisUrrutia/skills★ 2same 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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-agents-mdSkill
- create-checkpointSkill
- create-skillSkill
- create-usercontext-instructionsSkill
- repository-drift-controlSkill
- restore-checkpointSkill
- validate-agents-mdSkill
- validate-project-instructionsSkill
- validate-skillSkill
- validate-usercontext-instructionsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use this skill when the task is to create or regenerate project-context AGENTS.md.
- Very specific: line 18
Use this skill when project context must include role/phase/style defaults.
- Distinctive: line 19
Do not use this skill for user-context instruction generation.
- Very specific: line 28
Run phased discovery using references/discovery-phases.md.
- Distinctive: line 56
Keep recommendations tied to project scope.
- Distinctive: line 57
Avoid placeholders in final command examples unless explicitly unresolved.
- Distinctive: line 58
Use relative paths for references.
- Distinctive: line 59
Do not introduce provider-specific assumptions.
≈ “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
Create Project Context AGENTS
Purpose
Generate project-context AGENTS.md files with required sections, role definitions, command namespace controls, and validation-ready structure.
When To Use
- Use this skill when the task is to create or regenerate project-context
AGENTS.md. - Use this skill when project context must include role/phase/style defaults.
- Do not use this skill for user-context instruction generation.
Required Inputs
- Project name, description, and current phase.
- Tech stack, architecture, and repository structure.
- Roles, default session state, and command namespace.
- Objectives, testing strategy, and documentation standards.
Workflow
- Run phased discovery using
references/discovery-phases.md. - Apply required output schema from
references/output-schema.md. - Build command and role structures using:
references/command-template.mdreferences/role-template.md
- Apply artifact/summary contract from
references/output-format.md. - Stamp
<!-- spec_version: 1.5.0 -->as an HTML comment at the top of the generatedAGENTS.md. - Validate completeness using
references/quality-checklist.mdbefore final output.
Output Expectations
- One complete
AGENTS.mdfile with all required project-context sections. - Session-state and command-reference elements are fully populated.
- Core project-context required-section completeness is enforced through AGENTS structure.
- Role definitions and examples are project-specific and actionable.
- Output remains provider-neutral.
- Output contract and summary format follow
references/output-format.md.
Resources
- Discovery workflow:
references/discovery-phases.md - Output schema:
references/output-schema.md - Command template:
references/command-template.md - Role templates:
references/role-template.md - Output contract:
references/output-format.md - Quality checklist:
references/quality-checklist.md - Structure baseline:
../../templates/AGENTS_template.md - Example reference:
../../AGENTS.md
Constraints And Safety
- Keep recommendations tied to project scope.
- Avoid placeholders in final command examples unless explicitly unresolved.
- Use relative paths for references.
- Do not introduce provider-specific assumptions.
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.