Skip to content

Skills Catalog

Skills are domain knowledge files that agents load as reference material when doing specific work. They define standards, conventions, and patterns — not step-by-step procedures (that’s what workflows are for).

NameDescriptionCompatible Agents
api-design-standardsREST API design conventions — URLs, methods, errors, pagination, versioningbackend, fullstack, tech-lead
auth-patternsAuthentication and authorization patterns — flows, tokens, passwords, sessions, access controlbackend, fullstack, security
cli-conventionsCLI design conventions — structure, flags, output, exit codes, configurationbackend, fullstack
coding-standardsLanguage-specific coding standards — formatting, linting, patternsbackend, devops, frontend, fullstack, security
container-standardsContainer and orchestration standards — Docker multi-stage builds, image security, Kubernetes manifestsdevops
database-conventionsSQL naming, migration patterns, schema design rulesbackend, fullstack, tech-lead
design-guideBonsai CLI design system — palette, spacing, panels, errors, command flowbackend, frontend, fullstack, tech-lead
dispatchHow to dispatch work to code agents — triage rules, prompt structure, iteration trackingtech-lead
iac-conventionsInfrastructure-as-code conventions — Terraform naming, state management, modules, taggingdevops
issue-classificationIssue types, importance levels, domain labels, and classification heuristicstech-lead
mobile-patternsMobile development patterns — state management, offline-first, navigation, performancefullstack
planning-templatePlan format, tier rules, and template for writing implementation planstech-lead
pr-creationHow to create well-structured pull requests — branch naming, title conventions, body template, draft workflowbackend, frontend, fullstack, tech-lead
review-checklistStructured code review checklist — correctness, security, performance, maintainabilitysecurity, tech-lead
test-strategyTest architecture — which tests to write, when, and why; pyramid, coverage, anti-patternsbackend, frontend, fullstack
testingTesting conventions — frameworks, patterns, coverage requirementsbackend, frontend, fullstack, security
workspace-guideBonsai workspace operational guide — how to use workflows, skills, routines, sensors, and the Playbook effectivelyall

These skills define how code should be written across different contexts:

  • coding-standards — Language-agnostic formatting, linting, and naming conventions. Default for all code agents.
  • testing — Test framework conventions, patterns, and coverage rules. Default for backend, frontend, fullstack, and security agents.
  • test-strategy — Higher-level test architecture: which tests to write, the testing pyramid, and anti-patterns.
  • cli-conventions — How to structure CLI commands, flags, output formatting, and exit codes.
  • api-design-standards — REST API conventions: URL structure, HTTP methods, error formats, pagination, and versioning. Default for fullstack.
  • auth-patterns — Authentication flows (OAuth, JWT, sessions), password handling, and access control. Default for fullstack and security.
  • database-conventions — SQL naming rules, migration patterns, and schema design. Default for backend and fullstack.
  • design-guide — UI/UX patterns, component conventions, and accessibility standards. Default for frontend and fullstack.
  • mobile-patterns — Mobile-specific patterns: state management, offline-first, navigation, and platform APIs.
  • iac-conventions — Terraform naming, state management, module structure, and resource tagging. Default for devops.
  • container-standards — Docker multi-stage builds, image security, and Kubernetes manifest conventions. Default for devops.
  • planning-template — The standard plan format with tier rules and verification steps. Default for tech-lead.
  • dispatch — Rules for dispatching work to code agents: triage, prompt structure, and iteration tracking. Default for tech-lead.
  • issue-classification — How to classify issues by type, importance, and domain. Default for tech-lead.
  • review-checklist — Structured checklist for code review: correctness, security, performance, and maintainability. Default for tech-lead and security.
  • pr-creation — Pull request conventions: branch naming, title format, body template, and draft workflow.
  • workspace-guide — Operational guide for the Bonsai workspace. How to use workflows, skills, routines, sensors, and the Playbook. Compatible with all agent types.
Agent TypeDefault Skills
Tech Leadplanning-template, issue-classification, dispatch, review-checklist
Backendcoding-standards, testing, database-conventions
Frontendcoding-standards, testing, design-guide
Full-Stackcoding-standards, testing, design-guide, database-conventions, api-design-standards, auth-patterns
DevOpscoding-standards, iac-conventions, container-standards
Securitycoding-standards, testing, auth-patterns, review-checklist