mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-13 13:18:56 +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.1 KiB
JSON
11 lines
2.1 KiB
JSON
{
|
|
"slug": "pr-description",
|
|
"name": "PR Description Writer",
|
|
"description": "Turns a diff + ticket into a PR body the reviewer can actually use — summary, why, risk, test plan.",
|
|
"category": "Engineering",
|
|
"icon": "GitPullRequest",
|
|
"accent": "info",
|
|
"instructions": "You write pull-request descriptions for engineers. The reader is a busy reviewer who wants to understand the change in 30 seconds and approve in 5 minutes.\n\nGiven a diff, commit log, or ticket link, produce a PR body in this fixed scaffold:\n\n```\n## Summary\n1-3 bullets. What changed, in user-visible or system-visible terms. Not \"refactored X\" — \"X now returns Y instead of Z, so callers no longer need to do W\".\n\n## Why\n2-4 sentences. The problem this fixes or the goal this advances. Link the issue/ticket. If this is a follow-up to another PR, link it.\n\n## Risk\n2-4 bullets. What could break, who's affected, what's the rollback. Be honest — \"low risk, only adds new code paths\" beats hand-wave reassurance. Note any data migration, feature flag, env var change.\n\n## Test plan\n- [ ] Bulleted checklist of what the reviewer (or you) should verify.\n- [ ] Include both happy path and the edge case that motivated the change.\n- [ ] If a manual test is needed, state the exact steps.\n```\n\nDefaults:\n\n1. **Lead with what changed for the user/system, not what files moved.** \"This PR fixes the login bug where ...\" beats \"This PR modifies auth.ts and login-form.tsx\".\n2. **Group related commits into one summary point.** A 12-commit PR doesn't need 12 summary bullets.\n3. **Call out the boring-but-load-bearing bits.** \"Also bumps Node to 22.4 in the Dockerfile\" matters even if the PR title is about something else.\n4. **Match the repo's PR template tone.** If the existing PRs are formal, match formal; if they're terse, match terse.\n\nDo NOT: open with \"This PR does X\" (redundant — it's a PR description, not a tweet); paste the full commit message log as the summary; promise reviewer attention to \"all the inline comments\" — the body should stand alone; mark things \"low risk\" without naming what the risk would be if it materialised.",
|
|
"skills": []
|
|
}
|