ccteams

Frontier-grade engineering working method — goal compression, ground truth before opinion, hypothesis discipline, execution as evidence, honest reporting, exit checklist. Read in full at the start of any non-trivial task; inject the digest into every delegation prompt.

Operational playbook for systematic debugging — hypothesis ledgers, discriminating experiments, mechanism sentences, minimal fixes, sibling hunts. Read in full at the start of every bug investigation.

Operational playbook for Django + DRF — settings/version detection, ORM loading strategy, migration discipline, serializer field hygiene, timezone rules, and exact verification commands. Read in full at the start of every task on this team.

Operational playbook for framework-agnostic UI/UX/a11y — semantic-element-first markup, keyboard/focus verification, responsive layout checks, reuse of existing tokens over new CSS. Read in full at the start of every task on this team.

Operational playbook for stack-agnostic feature work — fixed-order stack detection, vertical-slice delivery, a catalog of unfamiliar-codebase mistakes (phantom utils, pattern drift, generated files, invented commands), and verification using only the project's own commands. Read in full at the start of every task on this team.

Operational playbook for Go HTTP APIs — error wrapping, goroutine lifetimes, database/sql resource discipline, race-flagged verification. Read in full at the start of every task on this team.

Operational playbook for Next.js App Router + TypeScript + Tailwind — server/client boundary placement, caching decisions, hydration failure catalog, build-based verification. Read in full at the start of every task on this team.

Operational playbook for FastAPI + Pydantic v2 async services — event-loop discipline, boundary validation, dependency lifetimes, response_model leaks, async ORM N+1s. Read in full at the start of every task on this team.

Operational playbook for Ruby on Rails — version/test-framework detection, ActiveRecord loading strategy, callback boundaries, migration discipline, and exact verification commands. Read in full at the start of every task on this team.

Operational playbook for Expo + React Native + TypeScript — SDK/workflow detection first, the native escalation ladder, mobile-specific failure catalog (lists, keyboard, safe areas, Expo Go limits), and a two-platform verification recipe. Read in full at the start of every task on this team.

Operational playbook for technical evaluation — project-first framing, criteria-before-candidates, source triangulation with dates, evidence-cited tradeoff matrices, and recommendation-first reporting. Read in full at the start of every task on this team.

Pick and apply the best ccteams agent team for a described need using natural language — reads team metadata, selects the closest match, and applies it.

List all available ccteams agent teams with their names, descriptions, and tags.

Apply a named ccteams agent team to the current project by running ccteams use <team-name>.