Claude-Code-Promts-Skills
AGENTS.md53 starsChanged 52 days agoMITView on GitHub
.claude/skills/find-prompt/SKILL.md is the canonical routing table. .agents/skills/find-prompt/SKILL.md is a thin cross-agent adapter. Keep the canonical table, indexes, llms.txt, and eval cases in sync whenever a prompt is added, removed, or renamed. The library covers the current Claude Code / Claude ecosystem. Keep these accurate against code.claude.com/docs and platform.claude.com/docs: Every prompt follows this template:
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- capability-auditSkill
- changelog-from-commitsSkill
- deterministic-checksSkill
- doc-link-auditSkill
- find-promptSkill
- skill-auditSkill
- capability-auditSkill
- changelog-from-commitsSkill
- deterministic-checksSkill
- doc-link-auditSkill
- find-promptSkill
- skill-auditSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
25 rules. About 0 are common, 11 are distinctive, and 14 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 81
Every prompt follows this template:
- Very specific: line 110
Use # for title, ## for major sections, ### for subsections
- Distinctive: line 116
Keep prompts concise — include token count in catalog tables
- Very specific: line 117
Use ⭐ emoji only for recommended/primary prompts in catalogs
- Very specific: line 121
No build system for the prompts themselves.
- Very specific: line 138
Create prompts/english/agents/your-topic-prompt.md using the template above.
- Very specific: line 139
Update prompts/english/agents/INDEX.md — the task router and the catalog table (with a ~token estimate)
- Very specific: line 140
Update prompts/english/INDEX.md task router
- Very specific: line 141
Add a row to .claude/skills/find-prompt/SKILL.md and a routing eval case
- Distinctive: line 142
Add entry to the portfolio table and, if it is a recurring pairing, the Common Combinations table in README.md
- Very specific: line 143
Add a line to llms.txt and REPOSITORY-MAP.md
- Distinctive: line 148
Add entry to the Foundation & Project Prompts table in README.md
- Distinctive: line 149
Add relevant combinations to the Common Combinations table in README.md
- Very specific: line 152
Create a new file in prompts/english/examples/
- Distinctive: line 157
Ensure all relative links still resolve
- Very specific: line 158
Keep CHANGELOG.md updated for notable changes
- Very specific: line 163
Add archive rationale in prompts/english/agents/archive/INDEX.md
- Very specific: line 164
Update active catalogs (README.md, prompts/english/agents/INDEX.md, prompts/english/INDEX.md)
- Distinctive: line 190
Don't add non-English content — this repo is English only
- Distinctive: line 192
Don't deviate from the APEI methodology in prompt design
- Distinctive: line 193
Don't remove the Remember section from prompts
- Distinctive: line 194
Don't use absolute URLs for internal links — use relative paths
- Very specific: line 195
Don't cite Claude Code features, commands, or model IDs from memory — verify against code.claude.com/docs / platform.claude.com/docs
- Very specific: line 196
Don't reference retired models (claude-3-*, claude-opus-4-1, claude-sonnet-4-0, gpt-4o) as current
- Distinctive: line 197
Don't add filler or AI-cliché phrasing.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md
Project Overview
- Name: Claude Code Prompts
- Type: Prompt library (Markdown-first) plus tested scripts bundled as Claude Code and cross-agent skills (
.claude/skills/,.agents/skills/) and safety hooks - Purpose: Production-ready system prompts for Claude Code, with cross-agent discovery through
AGENTS.md,.agents/skills/, andllms.txt - Core Methodology: APEI cycle — Analyze → Plan → Execute → Iterate
- License: MIT
- Language: English only
Routing skill
.claude/skills/find-prompt/SKILL.md is the canonical routing table. .agents/skills/find-prompt/SKILL.md is a thin cross-agent adapter. Keep the canonical table, indexes, llms.txt, and eval cases in sync whenever a prompt is added, removed, or renamed.
Repository Structure
├── AGENTS.md # This file — project memory
├── README.md # Main catalog, portfolio table, common combinations
├── REPOSITORY-MAP.md # 30-second orientation, task -> file lookup
├── QUICK-START.md # 30-second setup guide
├── USAGE.md # Scenario-based prompt composition
├── CONTRIBUTING.md # Contribution guidelines
├── CHANGELOG.md # Version history (current: 2.2.0)
├── llms.txt # Full LLM router index
├── .claude-plugin/
│ ├── plugin.json # Claude Code plugin manifest
│ └── marketplace.json # Installable marketplace catalog
├── hooks/
│ ├── hooks.json # PreToolUse wiring
│ └── scripts/ # block-destructive-commands.sh, block-secret-writes.sh
├── .claude/skills/ # 6 Claude Code skills
│ ├── find-prompt/
│ ├── deterministic-checks/
│ ├── changelog-from-commits/
│ ├── doc-link-audit/
│ ├── skill-audit/
│ └── capability-audit/
├── .agents/skills/ # Cross-agent adapters / mirrored deterministic skills
├── evals/ # find-prompt routing-accuracy regression tests (static + live tiers)
├── .github/workflows/
│ └── quality-gate.yml # CI: lint, link audit, skill audit, deterministic-checks, plugin validate, routing eval
└── prompts/
└── english/
├── INDEX.md # Global task -> file router
├── agents/ # Active agent prompts + compatibility stubs
│ ├── INDEX.md # catalog with token counts + task router
│ └── archive/ # Archived prompts removed from active catalog
├── base/ # Foundation prompt (universal best practices)
├── project-types/ # Domain-specific prompts (11 files)
├── examples/ # Real-world usage examples
└── workflows/ # Model selection, native features, Agent SDK,
└── INDEX.md # APEI, selection, troubleshooting, setup, maintenanceClaude Code operation prompts (agents/)
The library covers the current Claude Code / Claude ecosystem. Keep these accurate against code.claude.com/docs and platform.claude.com/docs:
agent-skills-prompt.md— SKILL.md authoringmcp-integration-prompt.md— MCP servers, scopes, auth, injection safetyclaude-code-plugins-prompt.md— plugin.json, marketplacesmulti-agent-orchestration-prompt.md— native subagents + dynamic workflowshooks-automation-prompt.md— hook events and settings.json schemaclaude-code-workflow-prompt.md— CLAUDE.md, rules, settings, permissionsclaude-code-modes-prompt.md— adaptive thinking, effort, plan modeworkflows/model-selection-guide.md— model lineup and effortworkflows/claude-code-native-features-guide.md— the current feature surfaceworkflows/agent-sdk-guide.md— the Claude Agent SDK
File Naming Conventions
| Type | Format | Example |
| Prompts | kebab-case-prompt.md | code-review-prompt.md |
| Guides | kebab-case-guide.md | iterative-development-guide.md |
| Index files | INDEX.md | INDEX.md |
Prompt Structure Standards
Every prompt follows this template:
# Prompt Title
> **Key Feature 1** | **Key Feature 2** | **Key Feature 3**
## Role
[Define what this prompt does]
## Protocol / Core Loop
[Main workflow — often uses a protocol acronym]
## Phases
[Phase details with templates and checklists]
## Remember
[Key takeaways — always the final section]Key elements:
- Protocol acronym: Each prompt defines a memorable acronym for its core loop
- Phases: Detailed steps with Markdown templates and
- [ ]checklists - Tables: Used for options, comparisons, and structured data
- Code blocks: Used for command examples, templates, and diagrams
- Remember section: Closing callout with priority rules (always last)
Markdown Style Guide
- Use
#for title,##for major sections,###for subsections - Tables for structured data (catalogs, options, comparisons)
> **bold text**for callout/subtitle lines under the title- Fenced code blocks with language tags where applicable
- [ ]checklists inside phases---horizontal rules to separate major sections- Keep prompts concise — include token count in catalog tables
- Use
⭐emoji only for recommended/primary prompts in catalogs
Build & Development
No build system for the prompts themselves. The bundled skill/hook scripts under .claude/skills/*/scripts/ and hooks/scripts/ are standalone (bash/Python, no install step, no dependency beyond what's noted in each SKILL.md).
- Install:
git clonethe repo, orclaude --plugin-dir <path>to try it as a plugin - Validate links:
python3 .claude/skills/doc-link-audit/scripts/check_links.py .— real link/anchor checker, not a grep spot-check - Validate formatting: Open
.mdfiles in a Markdown previewer - Lint:
npx markdownlint-cli2 '**/*.md' - Pre-commit scan:
bash .claude/skills/deterministic-checks/scripts/scan.sh . - Skill quality check:
python3 .claude/skills/skill-audit/scripts/audit.py .claude/skills - Plugin checks:
claude plugin validate .claude-plugin/plugin.jsonandclaude plugin validate .claude-plugin/marketplace.json
Bundled skills and scripts
.claude/skills/ ships 6 skills: find-prompt, 4 deterministic repository checks, and capability-audit. .agents/skills/ exposes the library to other agent hosts without maintaining a second routing table. hooks/ ships 2 PreToolUse safety scripts. Keep the catalogs, adapters, routing cases, and scripts synchronized; test scripts against real input before documenting them as working.
Common Tasks
Add a new agent prompt
- Create
prompts/english/agents/your-topic-prompt.mdusing the template above; open with a "Use this when" line and a "Skip to" anchor list - Update
prompts/english/agents/INDEX.md— the task router and the catalog table (with a ~token estimate) - Update
prompts/english/INDEX.mdtask router - Add a row to
.claude/skills/find-prompt/SKILL.mdand a routing eval case - Add entry to the portfolio table and, if it is a recurring pairing, the Common Combinations table in
README.md - Add a line to
llms.txtandREPOSITORY-MAP.md
Add a new project-type prompt
- Create
prompts/english/project-types/your-domain-prompt.md - Update
prompts/english/INDEX.md - Add entry to the Foundation & Project Prompts table in
README.md - Add relevant combinations to the Common Combinations table in
README.md
Add a usage example
- Create a new file in
prompts/english/examples/ - Show real-world prompt usage with context and expected output
Update documentation
- Edit the relevant
.mdfile - Ensure all relative links still resolve
- Keep
CHANGELOG.mdupdated for notable changes
Archive overlapping prompts
- Classify prompt as keep / merge / archive
- Move archived prompt to
prompts/english/agents/archive/ - Add archive rationale in
prompts/english/agents/archive/INDEX.md - Update active catalogs (
README.md,prompts/english/agents/INDEX.md,prompts/english/INDEX.md)
Quality Checklist
Before submitting changes:
- Content is accurate and follows best practices
- Markdown renders correctly (check headers, tables, code blocks)
- No spelling or grammar errors
- INDEX files updated if adding/removing prompts
- All relative links resolve to existing files
- Follows existing naming conventions (
kebab-case-prompt.md) - New prompts include Role, Protocol, Phases, and Remember sections
- README.md catalog tables updated if adding new prompts
- Recommendations are concrete (no vague advice)
Commit Messages
feat: add security audit prompt # New features
fix: correct typo in API prompt # Fixes
docs: improve README examples # Documentation
update: enhance code review checklist # UpdatesThings to Avoid
- Don't add non-English content — this repo is English only
- Don't add code beyond the bundled skill/hook scripts (
.claude/skills/*/scripts/,hooks/scripts/) — the prompt content itself stays pure Markdown; a script added there must ship inside a skill with aSKILL.mddocumenting it, be dependency-free or note its dependency explicitly, and be tested against real input before being documented as working - Don't deviate from the APEI methodology in prompt design
- Don't remove the Remember section from prompts
- Don't use absolute URLs for internal links — use relative paths
- Don't cite Claude Code features, commands, or model IDs from memory — verify against
code.claude.com/docs/platform.claude.com/docs - Don't reference retired models (
claude-3-*,claude-opus-4-1,claude-sonnet-4-0,gpt-4o) as current - Don't add filler or AI-cliché phrasing; every sentence carries information
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.

