Run local CI via the in-tree dev build of local-ci (pnpm local-ci-dev) to verify changes to this repo before completing work. Runs pnpm local-ci-dev run --all in the background, watches the log for step failures, and retries failed runners after fixes. Use before reporting work as complete, or whenever the user asks…
PromptScript language expert for reading, writing, modifying, and troubleshooting .prs files. Use when working with PromptScript syntax, creating or editing .prs files, adding blocks like @identity, @standards, @restrictions, @shortcuts, @skills, or @agents, configuring promptscript.yaml, resolving compilation errors…
Write or modify Rust code in the Neo CLI under neo/ - crate conventions, the error-as-LLM-repair contract, output prefixes, and interactive-vs-CI (--ci) behavior. Use when editing any neo/ .rs file, adding a subcommand or JSON field, wrapping a subprocess, or writing any user-facing error. This is Rust, not NeoHaskell…
Stage playbook for executing steps of the change formula v2 (ADR-0075) — the 5-step molecule that takes a request from spec to merged PR. Use when claiming or executing any bead poured from the change formula (spec, spec-approval, build, verify, pr), when parking a stuck step, or when recording a spec approval. Covers…
Orchestrate a NeoHaskell change end-to-end through the spec-gated pipeline - intake to merged PR with exactly two human gates. Use when implementing a feature, fixing a bug, or running any request that should produce a PR.
ANALYSIS SKILL — Analyze any repository and generate AI-ready configuration — AGENTS.md, copilot-instructions.md, skills, CI workflows, issue templates. WHEN: "make this repo ai-ready", "set up AI config", "add copilot instructions", "prepare this repo for AI contributions", "generate AGENTS.md". INVOKES: glob, grep…
Answer questions about using AI Primitives Hub and authoring bundles. Use this skill whenever the user asks about bundles, collections, hubs, profiles, sources, scopes, marketplace, repository installation, deployment manifests, source scaffolding, collection schemas, validation errors, publishing, or any AI…
Performs thorough code reviews following best practices. Use when reviewing pull requests, checking code quality, or ensuring coding standards compliance.
A persistent local-only memory system for AI coding agents. Two files, one idea — AGENTS.md (committed, shared) + .agents.local.md (gitignored, personal). Agents read both at session start, update the scratchpad at session end, and promote stable patterns over time. Works across Claude Code, Cursor, Copilot, Windsurf.…
Persistent local-only memory for AI coding agents. AGENTS.md (committed) + .agents.local.md (gitignored) = context that persists across sessions. Read both at start, update scratchpad at end, promote stable patterns over time.
Answer at the decision level - plain language the user can judge and decide on, with code, file paths and line numbers kept below a marked line. Armed for one session at a time and off by default. Use when the user types /decision-layer, or asks to work at the decision level, to stop mixing code into answers, to hide…
Review pull requests in adrkit for actionable defects and conflicts with governing architecture decisions. Use during Copilot code review to inspect changed paths, retrieve relevant ADR context through the adrkit MCP server, and produce evidence-backed inline findings.
Use when auditing an existing codebase, documentation set, plans, RFCs, or git history for architecture decisions that were made but never recorded as ADRs, and when triaging potential records before drafting them.
Use when planning, designing, reviewing, or changing code in a repository that keeps ADRs (usually docs/adr) — to load the decisions that already govern the work, check a plan or diff against them, or record a new decision. Also use when a choice feels already-settled and you cannot find where it was settled.
LLM and cloud cost awareness — model tiering, token budgets, right-sizing, and when a cheaper model suffices. Trigger before finalising any architecture that calls LLMs, before scaling a workload, or when a cost estimate is needed.
Scaffold and govern an MCP server as a bounded tool seam. Defines which tools the agent may call, enforces the principle that agents call tools and tools call infrastructure. Trigger when adding or reviewing an MCP server in an agent system.
Bootstrap or harden a project's operating model for mixed human and AI delivery teams. Use when starting a repository, adopting an agent harness, defining authority and risk tiers, coordinating parallel agents safely, binding evidence and review to an exact candidate, or correcting fragmented rules that prevent…