aaronkendell/dev

Test API endpoints in a workspace using OpenAPI specs, auth tokens from Infisical, and self-healing debugging for common failures

Provision a new app across Cloudflare, Infisical, Neon, Fly, Sentry, Grafana, Upstash and the rest — decide which vendors it needs, create what's scriptable, and print the manual checklist

Stand up a NEW app repo from project-template — config, catalog, design pack, generated DESIGN.md, CI wiring — and hand off to app-provision for vendors. Use when the user says "new app", "scaffold an app", "create the <name> repo", "bootstrap <name>", or asks what a new app needs. Covers the repo side only; app-provision covers Cloudflare/Infisical/Neon/Fly/etc.

How to run a bokendell app repo inside a cloud VM — a Cursor Cloud Agent or a Claude Code cloud session (vs swarm workspace dev on a laptop). Use when starting servers/apps (API, admin, web, mobile/Metro, Inngest, workers, MCP servers), deciding which services a task needs, wiring Infisical/swarm in the sandbox, or exposing something to a phone/browser over a tunnel. On a laptop keep using swarm workspace dev.

Auto-loads the correct pattern docs based on what's being worked on. Triggers when working on golf, portfolio, or hive apps — during planning, development, testing, or code review. Ensures DDD, API, frontend, mobile, and testing patterns are always in context. Use proactively whenever implementing, reviewing, or planning features.

Voice and copy for every word a user reads. Use when writing or reviewing UI strings, empty and error states, buttons, toasts, push notifications, emails, onboarding, marketing headlines, or App Store text. Also use when the user says copy sounds "generic", "AI-written", "off-brand", "slop", or asks about tone, humor, em dashes, microcopy, or naming a button. Companion to the design skill: design owns pixels, this owns words.

Unified design orchestrator for every app (golf/Bagman, portfolio, hive, keepings). Use when building UI components, designing screens, creating mocks, reviewing design compliance, updating design tokens, exploring color palettes or typography, implementing animations/motion, or doing any visual/frontend work. Also use when the user mentions "design system", "make it look better", "fix the UI", "design review", "polish this", "update the theme", or references any app's visual style. Also use when the user says design studio, golf design studio, studio sketch, flow sketch, primitive library, or app-specific design studio. Triggers proactively on ANY frontend/mobile file changes to ensure design compliance. This skill replaces golf-ui and is the primary studio router for every app, including golf.

Inbox + address workflow for design annotations. Lists every open annotation across an app's flows (or filters to one flow), then walks through each — reading the comment + the source file + the flow's decisions.md, making the fix, and posting a reply that marks the annotation addressed. Triggers when the user says: "check comments", "address feedback", "any new design comments", "let's go through the feedback", or invokes /design-comments / /design-address.

Multi-agent taste review for a design flow. Composes /design-verify (structural / HARD-RULES evidence) with parallel passes through /taste-skill, /impeccable:impeccable, /ui-ux-pro-max, and /huashu-design. Each agent writes its findings to swarm-api as annotations tagged with its own author (agent:taste, agent:impeccable, agent:ui-ux-pro-max, agent:huashu). The pin layer's agent badge surfaces who said what. Triggers when the user says: "review the flow", "do a design review", "what would taste-skill say about this", "have impeccable polish-check it", or invokes /design-review.

Visual verifier for design studios. Captures rendered screenshots + DOM + computed styles per artboard via the playwright-cli skill, then audits each one against the flow's decisions.md, packages/ui/HARD-RULES.md, and the design tokens. Findings POST to swarm-api as annotations tagged origin: "agent:verify". Triggers when the user says: "verify the studio", "check this flow's design", "run the visual verifier", "make sure the artboards match my decisions", or invokes /design verify. Use INSIDE Claude Code only — it authenticates as the shared Claude agent identity (/apps/swarm/agents in Infisical) so findings are attributed to the agent persona, not the user.

Use at the START of any substantive dev task to decide how much process it needs — before planning, before building. Classifies the task and loads only the phase skills the task's shape warrants. Also handles explicit /dev <subcommand> invocations (research, plan, build, ship).

Use when the user asks for the dev build workflow to implement a feature from a Linear issue with full TDD, automated testing, code review, and verification. Triggers on /dev build <LINEAR-ID> or /dev build <issue-path> or when the user says "build this", "implement this issue", "start coding GOLF-123". Full lifecycle: branch, worktree, context loading, TDD, API/web testing, 2 code review rounds, lefthook checks, stage files.

Use when the user asks for the dev plan workflow to break a design document into Linear projects and issues. Triggers on /dev plan <app> [initiative-path] or when the user says "break this down", "create issues", "plan this project", "sync to Linear". Reads the design doc, decomposes into projects and issues, writes local markdown files, and syncs to Linear.

Use when the user asks for the dev research workflow to create PRDs, database designs, architecture docs, API specs, and UX mocks for a new feature or app. Triggers on /dev research <app> <idea> or when the user says "research this", "design this feature", "create a PRD", "brainstorm this idea". Combines codebase scanning, brainstorming dialogue, and design document generation into one phase.

Use when the user asks for the dev ship workflow to commit, push, create a PR, update Linear, and optionally merge. Triggers on /dev ship or when the user says "ship it", "commit and push", "create a PR", "we're done". Handles the full git + Linear + GitHub flow.

The bokendell docs contract: where docs live, how to find the right one cheaply, when to update them, and how to distill planning docs on ship. Use when the user says "update the docs", "where does this doc go", "archive this project", "distill", "docs map", mentions MAP.md, or whenever creating/restructuring documentation in any bokendell repo. Also use when the docs-freshness hook reports stale owning docs. Spec lives at docs/planning/docs-context-layer/design.md in the golf repo.

Compatibility alias for the name people still type. The golf design pack now lives in the golf repo at .claude/skills/design/SKILL.md and loads automatically there; the cross-app method lives in dev:design. This file only redirects.

Find OpenAPI specs for every API in the monorepo — both on-disk JSON files and live URLs served by each API

Review files against the project's pattern docs (DDD service/repo, Hono+oRPC API, Awilix DI, testing layers, frontend container/component split, mobile, design app, design studio annotations, CLI, barrels, container-images, AI/Mastra, remote tunnels, etc.) and fix violations so the code follows the patterns exactly. Use this skill whenever the user says "review", "check against patterns", "make this follow the patterns", "review this PR", "fix pattern violations", "audit this against our conventions", "is this DDD-compliant", "does this match the api.md pattern", "review my changes", or invokes a /review style command — even if they don't name a specific pattern doc. Trigger when the conversation mentions specific files to audit OR when the user describes a code-quality / convention-compliance pass with no specific framework named (the skill maps file globs → pattern docs automatically). Use this *instead* of the patterns-reviewer agent for fast, on-demand, interactive review (the agent is for batch/background review during the build phase).

Use when implementing a feature and noticing changes that may be outside the planned scope. Triggers during execution when edits touch different domains, add unplanned features, or modify infrastructure not in the issue spec. Also use when reviewing a diff that seems larger than expected. Helps prevent scope creep during build phase.

How config and secrets reach running code — the zod config boundary, the three injection paths (local, CI, Fly runtime), why a value in Infisical is not yet a value on a machine, and the NEXT_PUBLIC build-time exception. Use when adding a config value, rotating a key, or debugging "it's set but the app can't see it".

The verification loop for any app change — pick the cheapest check that would catch this change breaking, run it, and LOOK at the result. Triggers when the user says "verify this", "prove it works", "run the verification loop", after any non-trivial change, and ALWAYS before declaring a feature done.

Manage dev workspaces — create, stop, start, status, URLs. Use when the user mentions "workspace", "start servers", "stop servers", "which workspace", "what port", or "show URLs".

Work productively inside a workspace — know ports, URLs, env vars, CLI commands, health checks

Bootstrap a workspace from scratch — full lifecycle from zero to running dev environment, portable to cloud workers