Open-source Claude Code project structure, README templates, and Agent Skills from SolveMotive.
Drop this into a repo so Claude (and other coding agents) get clear project context and reusable workflows instead of a giant prompt paste.
claude-project-kit/
├── templates/
│ ├── CLAUDE.md # short project instructions for Claude Code
│ ├── AGENTS.md # portable rules for any coding agent
│ ├── project-README.md # human-facing README skeleton
│ └── .claude/settings.json # optional Claude Code settings
├── skills/
│ ├── scaffold-claude-project/
│ ├── write-readme/
│ ├── pr-review/
│ ├── commit-message/
│ └── ship-checklist/
└── examples/web-app/ # filled-in example layout
| Piece | Role |
|---|---|
CLAUDE.md |
Always-on project facts for Claude Code |
AGENTS.md |
Shared rules across Claude Code and other coding agents |
skills/*/SKILL.md |
On-demand workflows (/skill-name) |
README template |
Human onboarding, not agent instructions |
From this kit’s root:
./scripts/install.sh /path/to/your-appOr copy manually:
cp templates/CLAUDE.md /path/to/your-app/CLAUDE.md
cp templates/AGENTS.md /path/to/your-app/AGENTS.md
mkdir -p /path/to/your-app/.claude/skills
cp -R skills/* /path/to/your-app/.claude/skills/Fill in the <!-- --> placeholders in CLAUDE.md, then start Claude Code:
claudeInvoke a skill:
/write-readme
/pr-review
/ship-checklist
mkdir -p ~/.claude/skills
cp -R skills/* ~/.claude/skills/Copy skills/scaffold-claude-project into the target repo, then run:
/scaffold-claude-project
| Skill | Use when |
|---|---|
scaffold-claude-project |
Setting up Claude Code layout in a repo |
write-readme |
Drafting or improving project documentation |
pr-review |
Reviewing a PR or local diff |
commit-message |
Writing a clear commit message from the diff |
ship-checklist |
Checking launch / deploy readiness |
Each skill is a folder with a SKILL.md (Agent Skills format). Compatible with Claude Code project skills under .claude/skills/.
your-app/
├── README.md # humans
├── CLAUDE.md # Claude Code project memory
├── AGENTS.md # shared agent rules
└── .claude/
├── settings.json
└── skills/
└── write-readme/
└── SKILL.md
Rule of thumb: facts in CLAUDE.md, procedures in skills. If a section of CLAUDE.md becomes a multi-step workflow, move it to a skill.
See examples/web-app for a filled Next.js-style layout.
- Short always-on context — keep
CLAUDE.mdlean - Progressive disclosure — load skill bodies only when needed
- Portable —
AGENTS.mdworks beyond Claude - Honest templates — placeholders over fake stack claims
- More skills (API design, migration notes, release notes)
- Claude Code plugin packaging
PRs welcome. Keep skills focused, descriptions trigger-rich, and SKILL.md bodies under ~500 lines.
MIT © SolveMotive