The command center for a complete Claude Code workflow — hooks, rules, methodology, and the connective tissue between every tool in the ecosystem.

Built through 500+ real-world AI collaboration sessions by a non-developer. Every hook, every rule, every framework earned its place by solving an actual problem.

Lineage: cc-empire is the merger of cc-rules-cookbook + cc-hooks-gallery + agent-nexus — three earlier repos that have since been archived. Their best parts live on here, consolidated into a single command center.

                              ┌─────────────────────┐
                              │      cc-empire        │
                              │  hooks + rules +     │
                              │  methodology + glue  │
                              └──────────┬──────────┘
                                         │
     ┌─────────────┬──────────────┬──────┴───────┬──────────────┐
     │             │              │              │              │
┌────┴─────┐ ┌─────┴─────┐ ┌──────┴──────┐ ┌─────┴─────┐ ┌──────┴──────┐
│  Memory  │ │  Content  │ │   Remote    │ │   Multi   │ │   Clone     │
│          │ │           │ │   Control   │ │  Session  │ │             │
│recallnest│ │ publishing│ │   TG + WX   │ │  studio   │ │  digital    │
│          │ │ (private) │ │             │ │           │ │   clone     │
└──────────┘ └───────────┘ └─────────────┘ └───────────┘ └─────────────┘

All modules are optional. Install what you need.

git clone https://github.com/AliceLJY/cc-empire.git
cd cc-empire
bash install.sh

The installer will:

1. Check prerequisites (Claude Code, git, etc.)
2. Show available modules — pick what you need
3. Install hooks into ~/.claude/hooks/ (mirroring the category layout, e.g. hooks/safety/bash-guard.sh)
4. Set up CLAUDE.md and workflow templates
5. Clone selected module repos

Then activate the hooks: merge settings-template.json into your ~/.claude/settings.json — its paths match what the installer creates.

Hooks covering six Claude Code lifecycle events. 16 are general-purpose and registered in settings-template.json; 3 are personal-flavored (marked below) — read them before enabling.

Safety Guards

Workflow Automation

Lifecycle Management

Quality Checks

Feedback Capture

All hooks support profile control (CC_HOOK_PROFILE=off to disable all) and individual disable (CC_DISABLED_HOOKS=hook1.sh,hook2.sh).

See docs/hook-lifecycle.md for the complete lifecycle diagram.

Distilled from 500+ sessions into reusable patterns. Located in rules/.

Methodology — How to work with AI

Thinking Frameworks — How to think clearly with AI

Borrowed Patterns — Proven techniques adapted for AI workflows

Architecture — System design patterns

• CLAUDE.md.example — Project contract template (execution rules, verification, reply discipline)
• workflow.md — Research → Plan → Implement methodology with ReAct loop
• memory/ — Memory index structure (MEMORY.md + identity + feedback templates)

Edit ~/.claude/hooks/repos.conf to add your project directories:

TRACKED_REPOS=(
  "$HOME/Projects/my-app"
  "$HOME/Projects/my-lib"
)

This project was built by a non-developer through AI collaboration. The perspective is different from most CC workflow tools:

• Cross-domain, not just coding — Writing pipelines, bot operations, remote control, not just TDD
• Production-tested rules — Every rule exists because its absence caused a real problem
• Memory as infrastructure — Persistent memory isn't optional; it's how the AI gets better over time
• Honest methodology — Anti-sycophancy prompts, neutral verification, confidence tags
• First-principles thinking — Patterns are cross-domain; a writing review framework becomes a code review framework

See docs/architecture.md for how modules work together.

Issues and PRs welcome. If you've built hooks or workflow rules that made your CC life better, share them.

MIT