Omar SobhandClaude Opus 5
4358964c05
55 of 85 role skill bindings pointed at skills that were never authored,
so 10 of 11 team templates bound a smaller context bundle than their role
prompts assumed. Three roles bound nothing at all (gpu.bench_engineer,
threejs.shader_author, threejs.perf_engineer) while their prompts described
procedures they had no way to read.
The loader comment at team_template_loader.rs:167 already diagnosed this —
snake_case slugs in TOML against kebab-case skill files — and it was
half-fixed: the kebab names were corrected, the snake_case ones left.
It was invisible because both existing tests assert authored ⊆ referenced
(30/30, green) and the second explicitly declines to check the other
direction. So the failing half was the half nobody asserted.
Resolved every name by one of three explicit choices:
- 23 skills authored where the role genuinely needed the procedure
(gpu, threejs, research, analysis, frontend, mobile, backend, platform)
- renames onto authored skills where one existed in substance, including
the four-near-duplicate cases that collapse onto one real skill
- 22 aspirational references deleted — a binding an agent cannot read is
a promise, not a capability
Two tests now hold it. The unit test checks referenced ⊆ authored against
the files. The new integration test runs both loaders in boot order and
asserts the bindings survive the trip through the database, which is a
different question: resolution goes through skills_catalog rows, so a skill
file that exists but fails to ingest still leaves the role empty.
Negative controls: the unit test failed naming all 55; the integration test
fails naming the exact role when one name is reverted.
threejs.shader_author and .perf_engineer gained a second and third skill
after the collapse — pin_in_context pins idx < 2, so a role left with one
skill silently pins less than the policy intends.
Co-Authored-By: Claude Opus 5 <[email protected]>
90 lines
3.1 KiB
TOML
90 lines
3.1 KiB
TOML
key = "backend"
|
|
name = "Backend"
|
|
description = "Rust backend teams — Postgres, DuckDB, graph databases, APIs, wire protocols, middleware."
|
|
stack = ["rust", "postgres", "duckdb", "graph", "api", "middleware"]
|
|
default_topology = "pipeline"
|
|
risk_profile = "coding_readwrite"
|
|
mcp_bundles = ["clawmates_door", "gitea_forge"]
|
|
version = 1
|
|
|
|
[[roles]]
|
|
slot = "api_designer"
|
|
order_idx = 0
|
|
skills = ["decompose-int-items", "openapi-contract-first", "small-focused-commits", "api-pagination-day-1"]
|
|
system_prompt = """
|
|
You are the API DESIGNER of a Backend team.
|
|
|
|
For each INT item, specify the endpoints, request/response schemas,
|
|
error contract, and pagination behavior BEFORE any code is written.
|
|
Prefer additive changes; call out breaking ones explicitly.
|
|
"""
|
|
brain_seed = """
|
|
# API design memory seed
|
|
|
|
## Wire discipline
|
|
- Every list endpoint paginates from day 1.
|
|
- Every mutation is idempotent (accept a client-supplied key) or
|
|
documents why it can't be.
|
|
- Errors use RFC 7807 problem details.
|
|
"""
|
|
|
|
[[roles]]
|
|
slot = "db_engineer"
|
|
order_idx = 1
|
|
skills = ["postgres-migrations-forward-only", "postgres-index-selection", "postgres-explain-analyze", "write-rust-current-edition", "workspace-repo-commit-protocol"]
|
|
system_prompt = """
|
|
You are the DB ENGINEER of a Backend team.
|
|
|
|
Own migrations, indexes, transaction boundaries, and query plans.
|
|
For any new query, run EXPLAIN ANALYZE mentally (or in the sandbox
|
|
when a DB is available) and rule out seq scans on hot paths.
|
|
"""
|
|
brain_seed = """
|
|
# DB memory seed
|
|
|
|
## Migration protocol
|
|
- Every migration is forward-only + reversible-by-new-migration.
|
|
- Never DROP without a two-release deprecation window.
|
|
- CREATE INDEX CONCURRENTLY on tables > 1M rows.
|
|
|
|
## Index heuristics
|
|
- Every FK gets an index unless it's write-heavy + rarely queried.
|
|
- Partial indexes for high-cardinality boolean filters.
|
|
"""
|
|
|
|
[[roles]]
|
|
slot = "coder"
|
|
order_idx = 2
|
|
skills = ["write-rust-current-edition", "cargo-test-driven-development", "workspace-repo-commit-protocol", "int-xx-marker-protocol", "rust-error-handling", "rust-async-tokio-idioms"]
|
|
system_prompt = """
|
|
You are the CODER of a Backend team.
|
|
|
|
Implement per the API DESIGNER + DB ENGINEER handoffs. Keep the HTTP
|
|
layer thin — validation + auth at the boundary, business logic in a
|
|
service layer that's testable without a Tokio runtime.
|
|
"""
|
|
brain_seed = ""
|
|
|
|
[[roles]]
|
|
slot = "tester"
|
|
order_idx = 3
|
|
skills = ["cargo-test-driven-development", "postgres-integration-testing", "tdd-red-green-refactor"]
|
|
system_prompt = """
|
|
You are the TESTER of a Backend team.
|
|
|
|
Integration tests hit a real Postgres via testcontainers — never mock
|
|
the DB in tests that matter. Contract tests validate the OpenAPI schema
|
|
still matches the shipped handlers.
|
|
"""
|
|
brain_seed = ""
|
|
|
|
[[roles]]
|
|
slot = "committer"
|
|
order_idx = 4
|
|
skills = ["workspace-repo-commit-protocol", "small-focused-commits"]
|
|
system_prompt = """
|
|
You are the COMMITTER. Same protocol as rust_sdlc: only run when tests
|
|
pass and reviewer (implicit here) approved. Emit COMPLETED: INT-<NN>.
|
|
"""
|
|
brain_seed = ""
|