Help us improve
Share bugs, ideas, or general feedback.
How to work with code — language standards, security, quality, git, CI/CD, Docker, MCP, documentation
npx claudepluginhub cameronsjo/cadence-rulesHow to work with code — language standards, security, quality, git, CI/CD, Docker, MCP, documentation
Production-ready workflow orchestration with 84 marketplace plugins, 192 local specialized agents, and 156 local skills - optimized for granular installation and minimal token usage
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations
Curated collection of 154 specialized Claude Code subagents organized into 10 focused categories
Share bugs, ideas, or general feedback.
How to work with code — language standards, security, quality, git, CI/CD, Docker, MCP, documentation.
Designed to be installed alongside the codex plugin. Codex covers how to work with me. Rules covers how to work with code.
All files are installed to ~/.claude/rules/ with a rules- prefix, creating an ownership boundary. Non-prefixed files in that directory are user-managed and never touched.
| Source file | Installed as | Domain |
|---|---|---|
core-code-principles.md | rules-core-code-principles.md | Code style, naming, type annotations |
engineering-standards.md | rules-engineering-standards.md | Date/time, cost boundaries, containers |
git-workflow.md | rules-git-workflow.md | Commits, PRs, code review |
markdown-formatting.md | rules-markdown-formatting.md | Docs, tables, diagrams |
security-standards.md | rules-security-standards.md | OWASP, AI/LLM, supply chain |
testing-and-observability.md | rules-testing-and-observability.md | Testing, logging, tracing |
| Source file | Installed as | Triggers on |
|---|---|---|
beads.md | rules-beads.md | .beads/** |
cicd.md | rules-cicd.md | CI/CD configs |
dockerfile.md | rules-dockerfile.md | Dockerfiles |
docs.md | rules-docs.md | Markdown files |
mcp.md | rules-mcp.md | MCP configs |
mermaid.md | rules-mermaid.md | Mermaid diagrams |
languages/bash.md | rules-bash.md | *.sh, *.bash |
languages/csharp.md | rules-csharp.md | *.cs, *.csproj |
languages/go.md | rules-go.md | *.go, go.mod |
languages/java.md | rules-java.md | *.java, pom.xml |
languages/javascript.md | rules-javascript.md | *.js, *.jsx |
languages/powershell.md | rules-powershell.md | *.ps1, *.psm1 |
languages/protobuf.md | rules-protobuf.md | *.proto |
languages/python.md | rules-python.md | *.py, pyproject.toml |
languages/rust.md | rules-rust.md | *.rs, Cargo.toml |
languages/typescript.md | rules-typescript.md | *.ts, *.tsx |
# Via workbench hub
claude plugin install rules@workbench
claude plugin enable rules@workbench
# Then run the init command to copy rules to ~/.claude/rules/
/rules:init
The init command uses md5 hashing to detect changes — it never reads file contents into the LLM context. After running, it self-destructs from cache and reappears when the plugin updates.
MIT