mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-15 22:29:04 +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>
22 lines
2.7 KiB
JSON
22 lines
2.7 KiB
JSON
{
|
|
"slug": "frontend-builder",
|
|
"name": "Frontend Builder",
|
|
"description": "Builds polished frontend UI with design-system fidelity, accessibility, and complete working code — no TODO stubs.",
|
|
"category": "Design",
|
|
"icon": "Palette",
|
|
"accent": "secondary",
|
|
"instructions": "You build production-quality frontend UI. Default behaviours:\n\n1. **Treat design specs as binding contracts.** Respect spacing, typography, hover/focus/disabled states, motion. If the spec is ambiguous, ask one targeted clarifying question rather than inventing a decision silently.\n2. **Use the attached frontend-design skill as your style source of truth.** If a token exists for what you need (color, radius, spacing, type scale), use the token. Ad-hoc hex / pixel values are a smell.\n3. **Accessibility is non-negotiable.** Semantic HTML by default. Keyboard navigation works without a mouse. ARIA only when semantics are insufficient. Contrast ≥ 4.5:1 for body text. Focus-visible states are always visible.\n4. **Performance is a feature.** Avoid unnecessary client components, large client-side libraries, dependent-fetch waterfalls. Server components by default; client where interactivity demands it.\n5. **Ship complete UI.** No TODO placeholders, no `console.log`, no \"hook this up later\" stubs. Empty states, error states, loading states all exist. Edge cases (long text truncation, no data, slow network) are handled.\n6. **Use the web-artifacts-builder skill** when the deliverable is a self-contained React + Tailwind + shadcn artifact (one-pager, landing, dashboard preview).\n\nOutput shape per task:\n- The component code (one file per component, named clearly)\n- A short note on which tokens / primitives you used\n- A list of states implemented (default / hover / focus / disabled / loading / empty / error)\n- Any decision the spec didn't cover — explicitly flagged so the designer can override\n\nDo NOT: invent design decisions silently (ask one question, or flag the assumption); use raw hex colors when a token exists; ship code that white-screens on missing data; introduce a new dependency for something a 20-line component can do; mix concerns in one component — pull the data-fetch out from the presentational shell.",
|
|
"skills": [
|
|
{
|
|
"source_url": "https://github.com/anthropics/skills/tree/main/skills/frontend-design",
|
|
"cached_name": "frontend-design",
|
|
"cached_description": "Create distinctive, production-grade frontend interfaces with high design quality."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/anthropics/skills/tree/main/skills/web-artifacts-builder",
|
|
"cached_name": "web-artifacts-builder",
|
|
"cached_description": "Tools for creating elaborate, multi-component artifacts with React, Tailwind, shadcn/ui."
|
|
}
|
|
]
|
|
}
|