craigvandotcom
@craigvandotcom
Public Skills
wiki
by craigvandotcom
Use when writing, updating, or gardening wiki synthesis pages — concept, entity, topic, or contradiction pages integrating atomic facts into one cited narrative. Triggers on "wiki page", "synthesis page", "seed a wiki page", "garden the wiki", "concept page", "entity page", "contradiction page", "write X up as a wiki page", "dedupe the wiki", "WIKI.md front door", "weekly distillation", "STRATEGY.md decisions log". NOT for saving one fact/rule/decision (context-engineering), session-end capture (reflect), or the weekly cross-session synthesis run (dream).
testing
by craigvandotcom
Use when writing, fixing, or reviewing tests for TypeScript/Next.js code — unit, component, integration, or E2E tests. Triggers on test, spec, coverage, mock, assertion, Vitest, Playwright, React Testing Library (RTL), MSW, flaky test, failing test, write a test, add test coverage. NOT for ad-hoc browser or simulator runs (the ac-qa driver references), pipeline-gated QA (ac-qa, ac-qa), or security/performance sweeps (audit).
multi-model
by craigvandotcom
Use when a task needs a specific AI model or several weighing in on one question — query Claude, GPT, Gemini, Grok or DeepSeek directly, or get a multi-model panel synthesized into one answer on OpenRouter Fusion. Triggers on "query a model", "which model for", "use OpenRouter", "ask GPT/Gemini/Grok directly", "run this on <model>", "ask the experts", "model consensus", "panel of AI models", "second opinion from other AIs". NOT for UI/design options (ui-brainstorm), forensic idea critique (ac-idea-lab), or Anthropic API/model reference (claude-api).
beads-standards
by craigvandotcom
'Use when creating, refining, or reviewing a bead in ANY .beads/ project — choosing a label, deciding refined vs unrefined, writing a human-gate/DECISION bead, wiring blocks dependencies, setting close_reason or defer_until, or picking priority/status. Triggers: "beads standard", "bead template", "human-gate", "DECISION bead", "HUMAN bead", "create a bead", "close reason", "refined unrefined", "wire dependencies", "which label". Canon for every repo with a .beads/ directory (root, every app, agent-compounds, any other task tracking) — not scoped to the agent-compounds ac-* pipeline (that pipeline''s own batch-epic + routing supplement lives in skills/beads-standards/reference/bead-conventions.md; read both inside an ac2 skill). This is the STANDARD, not an executor: to actually refine a bead use ac-polish, to capture one use ac-backlog, to generate a wave use ac-beadify.'
capacitor
by craigvandotcom
Use for ALL engineering decisions when building Capacitor native apps on the shared stack (Next.js static export + React + SWR + Supabase) — load before planning or implementing any UI, navigation, data fetching, auth, storage, lifecycle, or build work. Triggers on "capacitor", "native app", "iOS", "Android", "native feel", "tab switch", "keep-mounted", "WKWebView", "skeleton flash", "SWR cache", "static export", "cold start", "app lifecycle", "Preferences storage", "plugin", "native performance", "background", "app resume", "safe area", "tab navigation", "plugin bridge", "MainActor", "visibility hidden", "display none". NOT for writing or fixing tests (use testing), SQL/schema/RLS/migrations (use supabase), visual or CSS defects (use ui-debug), or accessibility audits (use ac-polish/references/ui-checklist.md).
ac-polish
by craigvandotcom
'Polish a plan, an epic''s bead set, or a code scope to FIXPOINT — a stateless severity-gated reader per round, stamped only against a measured empty diff at round >= 2. One engine, six modes, selected by argument; seams mode traces one object through three lenses (object · flow · boundary), converges on the merged maps, and derives its seams into a plan. Triggers: "ac2 polish", "polish the plan", "polish the beads", "polish this code", "refine the ac2 beads", "run polish to fixpoint", "ac-seams", "study the seams of", "seams plan for".'
ac-align
by craigvandotcom
'Align the execution pipeline against current strategy — audit backlog/plans/beads for fit, sequence, and gaps, and own pool → active promotion (binding versions late, against live strategy). Owns the weekly strategy-align heartbeat. Triggers: ''align pipeline'', ''pipeline alignment'', ''is my pipeline on strategy'', ''audit backlog against goals'', ''what should we plan next''. NOT for what to work on NOW (use ac-board to read the board, ac-human for the gated docket), for working the idea/strategy itself (use ac-idea-lab), for board housekeeping (use ac-tidy), or for codebase cleanup (use ac-hygiene).'
ac-hygiene
by craigvandotcom
'The single code-quality lane — a 5-lens Opus panel (bug hunter, adversary, failure engineer, promise keeper, test warden), minimum 3 rounds for cross-round consensus, scoped to code a user reaches in production. Audits the TEST SUITE as hard as the code: test-quality checks; mutation probes convict hollow tests and trimming counts as much as fixing. Fixes commit directly to main (trunk-direct); deferred findings become an epic of beads. Triggers: ''hygiene'', ''clean up the codebase'', ''iterative review'', ''tidy the code'', ''weekly hygiene run''. NOT for a single-module or single-domain deep dive (the audit checklists now live in ac-review/references/), the skill/agent registry (skill-builder's registry-audit workflow), or pipeline/board housekeeping (use ac-tidy).'
jef-flywheel
by craigvandotcom
Use when learning or applying the agentic build methodology end-to-end — beads (br/bv) and agent-swarm (ntm) setup, coordinating multi-agent work, AGENTS.md conventions. The conceptual/setup layer, not the per-stage pipeline skills. Triggers on flywheel, agent swarm, ntm, br/bv setup, agent coordination, multi-agent development. To convert a plan into beads use ac-beadify; to run a stage use the ac-* skills; for live coordination (identity, file reservations) use agent-mail; for bead canon use beads-standards.
ac-backlog
by craigvandotcom
'Capture ideas into the backlog pool — cohesive grouping (one theme = one wave), shape-routing (small+clear goes straight to a bead), strategy-aware horizon, no version guessing at capture. Also the single-bead intake: one raw idea, bug, observation or decision fork typed live in conversation and filed now as a bead carrying origin:ac-backlog. Triggers: ''add to backlog'', ''capture idea'', ''backlog this'', ''note for later'', ''park this'', ''bead this'', ''file this as a bead'', ''new bead'', ''log a bug'', ''track this item'', ''remember to do X''. For decomposing a whole plan use ac-beadify; for refining existing beads use ac-polish (bead mode); for polling external systems use ac-triage.'
ui-brainstorm
by craigvandotcom
'Use ONLY when the user explicitly wants MULTIPLE divergent design options or several AI models'' opinions on a UI — design ideation, exploring alternatives, or cross-model consensus ranking. Triggers on "ui brainstorm", "design options", "multiple ideas", "explore alternatives", "what would different models suggest", "consensus on this design". NOT for single-track polish of existing UI (ui-elevate), accessibility/compliance audits (ac-polish/references/ui-checklist.md), or visual/CSS bugs (ui-debug).'
ui-elevate
by craigvandotcom
'Use when raising already-working UI to premium quality — the taste layer above correctness. Two modes: app (the authenticated product surface) and site (the public marketing surface). Triggers on "polish this UI", "elevate this screen", "make it feel premium", "level up the design", "polish the landing page", "elevate the homepage", "the website looks like AI slop", "tighten the visuals", "make it production-quality", "audit the design craft". Covers the elevation manifesto, anti-slop critique, visual craft, interaction and feel, perceived performance, and conversion craft, with every edit bounded to the design spec''s tokens. NOT for: functional or correctness defects (ac-polish ui mode), accessibility mechanics (ac-polish/references/ui-checklist.md), React/Next perf internals (capacitor), visual/CSS bugs (ui-debug), or multi-model design ideation (ui-brainstorm).'
ui-debug
by craigvandotcom
Debug UI bugs, CSS styling issues, and unexpected visual behavior in React/Next.js apps. Use when elements render wrong, styles do not apply, or layout breaks across viewports. Triggers on CSS bug, style not applying, layout broken, element misaligned, rendering issue, responsive bug, flexbox/grid issue, visual regression. NOT for premium polish (ui-elevate), a failing visual-regression test (testing, ac-qa), accessibility (ac-polish/references/ui-checklist.md), or performance (capacitor).
ac-qa
by craigvandotcom
'Use when QA-ing an app build through journeys — browser (web shell) or device (native shell). One engine, two workflows: workflows/browser.md (agent-browser — SPA routing, storage/session, service worker, CORS, console, hydration, responsive) and workflows/device.md (agent-device + simctl — real native taps, keyboard, safe-area, splash, plugins, system sheets, deep links, push, appearance). Depth levels, journey reuse, findings=beads, and the conductor/worker evidence protocol are shared. Triggers on "QA the app", "test web app", "browser QA", "device QA", "simulator QA", "test native app", "validate the build", "web smoke test", "native smoke test", "QA on iOS". NOT for writing unit/component/E2E tests (testing), ad-hoc UI bug repro (ui-debug), or visual polish (ui-elevate).'
brainstorming
by craigvandotcom
Pre-planning exploration and ideation using divergent-convergent methodology. Use when exploring ideas before committing to a plan or uncertain which approach to take. Triggers on "brainstorm", "explore ideas", "what are the options", "think through approaches", "before I plan this", "/brainstorm". NOT for UI/design ideation across models (ui-brainstorm), forensic critique of an existing idea (ac-idea-lab), or polling models on one question (multi-model).
ac-idea-lab
by craigvandotcom
Use to deeply work a raw IDEA, framework, concept, or strategy (anything without execution steps yet) — two modes: GENIUS forensic first-principles critique (stress-test, find flaws, distill) and ALIEN paradigm transcendence (escape the frame, cross-domain transplants, expand). Triggers on "review this idea", "stress-test this", "devil's advocate", "critique this concept", "find flaws in this", "first-principles review", "transcend this idea", "go deeper", "push beyond analysis", "alien perspective", "escape local optima", "what am I missing at a deeper level". For a written implementation plan with steps/timelines use ac-plan-lab; for open-ended generation of new options use brainstorming; for a multi-model panel use multi-model.
ghosted
by craigvandotcom
"never mentioned"
real
by craigvandotcom
"mentioned below"
prose
by craigvandotcom
"desc here"
something-else
by craigvandotcom
"a deliberately wrong name"
agent-compounds
by craigvandotcom
Agentic tools that compound
alpha
by craigvandotcom
A minimal skill so the dry-run self-test has a skill to pick.
widget-a
by craigvandotcom
'Use when asked to frobnicate the widget. Triggers on "frobnicate the widget", "polish the widget".'
widget-b
by craigvandotcom
'Use when asked to frobnicate the widget. Triggers on "frobnicate the widget", "clean the widget".'