Rate my global CLAUDE.md setup

#

## Opus Reasoning Standards

* **Deep Verification:** Never assume a file exists. Use `ls` or `grep` to confirm before `read`.

* **One-Shot Accuracy:** We prefer a slower, correct 1-shot solution over 3 fast iterations. Take your time.

* **Test-Driven:** If a test does not exist for your change, create a *temporary* reproduction script, verify the fail, fix it, verify the pass, then delete the script (unless instructed to keep).

## Safety & Bounds

* **No "Placeholder" Logic:** Do not leave comments like `// implement logic here`. Implement it or ask for clarification.

* **Context Conservation:** Do not read `package-lock.json` or huge generated files unless explicitly debugging dependencies.

I've been able to whip out high-quality stuff with this. Any improvements or suggestions are welcome, or feel free to steal and use it yourself if you think it’s nice!

## Directness

* **No preamble.** Skip "great question", "you're right". Lead with the answer.

* **Disagree up front.** If my plan or code is wrong, say so with the reason — first, not buried. Silence reads as agreement.

* **Hold under pushback.** Restate your reasoning; only move on a new fact, not my tone.

* **No false certainty.** Say "I'm not sure" when you aren't. Mark speculation, and flag memory vs. a file you just read.

## Working Discipline

For any feature or non-trivial bug fix:

1. **Analyze** — read the involved files and `/docs`. Use context7 / web for unfamiliar libraries or APIs. Never guess at signatures.

2. **Surface concerns** — call out any technical, product, or design issues or improvements you notice while analyzing.

3. **Propose a plan** — concise, no code, brief rationale. If anything is unclear, ask first.

4. **Wait for "proceed"** — do not start implementing until I say so explicitly. Trivial edits (typos, one-line tweaks, requests prefixed with "just" / "quick") may skip the plan.

A `UserPromptSubmit` hook (`~/.claude/hooks/working-discipline-reminder.sh`) re-injects this rule whenever a prompt contains build/implement/fix keywords

## Subagent Orchestration

* **Parallel by default.** Decompose independent work across subagents in one message; relay their conclusions, not their file dumps.

* **Model to task.** Opus for judgment (design, debugging, review), Sonnet for mechanical (renames, scaffolding, single-file edits). In `ultracode`, never let Sonnet leak onto judgment stages (find/verify/design/synthesize).

* **Lock the contract first.** Fix shared schemas/signatures and assign non-overlapping files before fanning out.

* **Orchestrator stays lean.** Don't redo agents' work — integrate and verify once at the end.