agent-orchestrator/.claude/rules/10-code-consistency.md
DexterFromLab 3672e92b7e feat: Agent Orchestrator — multi-project agent dashboard
Tauri + Svelte 5 + Rust application for orchestrating multiple AI coding agents.
Includes Claude, Aider, Codex, and Ollama provider support, multi-agent
communication (btmsg/bttask), session anchors, plugin sandbox, FTS5 search,
Landlock sandboxing, and 507 vitest + 110 cargo tests.
2026-03-15 15:45:27 +01:00

10 lines
665 B
Markdown

# Code Consistency
Before writing any code, read the existing codebase and match its patterns.
## Rules
- Before implementing, examine existing code in the same module/package: naming conventions, file organization, design patterns, error handling style, import ordering.
- Match what's there. If the project uses factories, use factories. If it's camelCase, use camelCase.
- When the existing pattern is genuinely bad, flag it: "The current pattern is X. I think Y would be better because [reason]. Want me to refactor consistently, or match existing style?"
- When a formatter or linter is configured, use it. When none exists, propose one from project start.