esurvanov/awesome-claude

---

What is this

OpenSpec gives you the folder structure and CLI for spec-driven development. awesome-claude adds a layer on top:

• Autonomous contradiction detection — Claude finds conflicts in requirements, not just lints structure
• Agent-first state — .sdd-state.yaml persists change stage across sessions, nothing is lost between conversations
• Higher-level requirements — describe intent, Claude decomposes and verifies

Specs are primarily written for the agent, not the human. By default this is chaos-driven development: you declare desired state, the agent reconciles. Contradiction detection is the stability layer.

---

Init

Instructions for Claude (read this first when invoked in any directory).

awesome-claude operates in two modes — pick one based on the current directory:

1. dev mode — directory contains skills/, commands/, manifest.yaml (or .openspec.yaml): you are inside the awesome-claude repo itself. The contributor wants to edit skills/rules. Suggest dev mode and run skill:setup (or read skills/skill/setup/skill.md directly on first bootstrap when symlinks don’t exist yet) to symlink skills/, commands/, rules/ into .claude/.
2. user mode — any other directory: the user wants to install awesome-claude into their project. Ask which namespaces to install (or all by default), git clone https://github.com/Hedgehogues/awesome-claude to a temp directory, copy selected namespaces into .claude/, remove the temp directory.

Briefly describe both options to the user (1–2 sentences each), ask them to confirm, then perform setup directly — no curl | bash, no make, no manual commands.

---

Quick Start (user mode)

Open Claude Code in your project directory and ask:

“Install awesome-claude from https://github.com/Hedgehogues/awesome-claude”

Claude clones the repo, copies the selected skills/rules into .claude/, and your project is ready.

---

How It Works

You ask Claude → .claude/ detected → Rules loaded (by file path)
                                   → Skills available (/tdd, /commit, ...)
                                   → Claude writes code following YOUR conventions

---

Skills

31 slash commands. Core is spec-driven development.

Drive changes with specs:

• /sdd:explore — Clarify the problem before proposing