place. Respect token budgets.
- **Every recommendation has a "why"** — No bare rules without justification
- **Code examples must be modern C#** — Primary constructors, collection expressions, file-scoped namespaces, records
- **No Swashbuckle
moving code
- Tracing imports or dependencies
**ALWAYS run `codemap --diff` when:**
- Reviewing or summarizing changes
- Before committing code
- User asks what changed
- Use `--ref ` when comparing against something other than
design
- ✅ Create GitHub issues with `pilot` label for execution
- ✅ Review every PR before merging
- ❌ In *interactive* sessions, do not write code directly — defer to
Pilot so the knowledge graph
guides, role definitions, ecosystem mappings
- **Quality gate**: CI workflows that review SKILL.md changes on PRs
There is no application code, build system, or test suite in this repo
opus | Designs the change before code is written. |
| `implementer` | sonnet | Writes code that matches the surrounding style. |
| `reviewer` | opus | Hunts correctness bugs in the diff. |
| `test-writer` | sonnet | Adds
login`.
- Conventional Commits for commit messages. PRs require passing CI and one review.
## Authorship voice
Code comments are minimal and explain **why**, not what. Keep naming explicit. Prefer pure functions
configured with an `http://` URL, e.g. Twilio) and 308-redirects everything else; `"redirect"` (the code default) 308s every request. All three edges run `"proxy"` — the live per-region files
code edit.** Treat project source code as read-only by default. Before editing any code file, any config that affects a running system, or any commit / push / deploy, state
parity.
- Cookbook recipes are third-party work published by their author, not code the project owns.
Review asks only three things: it does no harm, deliberately or accidentally; it does
session support, model selection, reasoning effort, sandbox mode, full-auto, and working directory options
- **review**: Codereview for uncommitted changes, branches, or commits
- **websearch**: Web search using Codex CLI with
import what you use
- Components are tree-shakeable
- No runtime overhead from library
## 2. Code Splitting
```tsx
// Lazy load heavy components
const HeavyChart = lazy(() => import('@/components/ui/chart'))
<Suspense fallback={ }>
```
## Form Controls
implemented and all quality gates pass (linting, tests, build), you MUST ALWAYS spawn the `code-reviewer` subagent in plan compliance mode to verify the ENTIRE implementation matches the plan
pull request for reviewable
changes, and do not treat owner bypass as independent review. Until a second
human maintainer exists, any owner-bypass direct push must be locally verified
contract. The second is the mechanism that enforces it, and it belongs in codereview.
**Design context written into `docs/` outlives the change and rots there.** The design context
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## Project Overview
MCP (Model Context Protocol) server for Coolify that provides 45 token
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.