craigvandotcom
@craigvandotcom
Public Skills
supabase
by craigvandotcom
Supabase development. Use when writing or reviewing SQL and migrations, designing or modifying database schema, working with RLS policies, optimizing queries or indexes, using the Supabase CLI (supabase db, supabase migration), generating TypeScript types from schema, debugging database or auth issues, or touching lib/db.ts, lib/supabase/, or supabase/migrations/. NOT for UI component work (use ac-polish/references/ui-checklist.md for correctness, ui-elevate for polish), general React patterns or device storage (use capacitor), or auth UI flows (use CORE + auth spec).
ac-implement
by craigvandotcom
'Work an ac2 epic''s bead queue as a SWARM — you coordinate, spawned workers claim, flight check, RED, implement, self-review, close gate, next bead. Defaults to width 3, uncapped, until the qualifying beads are exhausted. Triggers: "ac2 implement", "work the ac2 beads", "run the ac2 loop", "swarm the ac2 beads", "ac2 swarm".'
ac-human
by craigvandotcom
'The human command center — sit down and keep the factory moving. Opens with the full board (invokes ac-board), then drives the docket: only work at a human gate, on a silver platter, exit-first. Optional gated tidy/align pre-pass. Triggers: ''human session'', ''what needs me'', ''sit down'', ''unblock work'', ''my action items'', "what''s blocked on me", ''keep the factory moving'', ''human next''. ''Unblock'' means a HUMAN gate only — NOT a technical blocker (use ac-backlog to file it, or ac-triage for inbound signal), and NOT doing the work itself (use ac-implement).'
ac-board
by craigvandotcom
'Read-only pipeline board — the whole factory in one glance: human gates split into decisions and actions, plans by stage, beads by stage, WIP plus CI health, and the agents now active. Observes only; never writes, closes, promotes, or prompts. Triggers: ''board'', ''dashboard'', ''show the board'', ''state of the pipeline'', ''pipeline status'', "what''s the factory doing", ''WIP status'', ''board overview'', ''full board''. To ACT on human gates use ac-human; to reconcile or re-prioritize use ac-align.'
ac-distribute
by craigvandotcom
Use to SHIP a built app out the door — push a signed build to TestFlight (closed beta), or submit a release to the App Store. The ship-OUT stage of the ac-* pipeline — position per ac-pipeline/references/stage-table.md; the hand-off target of the ac-publish release gate. Triggers on "ship to testflight", "push a build", "release to app store", "cut a build", "distribute the app", "submit for review". For pulling crashes/feedback BACK IN → ac-triage. For proving the build first → ac-qa. For the full production release gate (version bump, proof, tag) before this → ac-publish.
ac-pipeline
by craigvandotcom
'The pipeline CONSTITUTION + the operating contracts. Constitution: Invariants (hold at any model capability) + Calibrations (each naming the telemetry that retires it) — read before writing, tuning or reviewing any lean-pipeline skill or script. Triggers: "pipeline constitution", "pipeline invariants", "tune the pipeline", "ac-pipeline". Operating contracts: the owner-hosted runtime canons every ceremony consults live in references/ of this same skill (commit-discipline, delegation-contract, run-ledger, run-id, verification-gate, board-scan, risk/consensus/disposition, degraded-mode, shell-guardrails), the QA methodology lives in ac-qa/references/qa-shared.md, and the deterministic gates live in scripts/ (beads-closed-gate, validate-qa-run, close-evidence-check, board-truth). NOT for RUNNING anything: one stage (that stage''s own skill), or a gate/script this skill merely hosts (the calling ceremony fires it).'
ac-prove
by craigvandotcom
Use to obtain-or-produce a tip-valid full-suite proof for a commit — the shared freshness-probe/dispatch/fix-forward primitive every ship path calls instead of re-implementing its own CI-trust logic. Wraps scripts/ci/publish-checkpoint-gate.mjs (freshness) + quality-gate.yml's reason=prove dispatch (the full leg). Three modes — probe (read-only), ensure (probe + dispatch-if-stale), ensure --fix-forward (blocking, ship-path only). Triggers on "prove this commit", "ac-prove", "is main green", "get a fresh checkpoint", "prove the tip", "gate on a full proof". NOT for running tests locally (use testing) or for reading CI state as a board pane (use ac-board).
ac-land
by craigvandotcom
"The closing ritual — runs LAST, after ship. To land = leave it clean AND wiser: TEARDOWN (kill spawned tasks, sweep orphaned waiters, release+deregister Agent Mail, clear temp, clean tree) plus LEARN (retrospective + reflect + system compounding). Triggers: 'land the session', 'bead land', 'close out the bead work', 'wrap up session', loop exit. NOT for standalone lesson capture without bead-work context (that is reflect)."
ac-publish
by craigvandotcom
'The ac2 ship gate — obtain a proof via ac-prove, assert its REQUIRED JOBS ACTUALLY EXECUTED, then version, tag the proven SHA and hand off to ac-distribute; labels external escapes with a catch-stage on arrival. Triggers: "ac2 publish", "ship the ac2 batch", "release this batch" — run by the operator once a batch is ready to ship. NOT the proof itself (ac-prove), NOT the store upload (ac-distribute).'
context-engineering
by craigvandotcom
The canonical context + memory architecture for the AI-native org. Use when deciding WHERE or HOW to save something durable (a lesson, decision, rule, recipe, doc), when asked "where should this live", "how do we store/remember X", "what loads when", "how does memory actually work", or when designing/auditing anything touching memory, CLAUDE.md/AGENTS.md, CORE, skills structure, hooks, or retrieval. How the compounding system RUNS — the three lanes, their executors, cadence, drains, health surface ("memory pipeline" questions) — lives in references/operations.md. NOT for executing a save at session end (that is reflect), cross-session synthesis or memory lint (that is dream), or plain file/folder organization on disk (no skill needed).
agent-mail
by craigvandotcom
'Multi-agent coordination via Agent Mail — registering a session identity, reserving files before editing a shared checkout, releasing + self-deregistering at exit, build slots, messaging. Use when starting any session that will commit code alongside concurrent agents, when hitting FILE_RESERVATION_CONFLICT or a pre-commit guard block, or when choosing between a minted Tier-1 identity and the FoggyCreek chore fallback. Triggers: "register agent identity", "reserve files", "file reservation", "agent mail", "macro_start_session", "release reservations", "deregister agent", "build slot", "FoggyCreek". NOT for commit discipline itself (that is ac-pipeline references/commit-discipline), for choosing a delegation stance (ac-pipeline references/delegation-contract), or for actual email/outbound comms (ac-distribute).'
snippet-skill
by craigvandotcom
fixture
demo
by craigvandotcom
fixture skill for 28-citations (must go RED)
legacy-skill
by craigvandotcom
fixture skill citing retired machinery
skill-builder
by craigvandotcom
Use when creating, editing, refactoring, or cleaning up skills — dieting a SKILL.md to its spine, extracting references/, centralizing shared blocks, optimizing description cost, building an orchestrated /command or scheduled workflow (run ledger, phases, quality gates), scoring subagent prompts against a rubric, auditing the skill registry for trigger collisions, duplicates, and doc-disk drift. Triggers on "create a skill", "build a skill", "refactor this skill", "clean up our skills", "skill hygiene", "diet this skill", "extract to references", "convert to a skill", "description budget", "build a workflow", "create a /command", "turn this SOP into a command", "design a pipeline command", "workflow builder", "enhance prompts", "improve subagent prompts", "score my prompts", "prompt quality review", "rate this prompt", "registry audit", "audit the skill registry", "registry hygiene", "dedup the skills", "skill collision check", "clean up agent-compounds". NOT for a canned prompt (use jef-prompts).
dream
by craigvandotcom
Run the dream session — the org's deliberate self-improvement review, human-run and unscheduled. Use when asked to "run the dream cycle", "dream", "synthesize the week's lessons", "lint the memory substrate", "review dream proposals", "review the dream dockets", or "what did the dream cycle find"; also when a docket-review bead is open. The session reads both ranked dockets (memory-rollup — knowledge substrate, friction-rollup — friction ledger, both computed live), rules each item with the human, and emits approved work as task beads. NOT for capturing one session's lessons (that is reflect) or saving a single item (that is context-engineering routing).
ac-triage
by craigvandotcom
Use to pull operational + user signal BACK IN from external systems — crashes, errors, logs, beta feedback, externally-filed issues — cluster it, and route real findings by shape — defects to beads, recurring feature/experience themes to the backlog pool (as candidates the human approves). Fetches from Sentry, App Store Connect (TestFlight feedback), Supabase logs, GitHub Issues, PostHog, store reviews. The inbound counterpart to ac-distribute. Triggers on "triage crashes", "check sentry", "any new errors", "pull feedback", "triage github issues", "what's breaking in prod", "triage production signal", "review crash reports". Headless — runs anywhere, scheduled. NOT for triaging the bead board itself — that is bv (read-only) or ac-polish (bead mode).
ac-tidy
by craigvandotcom
'Pipeline housekeeping — reconcile backlog, plans and beads against live state: archive what is done, repair statuses and readiness labels, remove invalid labels, close moot proposals, and file a bead for anything that needs a human. Interactive on request; the nightly heartbeat runs it headless. Triggers: ''tidy the pipeline'', ''clean up the backlog'', ''reconcile plans and beads'', ''archive what is done'', ''fix bead labels''. NOT for strategy fit or pool → active promotion (ac-align), reading the board (ac-board), the human docket (ac-human), or code cleanup (ac-hygiene).'
jef-prompts
by craigvandotcom
'A curated library of high-leverage one-shot prompts — the Jeffrey-Emanuel jef pack plus local additions. Triggers: "/jef-prompts <hint>", "give me a prompt for", "is there a prompt for", "bug hunting prompt", "planning prompt", "performance audit prompt", "refactor prompt", "find a prompt". RETRIEVES a canned prompt — NOT for scoring or improving prompts already written (skill-builder's prompt rubric) or authoring skills (skill-builder).'
ac-plan
by craigvandotcom
'Turn an idea into ONE ac2 plan file — problem, approach, deliverables, assumptions, risk + sequence, out-of-scope, and a success criterion that can come out FALSE. Explorers optional, chosen by size. Triggers: "ac2 plan", "write an ac2 plan", "plan this for ac2". Hands off to ac-polish.'
ac-beadify
by craigvandotcom
'Compile an APPROVED ac2 plan into lean beads — the four-section ac2 schema, a wired dependency graph, and plan retirement. Refuses any bead whose ACs name no executable probe (no probe, no bead). Triggers: "ac2 beadify", "compile the plan into ac2 beads", "ac2 beads from plan". To grade the result use ac-polish.'
ac-review
by craigvandotcom
'The hand-run independent review: ac-review <range> over a range the operator names — nothing triggers it and no batch runs it. Three lenses (correctness against the plan and the bead ACs, test-quality, and one risk lens the diff chooses) report against one bar: a demonstrated failure in ordinary operation, or a violated acceptance criterion, with a reproducing command. Every finding routes to Defect (a bead), Hardening (one report line, never a bead) or Nothing; a fresh verifier re-runs each Critical/High before any fix. Reviewers run the validator stance, read-only on the shared tree; reports land in .claude/reviews/. Triggers: ''/ac-review'', ''review the batch'', ''review this range''.'
demo
by craigvandotcom
Agentic tools that compound
reflect
by craigvandotcom
Capture session learnings into the AI-native-org memory substrate. Use at the end of any session, or when asked to "reflect", "capture learnings", "what did we learn", "save lessons", "remember this", "compound this session". Called by ac-land; also runs standalone. NOT for full bead-work closure (that is ac-land), cross-session synthesis/lint (that is dream), or deciding WHERE something durable should live (that is context-engineering).