mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-30 16:20:35 +02:00
68edf57f64
Server-side foundation for Phase 1 of the quick-create roadmap (see
docs/agent-quick-create-plan.md). Adds:
- server/internal/agenttmpl/ — embed-loaded catalog of curated agent
templates. Each template ships pre-written instructions plus a list
of skill URLs that get materialised into the workspace at create
time. Validation runs at startup (init() panics on a malformed
template) so a bad JSON ships as a deploy-time defect, not a
runtime 500. Slug must equal the filename basename so the URL
router is mirror-symmetric with the file layout.
- 11 starter templates covering Engineering / Writing / Building /
Testing (code-reviewer, frontend-builder, planner, docs-writer,
one-pager, html-slides, full-stack-engineer, …).
- Three new endpoints, all behind RequireWorkspaceMember:
GET /api/agent-templates — picker list (no instructions)
GET /api/agent-templates/:slug — detail with instructions
POST /api/agents/from-template — materialise + create
Create flow:
1. Auth + runtime authorization happen BEFORE the GitHub fan-out
so a 403 never wastes 20s of upstream fetches.
2. Pre-flight dedupe by cached_name reuses workspace skills
without an HTTP fetch — second create-from-the-same-template
drops from 20s to <100ms.
3. Parallel fetch (30s per-URL timeout) for the remaining skills.
4. Single transaction: every skill insert, the agent insert, and
the agent_skill bindings. On any upstream fetch failure the TX
rolls back and the API returns 422 with `failed_urls` so the
UI can name the bad source(s).
5. extra_skill_ids (user-supplied additions) are verified through
GetSkillInWorkspace per id before attach, so a malicious client
can't graft a skill from another workspace via UUID guessing.
- multica agent create --from-template <slug> CLI flag dispatches to
the new endpoint with a 60s ceiling, matching `multica skill import`.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
22 lines
1.6 KiB
JSON
22 lines
1.6 KiB
JSON
{
|
|
"slug": "frontend-builder",
|
|
"name": "Frontend Builder",
|
|
"description": "Builds polished frontend UIs with design-system fidelity and accessibility in mind.",
|
|
"category": "Building",
|
|
"icon": "Palette",
|
|
"accent": "secondary",
|
|
"instructions": "You build production-quality frontend UIs. Default behaviors:\n\n1. Treat design specs as binding contracts: respect spacing, typography, hover/focus/disabled states, and motion.\n2. Use the attached design skill as your style source of truth. If a token (color, radius, spacing) exists, use it; do not introduce ad-hoc values.\n3. Accessibility is non-negotiable: semantic HTML, keyboard navigation, ARIA only when semantics are insufficient, contrast ratio ≥ 4.5:1 for body text.\n4. Performance budget: avoid unnecessary client components, large client-side libraries, and waterfalls of dependent fetches.\n5. Ship complete, working UI — no TODO placeholders, no \"hook this up later\" stubs.\n\nWhen the user gives a vague spec, ask one targeted clarifying question (which layout, which interaction) before writing code. Do not invent design decisions silently.",
|
|
"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."
|
|
}
|
|
]
|
|
}
|