mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-22 17:49:48 +02:00
0c4133ef5b
* feat(agents): rewrite template catalog as 25 lightweight starters Replaces every Phase-1 template with a curated set built around the "persona + intake + scaffold + hard negatives" instruction shape. Cross- platform survey (Cursor / Cline / Roo / Continue / Custom GPTs) showed the industry baseline for starter agents is "few but sharp" — single intent, no methodology buy-in, mostly prompt-only. The original catalog went the opposite direction (avg 2.5 skills, six-skill Full-stack methodology stack) and felt heavy for first-time use. Catalog shape: - 25 templates across 7 categories: Engineering (8), Product (4), Writing (5), Design (3), Communication (2), Team (1), Productivity (2). New Product / Design / Communication / Team domains fill gaps the old Eng-heavy catalog ignored. - 16 / 25 are prompt-only (no skill fan-out). Avg 0.56 skill per template vs. 2.5 prior. Heaviest is 2 skills, only for templates whose intent cannot be expressed in instructions alone (Playwright runner, single- file HTML bundlers, design + UX-guidelines pair). - Universal top-frequency intents that the old catalog missed are now covered: Code Explainer (intent #1 across every platform surveyed), Translator (中英), Summarizer, Writing Critic, PRD Drafter/Critic, RCA Writer, ADR Writer, PR Description Writer, Commit Message Writer. Loader allows 0-skill templates: - server/internal/agenttmpl/loader.go drops the "must declare at least one skill" validation; comment explains the picker's "Prompt only" rendering path. - loader_test.go: removed the corresponding negative case, added TestLoadFromFS_PromptOnlyTemplate as a regression guard. - agent_template.go handler is unchanged — every len(tmpl.Skills) call site was already 0-safe (empty fan-out short-circuits the fetch phase and the in-tx loop both skip cleanly). Frontend: - template-picker.tsx: 18 new lucide icons (BookOpen, Bug, GitPullRequest, GitCommit, AlertTriangle, Scale, ClipboardList, Microscope, UserRound, Target, Highlighter, Languages, AlignLeft, GraduationCap, Lightbulb, Type, MessageSquare, Briefcase). Card renders a "Prompt only" badge when skills.length === 0 instead of "0 skills". - template-detail.tsx: skill list section is hidden entirely for prompt- only templates — a header reading "Includes 0 skills" above an empty list was just visual noise. Instructions section below carries the agent's identity for these. - locales/en + zh-Hans agents.json: new create_dialog.template_card. prompt_only key ("Prompt only" / "纯指令"). Verification: - go test ./internal/agenttmpl/ — 9/9 pass, including TestLoad_RealTemplates which fails closed if any new JSON is malformed. - pnpm typecheck — all 6 packages clean. - pnpm --filter @multica/views test — 482/482 pass. - pnpm lint — 0 errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(agents): add category filter pills to template picker 25 templates across 7 categories made the picker scroll-heavy on first open. Add a single-select category filter row above the grid so a PM can isolate Product templates in one click, an engineer can jump straight to Engineering, etc. Visual reuses the IssuesHeader scope-toggle pattern verbatim — Button variant="outline" + active class swap (bg-accent / text-muted-foreground) — so the affordance reads the same as the existing filter pills in issues / squads / runtimes / my-issues. flex-wrap keeps the 8 pills (All + 7 categories) honest on narrow widths. Counts are inlined into the label ("Engineering (8)") rather than shown as a separate badge — single-line-tall pills look right next to the picker grid, and surfacing the per-category density up front doubles as a hint at the catalog's "less but sharper" intent. When a specific category is active, the grid renders flat (no section headers) — the active pill already names what's on screen, and a header reading "Engineering" above an only-Engineering grid is visual duplication. "All" falls back to the prior grouped layout. State is component-local (no URL sync, no persistence) since the picker is dialog-internal transient state — closing the dialog naturally resets the filter, which is the expected behaviour for a "choose from a catalog" surface. i18n: new `create_dialog.template_picker.filter_all` key in en + zh. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
17 lines
2.2 KiB
JSON
17 lines
2.2 KiB
JSON
{
|
|
"slug": "bug-fixer",
|
|
"name": "Bug Fixer",
|
|
"description": "Diagnoses a failure by tracing it back to the root cause, then proposes the smallest fix that addresses it.",
|
|
"category": "Engineering",
|
|
"icon": "Bug",
|
|
"accent": "warning",
|
|
"instructions": "You debug systematically. Given a failure (stack trace, wrong output, flaky test), your job is to find the root cause and fix it — not paper over the symptom.\n\nDefaults:\n\n1. **Reproduce or get the user to.** If you can't see the failure happen, ask for the exact command, input, environment, and the full error. Never start fixing on guesses.\n2. **Trace backward, not forward.** Start at the failure point and walk the stack toward the trigger. Use the root-cause-tracing skill — name each hop and what it tells you.\n3. **State the root cause in one sentence before proposing a fix.** \"X happens because Y assumes Z, which is no longer true since W.\" If you can't write that sentence, you don't understand the bug yet.\n4. **The fix lives where the cause lives.** If the root cause is in module A, fix it in module A. Wrapping module B with a try/catch that swallows A's symptom is a patch, not a fix.\n5. **Prove the fix.** Write or update a test that fails before and passes after. If the bug is in a code path tests can't reach, say so explicitly and explain the manual repro.\n\nOutput shape:\n**Symptom** — what the user sees.\n**Root cause** — one sentence, naming the file and line.\n**Fix** — the diff (small) and where it goes.\n**Test** — the test that pins this down, or why one isn't feasible.\n\nDo NOT: add a defensive `if` to silence the error without explaining what condition triggers it; suggest \"add more logging and see what happens\" as a fix (logging is investigation, not resolution); claim something is fixed without running the repro; widen scope (\"while I'm here, let me also refactor X\") — one bug, one fix.",
|
|
"skills": [
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/debugging/root-cause-tracing",
|
|
"cached_name": "root-cause-tracing",
|
|
"cached_description": "Systematically trace bugs backward through the call stack to find the original trigger."
|
|
}
|
|
]
|
|
}
|