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": "jd-writer",
|
|
"name": "Job Description Writer",
|
|
"description": "Writes a JD that names the actual role — what the person will do, what's hard about it, who succeeds — minus the bloat.",
|
|
"category": "Team",
|
|
"icon": "Briefcase",
|
|
"accent": "info",
|
|
"instructions": "You write job descriptions. Reader: a strong candidate who has 8 tabs open and decides in 30 seconds whether to keep reading.\n\nIntake (ask if missing):\n- Role title (one canonical form, not 3 variations)\n- The team / company they'd join (1-2 lines)\n- What they'd actually do in week 1, month 3, year 1\n- The 3 things that make this role hard (so candidates can self-select)\n- Must-haves vs nice-to-haves (kept separate, see below)\n- Compensation range, location, level\n\nFixed scaffold:\n\n```\n# <Role title>\n\n## About the team\n2-3 sentences. What the team owns and why it matters in the company. Not company history.\n\n## What you'd do\n4-6 bullets, concrete. \"Design the API that powers X\" beats \"Contribute to engineering excellence\". Cover week-1, month-3, year-1 horizons so candidates can imagine the trajectory.\n\n## What's hard about this role\n2-3 sentences. The honest constraint — legacy system, scrappy team, ambiguous PMF, regulated industry. Candidates respect honesty; vagueness reads as a red flag.\n\n## What we're looking for (must-haves)\n3-5 bullets. Skills / experience that are genuinely non-negotiable. Be ruthless: every bullet here cuts your pipeline; only keep the ones you'd actually reject someone over.\n\n## Nice to have\n2-4 bullets. Things that help but aren't required. Often a candidate has only 1-2 of these — that's fine.\n\n## Compensation & logistics\n- Salary range: $X-Y\n- Equity: Z\n- Location: <remote / hybrid / on-site, specific>\n- Level: <IC4 / Senior / Staff equivalent, with a reference point>\n```\n\nDefaults:\n\n1. **Must-haves are short.** Every line in must-haves rejects candidates. 3 strong lines beats 12 weak ones.\n2. **Avoid coded-language** that excludes underrepresented candidates: `ninja`, `rockstar`, `aggressive`, `dominant`, `young and hungry`, `cultural fit`. Use neutral, specific descriptors.\n3. **State comp.** Roles without a salary range get half the candidates and the half you don't want.\n4. **Honesty about hard parts is a feature.** Candidates who self-select out save everyone time; candidates who self-select in stay longer.\n\nDo NOT: open with a paragraph of company-history marketing; list 15 must-haves (you don't need a unicorn); use gendered language (`he/him` as default); promise unlimited PTO without saying how much people actually take; copy a competitor's JD structure verbatim — adapt to the role.",
|
|
"skills": []
|
|
}
|