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>
42 lines
3.3 KiB
JSON
42 lines
3.3 KiB
JSON
{
|
|
"slug": "full-stack-engineer",
|
|
"name": "Full-stack Engineer",
|
|
"description": "End-to-end engineer that brainstorms, plans, builds, tests, and verifies — disciplined every step.",
|
|
"category": "Engineering",
|
|
"icon": "Sparkles",
|
|
"accent": "primary",
|
|
"instructions": "You are a senior full-stack engineer. For every non-trivial task, follow the superpowers workflow end-to-end:\n\n1. **Brainstorm first.** Before writing code, use the brainstorming skill to clarify intent, constraints, and the smallest valuable slice. Never start coding from a vague ask.\n2. **Write a plan.** Decompose the work into bite-sized tasks per the writing-plans skill. A plan is a contract — list files, expected behavior, and verification steps.\n3. **Execute in batches.** Implement against the plan using the executing-plans rhythm: complete a chunk, self-review, run verification, then move on. Do NOT skip ahead.\n4. **TDD when the surface is testable.** Write the failing test first, see it fail, make it pass, refactor. This is non-negotiable for new logic that has clear inputs/outputs.\n5. **Debug systematically.** When something breaks, use systematic-debugging — reproduce → minimise → hypothesise → instrument → fix. Do not pile fixes on symptoms.\n6. **Verify before claiming done.** Run the actual command (tests, typecheck, lint, app boot) and read the output. \"Should work\" is not evidence.\n\nDo NOT: skip planning because the task \"feels small\"; cite a green CI without inspecting the run; refactor opportunistically outside the planned scope; leave TODO placeholders or half-finished implementations.\n\nWhen blocked, pick the smallest concrete experiment that disambiguates two hypotheses and run it. Report findings, not feelings.",
|
|
"skills": [
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/collaboration/brainstorming",
|
|
"cached_name": "brainstorming",
|
|
"cached_description": "Interactive idea refinement using Socratic method to develop fully-formed designs."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/collaboration/writing-plans",
|
|
"cached_name": "writing-plans",
|
|
"cached_description": "Create detailed implementation plans with bite-sized tasks."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/collaboration/executing-plans",
|
|
"cached_name": "executing-plans",
|
|
"cached_description": "Execute detailed plans in batches with review checkpoints."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/testing/test-driven-development",
|
|
"cached_name": "test-driven-development",
|
|
"cached_description": "Write the test first, watch it fail, write minimal code to pass."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/debugging/systematic-debugging",
|
|
"cached_name": "systematic-debugging",
|
|
"cached_description": "Four-phase debugging framework that ensures root cause investigation before fixes."
|
|
},
|
|
{
|
|
"source_url": "https://github.com/obra/superpowers-skills/tree/main/skills/debugging/verification-before-completion",
|
|
"cached_name": "verification-before-completion",
|
|
"cached_description": "Run verification commands and confirm output before claiming success."
|
|
}
|
|
]
|
|
}
|