Agent Skills

---

name: coco-ads

description: Turn the project you just shipped into a short, polished, shareable launch video (an "ad") using HyperFrames. Use when someone says "/coco-ads", "make a launch video", "brag about this", "turn this into a promo", "make an ad for this", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed. Renders locally.

---

name: coco-cli

description: Install, update, version-check, or uninstall the Coco open-source AI workflow framework via bin/coco.js. Use when setting up Coco on a machine, checking out the pinned release tag into an existing clone, checking the installed version, or removing it. npx cocosuperintelligence is the published path (clones the pin and installs). Triggers on "install coco", "update coco", "set up coco", "coco cli", "uninstall coco".

---

name: coco-diagram

description: Use for architecture, current-state, process, data-flow, medallion, or DP diagrams, including redrawing .drawio and Mermaid sources. Creates branded flowchart, sequence, ER, org, timeline, and chart visuals as standalone HTML/SVG/PNG.

---

name: coco-loop

description: Start a safe, governed autonomous loop from a plain-language goal. Use when the user says /coco-loop, "run an autonomous loop", "keep my build green for N hours", "work on X autonomously for a while", or wants a bounded self-improving loop that proposes fixes and never commits on its own. Turns a vague goal into a readable charter the user confirms, then arms and runs the loop propose-only under the coco-loops governance framework.

---

name: coco-ship

description: Use when finished work needs to reach a coco-managed repository (coco-research/coco or similar) — verifies branch state, commits, pushes through the corporate DLP guard only when actually needed, opens a PR against main, waits for CI, and reports the result. Never merges, never pushes to main directly.

---

name: code-verification

description: Use after every code change, after writing tests, or before marking a task complete, and when the user says verify, quality gate, or audit code. Runs a 7-category mechanical check for TDZ, import, dead code, and mock leakage bugs.

---

name: context-budget

description: Audit token consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations. Use when the context window is filling up too fast or before adding new components.

---

name: design-taste-frontend

description: Use when the user asks for a landing page, marketing site, portfolio, or redesign, not dashboards or data tables. Infers a design read, sets the three dials, picks a real design system, and blocks generic AI patterns at pre-flight.

---

name: dispatching-parallel-agents

description: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

---

name: executing-plans

description: Use when you have a written implementation plan to execute in a separate session with review checkpoints

---

name: expo-api-routes

description: Use when adding server-side API routes to an Expo Router app (+api.ts files) for secrets, database access, third-party proxies, webhooks, CORS, or EAS Hosting deploys. Covers file routing, env vars, and Cloudflare Workers limits.

---

name: find-skills

description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

---

name: finishing-a-development-branch

description: Use when implementation is done and tests pass and the user must choose to merge locally, open a PR, keep the branch, or discard it. Presents those four options, executes the choice, and cleans up the worktree for merge and discard.

---

name: ln-11-opportunity-evaluator

description: Evaluates new product opportunities through demand, channels and economics before committing to build.

---

name: ln-12-product-requirements-builder

description: Defines product requirements, business rules and acceptance criteria for a committed intent; edits product docs only.

---

name: ln-13-interaction-design-builder

description: Designs user flows, interaction states and mockups for a defined product scope; does not implement UI code.

---

name: ln-21-system-design-baseline-builder

description: Defines measurable architecture drivers and constraints before system design; edits architecture docs only.

---

name: ln-22-current-architecture-documenter

description: Documents current architecture from implementation evidence; does not propose a target or audit fitness.

---

name: ln-23-system-design-proposal-builder

description: Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement.

---

name: ln-24-architecture-decision-recorder

description: Records one architecture decision with alternatives, consequences and status; does not design the whole system.

---

name: ln-25-architecture-diagram-builder

description: Creates evidence-backed current or target architecture diagrams; not UI design.

---

name: ln-26-architecture-migration-planner

description: Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them.

---

name: ln-31-delivery-plan-builder

description: Builds dependency-ordered delivery plans from requirements and repository evidence; read-only.

---

name: ln-32-test-strategy-planner

description: Plans risk-based test portfolios and acceptance evidence; does not write or execute tests.