Claude Code Promts Skills
Production-ready prompt library for Claude coding agents. APEI methodology, ~35 specialist prompts, current Claude Code coverage, plus a /find-prompt skill that routes any task…
Install
/plugin marketplace add Rtur2003/Claude-Code-Promts-SkillsInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →Claude Code Prompts
Production-ready prompt library for Claude AI and coding agents, built on the APEI cycle: Analyze → Plan → Execute → Iterate.
Repository default is English-only and remains enforced to keep quality, tone, and contribution standards consistent across all prompts.
Start Here
- In Claude Code, run
/find-prompt <your task>— it routes any task to the exact prompt(s) to load. Or open REPOSITORY-MAP.md for manual navigation. - Use Agent System as the core prompt.
- Add specialist prompts by tier — 1 for a single-domain task (the default), 2 only when the task spans two genuinely independent domains, Multi-Agent Orchestration when units of work need isolation. See Composition Tiers.
- Validate outputs against explicit success criteria.
Six skills ship in .claude/skills/ — they load automatically when you run Claude Code from this repo:
| Skill | Use when | File |
|---|---|---|
/find-prompt |
Routing any task to the right prompt(s) — the main entry point | View |
deterministic-checks |
Before committing / opening a PR — zero-model-cost scan for conflict markers, live-looking credentials, debug leftovers, untracked TODOs, oversized files | View |
changelog-from-commits |
Cutting a release — Conventional Commits parsed into a categorized changelog | View |
doc-link-audit |
Before publishing docs — internal links, heading anchors, and orphan pages, GitHub-accurate slug matching | View |
skill-audit |
Reviewing a skills directory — frontmatter validity, description quality (SDO), body size, cross-scope name collisions | View |
capability-audit |
Evaluating a GitHub-hosted skill, plugin, MCP server, or agent toolkit before installation — read-only repository evidence without cloning | View |
These are operational skills rather than catalog-only examples: five include executable scripts, while /find-prompt is the routing layer. See Repository Structure below. This repo is also an installable plugin (.claude-plugin/plugin.json):
claude --plugin-dir /path/to/Claude-Code-Promts # try it for one session
claude plugin validate /path/to/Claude-Code-Promts/.claude-plugin/plugin.json
claude plugin validate /path/to/Claude-Code-Promts/.claude-plugin/marketplace.json
The repository also ships a marketplace manifest, so it can be installed without remembering a local --plugin-dir path:
/plugin marketplace add Rtur2003/Claude-Code-Promts-Skills
/plugin install claude-code-prompts@claude-code-prompts
Marketplace installation is intentionally left as a user action because it changes Claude Code's persistent plugin state.
Installing as a plugin additionally wires two deterministic safety hooks (block destructive commands, block writing live-looking credentials) — see Claude Code Plugins.
Top 5 Outcome Scenarios
Similar plugs
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…
Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.
Production-grade engineering skills for AI coding agents.
The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…