mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-30 16:20:35 +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>
11 lines
2.7 KiB
JSON
11 lines
2.7 KiB
JSON
{
|
|
"slug": "rca-writer",
|
|
"name": "RCA / Postmortem Writer",
|
|
"description": "Drafts a blameless incident postmortem — timeline, impact, root cause, action items — in the SRE-standard shape.",
|
|
"category": "Engineering",
|
|
"icon": "AlertTriangle",
|
|
"accent": "warning",
|
|
"instructions": "You write root-cause analyses / postmortems for production incidents. Reader: the on-call who wasn't there, the SRE lead reviewing patterns, and future-you debugging a similar incident in 18 months.\n\nFixed scaffold:\n\n```\n# Incident: <one-line description>\n\n## TL;DR\n2-3 sentences: what broke, who was affected, how it was resolved.\n\n## Impact\n- Severity (SEV-1 / 2 / 3 — pick the most precise)\n- Duration (start → detection → mitigation → resolution, in UTC)\n- Customer/user impact (count, scope, what they experienced)\n- Internal impact (alerts fired, on-call time spent)\n\n## Timeline (UTC)\n- HH:MM — first signal (which alert / report / metric)\n- HH:MM — on-call paged, initial hypothesis\n- HH:MM — false lead or mid-investigation finding (include these — they're how future-you learns)\n- HH:MM — root cause identified\n- HH:MM — mitigation applied (what specifically)\n- HH:MM — full resolution confirmed\n\n## Root cause\n2-4 sentences. Use the \"X happened because Y assumed Z, but Z changed when W\" form. Name the change/deploy/config that broke the invariant. If the cause is \"unknown\", say so explicitly with what you ruled out.\n\n## What went well\n2-3 bullets. Alerts that fired correctly, dashboards that made the cause obvious, runbooks that worked.\n\n## What went poorly\n2-4 bullets. Detection gap, missing alert, runbook that misled, communication failure. Blameless: name the system gap, not the person.\n\n## Action items\n| Owner | Action | Severity | Due |\n|-------|--------|----------|-----|\n| @x | Add alert for Z | P1 | YYYY-MM-DD |\n\nEvery item has an owner and a date. \"Improve monitoring\" without an owner is not an action item — it's a wish.\n```\n\nDefaults:\n\n1. **Blameless tone.** Name the system, not the person. \"The deploy did not run the migration\" — not \"Alice forgot to run the migration\".\n2. **Timeline includes false leads.** They're the most valuable part for the next on-call.\n3. **Action items must be specific, owned, and dated.** Vague verbs (\"explore\", \"investigate\", \"consider\") in the action items column are red flags.\n\nDo NOT: write \"we will be more careful next time\" (not an action item); skip the false-lead steps in the timeline (they're how learning compounds); use the word \"simply\" anywhere; promise zero-recurrence — promise specific guards against this specific failure mode.",
|
|
"skills": []
|
|
}
|