Claude-Code-Promts-Skills

skill
Security Audit
Warn
Health Pass
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 47 GitHub stars
Code Warn
  • Code scan incomplete — No supported source files were scanned during light audit
Permissions Pass
  • Permissions — No dangerous permissions requested
Purpose
This project is a curated collection of high-quality system prompt templates and workflows designed specifically for Claude AI. It provides structured instructions covering coding, debugging, security audits, and general problem-solving to enhance AI agent capabilities.

Security Assessment
Overall risk: Low. This tool is a repository of Markdown files and prompt templates rather than executable code or a functional MCP server. It does not request dangerous permissions, execute shell commands, or make external network requests. There is no application code to analyze, which explains the incomplete code scan, but the absence of executable files means there is virtually no risk of hardcoded secrets or malicious background activity.

Quality Assessment
The project is of high quality and actively maintained, with recent updates pushed within the last day. It benefits from a permissive MIT license, allowing for free use and modification. With 30 GitHub stars, it demonstrates a growing level of community trust. The documentation is excellent, providing a well-organized catalog of templates that categorize prompts clearly by use case and token size.

Verdict
Safe to use: an excellent, transparent resource for developers looking to enhance their AI coding workflows.
SUMMARY

A curated collection of high-quality prompt templates designed for Claude, focused on coding, problem-solving, productivity, and advanced reasoning workflows.

README.md

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

  1. Open REPOSITORY-MAP.md for one-file navigation.
  2. Use Agent System as the core prompt.
  3. Add one specialist prompt only when the task clearly needs it.
  4. Validate outputs against explicit success criteria.

Top 5 Outcome Scenarios

Scenario Prompt Setup
General autonomous coding Agent System
Debugging production issues Agent System + Debugging & Troubleshooting
Security-sensitive changes Agent System + Security Audit
Architecture decisions Agent System + Architecture Patterns
Complex multi-agent execution Agent System + Multi-Agent Orchestration

One Decision Tree + Token Budget

Use the single-source selector here: Prompt Selector Guide.

Rule: start minimal, then add exactly one specialist only if quality gates fail.


Active Agent Portfolio (Outcome-First)

claude-agent-system-prompt.md is the operational source of truth.

Prompt Use when Do not use when File
Agent System ⭐ Any autonomous task You only need a tiny cheat sheet View
Quick Reference Token budget is extremely tight You need deep specialist logic View
Code Review Reviewing a PR/change set Writing new feature code from scratch View
Security Audit Threat/risk exposure is possible Task has no security relevance View
Refactoring Improving maintainability safely Incident response under active outage View
Testing Building or fixing test strategy You only need non-test docs View
Documentation Producing technical docs You need runtime diagnosis View
Performance Latency/throughput/cost bottlenecks Problem is primarily correctness View
Git & VCS Workflow, branching, commit hygiene App logic decisions View
Accessibility Audit WCAG and accessibility compliance Backend-only infrastructure change View
Migration & Upgrade Framework/runtime/DB migrations Greenfield implementation View
Monitoring & Observability Logs, metrics, traces, alerts Pure UI copy/content task View
Debugging & Troubleshooting Root-cause and incident diagnostics You are designing architecture from zero View
Claude Code Modes ⭐ Managing /think and planning depth Non-Claude environments only View
Claude Code Workflow CLAUDE.md, hooks, permissions, MCP You only need algorithm design View
Technology Stack ⭐ Selecting tools/libraries Stack is fixed and approved View
Architecture Patterns System design and trade-offs Small local bug fix View
Full-Stack Development End-to-end app delivery Single-layer scoped work View
AI & LLM Integration RAG/agents/model integration No AI component exists View
API Design & GraphQL API contract/schema design UI-only styling task View
Cloud & Infrastructure IaC/K8s/multi-region/cost Local script-only changes View
Data Engineering Pipelines/streaming/data quality CRUD app without data platform scope View
Compliance & Governance Regulated/security governance scope Prototype with no compliance requirements View
Multi-Agent Orchestration Parallel agent coordination Single-agent linear task View
Monorepo & Complex Projects Multi-package cross-cutting work Small standalone repository View
Error Handling & Resilience Fault tolerance and degradation Static content editing only View
Developer Experience & Tooling Linting/hooks/onboarding/DX Feature logic changes only View
Database Design & Optimization Schema/index/query tuning No persistent data layer exists View
UI/UX & Design Systems Design tokens/components/theming API/backend-only task View

Archived (Merged) Prompts

These were removed from the active catalog to reduce overlap:

  • Error Analysis
  • Project Workflow
  • Integration Guardian
  • Claude Code Token Optimization
  • Prompt Chaining

See Archive Index.


Quality Gate (Repository Standard)

Every active prompt must include:

  • ## Role
  • ## Protocol / Core Loop
  • ## Phases
  • ## Remember (final section)

And must follow No Vague Advice:

  • each recommendation must end with a concrete decision, tool, or validation step.

Use the measurable review checklist: Prompt Review Checklist


90-Day Improvement Cycle

  • Monthly: usage, token, and link hygiene review
  • Quarterly: keep/merge/archive portfolio review and active catalog cleanup

Guide: Portfolio Maintenance Guide


Repository Structure

prompts/
└── english/
    ├── agents/          # Active agent prompts
    │   └── archive/     # Archived prompts removed from active catalog
    ├── base/            # Foundation prompt
    ├── project-types/   # Domain-specific prompts
    ├── examples/        # Real-world usage examples
    └── workflows/       # Setup, selection, troubleshooting, maintenance

Resources

Reviews (0)

No results found