Sibling deliverables live in this repo: `plugin/` is the herdr plugin that renders Pairing Codes and posts Agent Notifications (Node, zero framework, `npm test`); `relay/` is the stateless Push Relay
frontmatter checking), use a script. Reserve LLM judgment for contextual diagnosis, design decisions, and codereview.
**Write dense.** High fidelity, minimum words. Prefer tables and lists over paragraphs
posts, emails, ads, landing pages)
- Any project planning or architecture decisions
- Any refactoring or codereview
- Any task where the user asks "how should I..." or "what's the best
goals, alternatives rejected, risk accepted -- then the blueprint, then the code. A requirement written after the fact reviews nothing, and `scripts/check_product_record.py` gates PRs on citing one (or an explicit
auto-imports these):
@skill/CLAUDE.md
@command/CLAUDE.md
@agent/CLAUDE.md
@docs/CLAUDE.md
## Behavioral Guidelines
Behavioural guardrails applied to every coding, review, and refactoring task in this repo. Full skill: `~/.claude/skills/karpathy-guidelines/SKILL.md`.
1. **Think before coding.** State
next regression. If you find existing naked suppressions,
treat them as a mini code-review task: add a reason or remove the
suppression.
If a threshold (`max-complexity`, `max-args
Dispatch - Development Guide
Dispatch is a skill (`/dispatch`) for Claude Code that decomposes large coding tasks into subtasks, dispatches them to background AI worker agents, and tracks progress via checklist
Development
This project enforces WCAG AA accessibility standards for all web UI code.
## Hook-Based Enforcement
Accessibility review is enforced by three global hooks:
1. **Proactive detection** (`UserPromptSubmit`) — Detects
Development
This workspace enforces WCAG AA accessibility standards for all web UI code.
## Hook-Based Enforcement
Accessibility review is enforced by three global hooks, not just instructions:
1. **Proactive detection
driven development** (`superpowers:subagent-driven-development`) — Dispatch subagents per task in this session with codereview between tasks. Faster, lighter-weight, lower token cost.
> 3. **Parallel session** (`superpowers:executing-plans
these automatically.
---
## Architecture Principles
### Business-First Design
- Designed for non-technical GTM users
- No coding required
- Natural language interaction supported
### Token Optimization
- Average 3.2 components per plugin (follows Anthropic
Optional` from typing, using the `| `syntax.
- Always add appropriate type hints such that the code would pass a pywright type check.
- Do not add extra newlines before loops.
- For type
Trust in emergence from simple, well-defined components
- Direct library integration with minimal wrappers
### Code Style
- Use 4 spaces for indentation
- Maximum line length: 120 characters
- Follow PEP 8 naming
refs to click/type/drag/select
3. Re-snapshot if the page changed
## Skills
### /review-code - CodeReview After Changes
Reviewcode changes in the current branch compared to main. Provide structured feedback
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.