A full-featured CRM built with React, shadcn/ui, and Supabase.
Feat(plugin): Ponytail
erwanMarmelabccc5ed592b0d
diff --git a/.claude/agents/developer.md b/.claude/agents/developer.mdindex 8c858c21..2f8d093e 100644--- a/.claude/agents/developer.md+++ b/.claude/agents/developer.md@@ -149,6 +149,15 @@ Context grows with every turn — fewer turns means lower cost and faster execut## Codebase audit+Before building anything, walk the **Ponytail ladder** (applied automatically,+full mode) and stop at the first rung that satisfies the+ticket: (1) does it need to exist? → (2) stdlib? → (3) native platform feature?+→ (4) already-installed dependency (react-admin / shadcn / existing component)?+→ (5) one line? → (6) only then minimal code. The cheapest ticket adds no code+at all. Rungs 3–4 ARE the reuse registry below — build it first and let it shape+the plan. Never minimize away validation, security, accessibility, error+handling, or required tests.+From `files_to_modify`, build a reuse registry:- Existing entities in `src/resources/`@@ -193,6 +202,7 @@ e2e tests:Implement the plan. No deviations without flagging team-lead.+- **Ponytail (full mode) is always on** — apply the ladder on every ticket without being asked: native HTML/CSS and already-installed react-admin / shadcn components before any new component or dependency; deletion over addition; fewest files, shortest working diff. Adding a dependency for something the stack already covers is a blocking review finding. Never minimize away validation, security, accessibility, error handling, or required tests.- All work in the worktree. Commits on `BRANCH_NAME`, never on `main`. MERGER does the merge.- Atomic commits per logical step. Every subject includes `TASK-XXX`: `feat(TASK-XXX): <what>`.- TypeScript strict: no `any`, no `@ts-ignore` without JSDoc.diff --git a/.claude/agents/quality-reviewer.md b/.claude/agents/quality-reviewer.mdindex ddce9bcd..badb418e 100644--- a/.claude/agents/quality-reviewer.md+++ b/.claude/agents/quality-reviewer.md@@ -146,9 +146,17 @@ Any `[FAIL]` → BLOCKED. Omitting a criterion from the list is itself a bug.- Grep for hardcoded color literals — they bypass the theme system and break contrast in at least one mode.- Verify interactive states (hover, focus, disabled) use theme variables, not hardcoded values. A hardcoded foreground color on a themed background will be invisible in the opposite color mode.-### A.2 Reuse (BLOCKING)-- Native framework components used where they cover 80%+ of the need-- No duplication of existing logic — the developer should reuse existing entities, components, and types whenever possible+### A.2 Reuse & minimization (BLOCKING)++The developers apply Ponytail (full mode); review against the same ladder — flag over-engineering, not just duplication:++- Native HTML/CSS or framework components used where they cover 80%+ of the need (e.g. `<input type="date">` over a date-picker library).+- No new npm dependency for something the stack (react-admin, shadcn, stdlib) already covers → BLOCKING.+- No custom wrapper component that adds no behavior over a native element / existing component.+- No re-implementation of list / filter / form / pagination logic react-admin already provides.+- No duplication of existing logic — reuse existing entities, components, and types.++Do NOT flag the *absence* of validation, security, accessibility, error handling, or tests as "minimization" — those are required (covered by Parts A.1, A.6, A.7, B).### A.3 TypeScript correctness (BLOCKING)- No `any` without justifying JSDocdiff --git a/.claude/agents/simple-developer.md b/.claude/agents/simple-developer.mdindex 549bfbff..8dfed980 100644--- a/.claude/agents/simple-developer.md+++ b/.claude/agents/simple-developer.md@@ -114,6 +114,7 @@ Then `Read("$CLAUDE_PROJECT_DIR/MEMORY.md")` — domain vocabulary. Even a label### 3. Make the change (Edit/Write only)- Locate the file (Grep / Glob).+- **Ponytail (full mode) is always on** — walk the ladder before editing (need it? → stdlib? → native? → already-installed? → one line?). Prefer native HTML inputs and existing react-admin / shadcn components over anything new; a single-field change is usually one input + one display + one type line, no more. Never cut validation, security, accessibility, or i18n.- Edit/Write the change.- File modifications MUST go through Edit or Write — NEVER use Bash to write files (`sed -i`, `cat > file`, `echo > file`, in-place edits). Renames via `git mv` are allowed.- Stay strictly within the scope above — cosmetic, single-field (optionally with i18n labels for that field), or a list filter reusing existing components. Anything broader (multiple fields, import, new entity, new custom component) → refuse with `FAILED: out of scope — needs COMPLEX flow`.diff --git a/.claude/settings.json b/.claude/settings.jsonindex cc9dbb34..eb45edd3 100644--- a/.claude/settings.json+++ b/.claude/settings.json@@ -1,5 +1,14 @@{+ "extraKnownMarketplaces": {+ "ponytail": {+ "source": {+ "source": "github",+ "repo": "DietrichGebert/ponytail"+ }+ }+ },"enabledPlugins": {+ "ponytail@ponytail": true,"context7@claude-plugins-official": false,"playwright@claude-plugins-official": false,"security-guidance@claude-plugins-official": false,diff --git a/CLAUDE.md b/CLAUDE.mdindex 34548aa4..05abc8e6 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -27,8 +27,8 @@ The `agent-team` skill is the single source of truth for team layout and cross-a|---|---|---|| chat-orchestrator | sonnet | User-facing. Routes, narrates. SIMPLE flow dispatches simple-developer + merger directly (no team). || planner | sonnet | Decomposes the plan into tickets JSON with waves + file hints. |-| developer | opus | Implements + commits in a worktree. Writes ADRs for structural decisions. Never writes SQL migrations (deploy-time only). |-| simple-developer | sonnet | One cosmetic edit, one single-field entity change, or one filter reusing existing components. No team, no review. |+| developer | opus | Implements + commits in a worktree. Applies the **Ponytail** minimization ladder (full mode) automatically on every ticket, via an inline prompt directive. Writes ADRs for structural decisions. Never writes SQL migrations (deploy-time only). |+| simple-developer | sonnet | One cosmetic edit, one single-field entity change, or one filter reusing existing components. Applies the **Ponytail** ladder (full mode) automatically, via an inline prompt directive. No team, no review. || quality-reviewer | sonnet | Combined semantic code + security review only. Never re-runs validation. || test-validator | haiku | Integration wiring + e2e presence. || merger | haiku | `git merge --no-ff` only. Never `git add` / `git commit`. |@@ -36,6 +36,8 @@ The `agent-team` skill is the single source of truth for team layout and cross-aOnly **developer** runs on opus; everything else is sonnet or haiku.+The **developer** and **simple-developer** apply the **Ponytail** minimization ladder (full mode) on every change, via inline directives in their prompts. The plugin (`ponytail@ponytail`, enabled in `.claude/settings.json`) also provides orchestrator-level guidance and the manual `/ponytail*` skills — but its `SessionStart` / `UserPromptSubmit` hooks reach only the main session, NOT `Agent`-dispatched subagents, which is why the dev agents get the ladder inline rather than from the plugin.+## The orchestrator's job between hand-offsRelay agent reports, surface blockers, and stop to ask the user whenever an agent flags an open question or a `BLOCKED` verdict. Do not bypass this flow for "small-looking" changes — the trigger is *plan approved*, not *task size*. Direct requests that never entered plan mode are not subject to this workflow.