engineering-team

Plugin engineering-team from marketplace tonone-ai in tonone-ai/tonone. Commands read from the repo's manifest — 2 days ago.

Skills (90)

• apex-decisions

  Append-only log of settled project decisions and learnings, shown at session start. Use when asked to "log this decision", "record that we decided", "supersede decision", "what did we decide", "/learn", "remember this lesson", or "show learnings".

• apex-guard

  Opt-in session guard that confirms destructive commands and freezes edits to one directory. Use when asked to "be careful", "freeze edits to src/", or "guard this session".

• apex-plan

  Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

• apex-recon

  Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

• apex-retro

  Weekly engineering retrospective from git history. Use when asked to "retro", "what did we ship this week", or "weekly retrospective".

• apex-review

  Cross-cutting multi-lens review of a diff — parallel security/backend/data/test lenses, red-team pass, merged verdict. Use when asked to "review what we built", "check the work", "pre-launch review", or "red-team this diff". Not the skill-manifest gate.

• apex-second-opinion

  Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".

• apex-skillify

  Turn a flow that just worked in this session into a reusable skill. Use when asked to "skillify this", "make this a skill", or "save this workflow".

• apex-status

  CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

• apex-takeover

  System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

• atlas-adr

  Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

• atlas-changelog

  Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".

• atlas-map

  Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".

• atlas-onboard

  Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".

• atlas-present

  Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".

• atlas-recon

  Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".

• atlas-report

  Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.

• cortex-eval

  Evaluate model performance — check for accuracy drops, data drift, and error patterns. Use when asked about "model accuracy dropped", "evaluate the model", "check for drift", or "model performance".

• cortex-integrate

  Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".

• cortex-model

  Build an ML pipeline — from data to trained model to serving endpoint. Use when asked to "build ML model", "train a model", "prediction pipeline", "classification", or "regression".

• cortex-prompt

  Build a production-ready prompt package — system prompt, few-shot examples, output format, edge case handling, eval criteria. Use when asked to "prompt engineering", "build a prompt", "write a system prompt", or "improve this prompt".

• cortex-recon

  ML reconnaissance — inventory all models, pipelines, data sources, and monitoring. Use when asked "what ML do we have", "model inventory", or "ML assessment".

• flux-health

  Data quality and pipeline health check — freshness, schema drift, null rates, orphaned records, pipeline status. Use when asked about "data quality check", "pipeline health", "is our data fresh", or "schema drift".

• flux-migrate

  Build zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence. Use when asked to "write migration", "schema change", "add column", "rename table", "drop column", or "migrate safely".

• flux-pipeline

  Build a data pipeline — ETL/ELT with extraction, transformation, loading, error handling, and scheduling. Use when asked to "build ETL", "data pipeline", "move data from X to Y", or "sync data".

• flux-query

  Optimize slow database queries — analyze execution plans, add indexes, rewrite queries. Use when asked about "slow query", "optimize SQL", "query performance", or "explain this query".

• flux-recon

  Database reconnaissance — full inventory of schema, migrations, data volume, backups, connection pooling, and query patterns. Use when asked to "assess this database", "understand the schema", or "database health check".

• flux-schema

  Design and build database schema — tables, columns, types, indexes, constraints, relationships. Given a domain description, output the schema and write the files. Use when asked to "design schema", "database design", "create tables", or "data model".

• forge-audit

  Audit existing infrastructure for security issues, waste, and misconfigurations. Use when asked to "audit my infra", "check cloud setup", "infra review", "are we wasting money", "security check on infra", or "review my terraform".

• forge-cost

  Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".

• forge-diagnose

  Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".

• forge-infra

  Build production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".

• forge-network

  Design and build networking infrastructure — VPCs, subnets, DNS, load balancers, firewall rules. Use when asked to "set up networking", "VPC design", "configure DNS", "load balancer setup", "network architecture", or "firewall rules".

• forge-recon

  Infrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".

• lens-audit

  Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".

• lens-dashboard

  Design and spec an analytical dashboard — the question each chart answers, SQL queries, layout and refresh cadence, ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".

• lens-metrics

  Produce a metrics definition doc — name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like, for a product area. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".

• lens-recon

  Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".

• lens-report

  Build a reporting pipeline — scheduled reports with SQL queries, delivery via Slack or email, threshold alerts, and historical comparison. Use when asked for "automated reports", "scheduled report", "email digest", or "Slack alerts for metrics".

• pave-audit

  Audit developer experience — measure onboarding time, build speed, deployment friction, and developer satisfaction. Use when asked to "DX audit", "developer experience review", "why is development slow", "onboarding assessment", or "DORA metrics".

• pave-catalog

  Build a service catalog — schema, starter entries, and governance model. Produces what information to capture per service, how it's maintained, and where it lives. Use when asked to "service catalog", "what services do we have", "catalog our services", "service inventory", or "who owns what".

• pave-env

  Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".

• pave-golden

  Define a golden path — the opinionated, supported way to do a common developer task (new service, environment, deploy), with concrete steps, templates and tooling. Use when asked for a "golden path", "create project template", "scaffold a new service", or "standardize our setup".

• pave-recon

  Platform reconnaissance — inventory all developer tooling, environments, build systems, and developer workflows for project takeover. Use when asked to "understand the dev setup", "developer tooling assessment", "platform assessment", or "how do developers work here".

• prism-audit

  Frontend audit — bundle size, dependencies, accessibility, performance, component quality. Use when asked for "frontend review", "performance audit", "accessibility check", or "bundle size".

• prism-component

  Implement a reusable, accessible, typed component from a design spec. Use when asked to "create a component", "build a widget", "implement this design", or "reusable UI element".

• prism-dashboard

  Build an internal dashboard with data tables, filters, detail views, and CRUD. Use when asked to build an "admin panel", "internal dashboard", "back office", or "data dashboard UI".

• prism-extract

  Extract repeated values and markup into design tokens and components. Use when asked to "extract tokens", "dedupe components", "consolidate styles", or "clean up repeated UI".

• prism-harden

  Make UI survive real data — overflow, i18n, empty/error/loading states, extreme values. Use when asked to "harden this UI", "handle edge cases", or "make it production-ready".

• prism-recon

  Frontend reconnaissance — map the component tree, routing, state management, build config, and assess quality. Use when asked to "understand this frontend", "frontend assessment", or "what's the UI built with".

• prism-redesign

  Fix an existing UI in a bounded scan, diagnose, fix, re-lint loop. Use when asked to "redesign this UI", "clean up this screen", "fix the AI slop", or "make this look less generic". Lint-driven, max 3 loops, never changes brand direction silently.

• prism-ui

  Implement a complete UI screen or feature from a Form visual spec. Use when asked to "build a page", "implement this screen", "build the frontend for this feature", or "create this UI".

• prism-variants

  Generate 3-5 side-by-side variants of one UI component, screenshot each, compare, fold the winner in. Use when asked to "try variants", "explore options for this component", "show me alternatives", or "A/B this component visually".

• proof-api

  Build API test suites — endpoint testing, contract testing, load testing for REST/GraphQL/gRPC APIs. Use when asked to "test this API", "API tests", "endpoint testing", "contract tests", or "load test".

• proof-audit

  Audit test suite health — find flaky tests, slow tests, coverage gaps, and testing anti-patterns. Use when asked to "audit tests", "fix flaky tests", "why are tests slow", "test health", or "improve test suite".

• proof-e2e

  Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".

• proof-recon

  Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".

• proof-strategy

  Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".

• relay-audit

  Audit an existing CI/CD pipeline for slowness, security issues, and reliability gaps. Use when asked to "audit pipeline", "why is CI slow", "pipeline review", or "deployment review".

• relay-deploy

  Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".

• relay-docker

  Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".

• relay-pipeline

  Build a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".

• relay-recon

  Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".

• spine-api

  Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".

• spine-design

  Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".

• spine-perf
• spine-recon
• spine-review
• spine-service
• tonone-doctor
• touch-app
• touch-audit
• touch-feature
• touch-recon
• touch-release
• vigil-alert
• vigil-check
• vigil-incident
• vigil-instrument
• vigil-recon
• volt-driver
• volt-firmware
• volt-ota
• volt-power
• volt-recon
• warden-audit
• warden-harden
• warden-iam
• warden-recon
• warden-threat

Subagents (15)

• apex

  Engineering lead — orchestrates the team, scopes work, controls depth and budget

• atlas

  Knowledge engineer — architecture docs, ADRs, API specs, system diagrams, onboarding

• cortex

  ML/AI engineer — LLM integration, prompt engineering, RAG, evals, and AI feature design for production

• flux

  Data engineer — databases, migrations, pipelines, data modeling

• forge

  Infrastructure engineer — cloud services, networking, IaC, cost optimization

• lens

  Data analytics & BI engineer — dashboards, metrics design, reporting, data storytelling

• pave

  Platform engineer — developer experience, golden paths, service catalogs, environment management, internal tooling. Builds what removes friction for the team that exists.

• prism

  Frontend & DX engineer — translates Form's design system into production UI components, pages, and internal tools

• proof

  QA & testing engineer — test strategy, E2E suites, integration testing, test infrastructure, flaky test triage

• relay

  DevOps engineer — CI/CD, deployments, GitOps, developer experience

• spine

  Backend engineer — APIs, system design, performance, distributed systems

• touch

  Mobile engineer — native iOS/Android, cross-platform, app stores, mobile performance

• vigil

  Observability & reliability engineer — SLOs, alerting, instrumentation, incident response. Writes configs and runbooks, doesn't produce roadmaps.

• volt

  Embedded & IoT engineer — firmware architecture, microcontrollers, OTA updates, edge computing, device protocols

• warden

  Security engineer — IAM, secrets, threat modeling, hardening, auth, and supply chain security

Hooks (2)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/team/apex/hooks/apex-decisions.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/team/apex/hooks/apex-guard.js"

Similar plugins