xiaolai

Use when scoring or writing Codex CLI artifacts — covers .codex/config.toml schema, .codex-plugin/plugin.json, .agents/skills/ layout, Codex hook events, AGENTS.md hierarchy, marketplace.json, and the agents/openai.yaml sidecar. Refreshed 2026-08-02 against…

The 50 rules of natural language programming. Loaded when writing, reviewing, or improving any NL artifact — skills, agents, commands, rules, hooks, prompts, plugins, and the project memory file (CLAUDE.md / AGENTS.md / GEMINI.md). The definitive style guide…

Use when scoring NL artifact quality, applying penalties, or calibrating lint judgment — contains the 100-point rubric with penalty tables per artifact type. Four worked calibration examples (Excellent Agent / Rewrite Agent / Excellent Rule / Weak Rule) live…

Universal NL programming conventions — SKILL.md open spec (agentskills.io), AGENTS.md as canonical universal memory file, vague-quantifier list, prompt engineering layers, naming conventions, the override system. Tool-specific schemas live in…

The 50 rules of natural language programming. Loaded when writing, reviewing, or improving any NL artifact — skills, agents, commands, rules, hooks, prompts, plugins, and the project memory file (CLAUDE.md / AGENTS.md / GEMINI.md). The definitive style guide…

Use when scoring NL artifact quality, applying penalties, or calibrating lint judgment — contains the 100-point rubric with penalty tables per artifact type. Four worked calibration examples (Excellent Agent / Rewrite Agent / Excellent Rule / Weak Rule) live…

Use when scoring or writing Codex CLI artifacts — covers .codex/config.toml schema, .codex-plugin/plugin.json, .agents/skills/ layout, Codex hook events, AGENTS.md hierarchy, marketplace.json, and the agents/openai.yaml sidecar. Refreshed 2026-08-02 against…

Use when scoring or writing Claude Code artifacts — covers .claude/ paths, plugin.json schema, command + agent + skill frontmatter, CLAUDE.md, hook events, hooks.json format, settings.json, LSP, monitors, memory file conventions, and the Claude Code built-in…

Audit the book-level callback graph that tracks setup → payoff edges across chapters. Verifies every planted anchor has its declared downstream payoff and every payoff still has its upstream plant. Catches orphaned plants and orphaned payoffs. Reads…

Build a structured responsibility-laundering case file from a historical, political, legal, corporate, war, or AI event.

Turn approved case files into chapter architecture for serious trade nonfiction.

Diagnose a chapter against the 10 reader-experience values in rule 12 (5 core + 5 craft) and build a defect map naming which values fail, with cited prose evidence, and recommending one of the five treatment classes from rule 08. Output is…

Prepare citation-ready notes for drafting, fact-checking, and legal review.

Audit chapter prose for verbose inline `[CITE:]` markers that violate rule-13's slug-only invariant. Inline `[CITE:]` brackets must carry only card slugs (separated by `;` for multi-source claims); full citation apparatus lives in the source-ledger card and…

Audit the book's cognitive arc — the discriminations and concepts the reader acquires chapter by chapter — against the actual prose. For each discrimination, verifies introduction, consolidation, and application in every required chapter. For each concept,…

Audit a chapter against its declared per-chapter contract (Hoare triple of reader-state pre/postconditions) and verify the chapter delivers the declared `knows`, `can_discriminate`, `feels`, and `primed_for` slots. The `feels:` slot resolves through rule 12…

Audit a generated candidate EOU set for boundary quality, minimality, overlap, authority, operational value, and governance risk.

Audit value_invocations in run traces for EOUs with classification.judgment_authorized:true. Verifies invocations against the captured_workflow's declared priority (no F15), checks for drift over multiple runs (no F16), detects hallucinated value ids (no…

Audit EOU specs for Foundry V2 faceted classification, authority limits, schemas, validation, failure modes, trace, blast radius, and responsibility ownership.

Synthesize a Stage 0 captured_workflow (D2.4 step 1–5 outputs + per-app constitutional domain_values layer) from a user goal, structured 5-role reference set, and constraints. For users entering an unfamiliar craft domain who cannot articulate a workflow…

Generate a minimal, ranked candidate EOU set from a messy workflow using Foundry V2 constraints. Candidates are proposal-only and cannot be activated.

Audit a generated candidate EOU set for boundary quality, minimality, overlap, authority, operational value, and governance risk before any candidate advances to specification. <example> Context: A generation run has just produced a candidate set; the owner…

Audit value_invocations in run traces for EOUs with classification.judgment_authorized:true. Verifies invocations against the captured_workflow's declared priority (no F15), checks for drift over multiple runs (no F16), detects hallucinated value ids (no…

Audit an EOU spec — classification, authority, validators, failure modes, trace, blast radius, responsibility. <example> Context: Auditing an EOU before promoting it to active. user: "$eou-audit eou-diagnose" assistant: "Loading spec + governance + maturity…

Build or update MCP server/client integrations for VMark. Use when configuring MCP servers, adding MCP tools, or updating MCP-related docs and settings.

E2E testing expert for Tauri applications using Tauri MCP server. Use when testing running Tauri apps - session management, webview interaction, IPC verification, screenshot capture, and debugging. ALWAYS use tauri_* tools, NEVER Chrome DevTools MCP for Tauri…

Translate VMark documentation and app strings to all 9 supported locales with subagent-driven audit, proofreading, and cultural polish. Use when adding or updating website pages, React locale JSON (src/locales/en/*.json), or Rust locale YAML…

Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.

Audit an implementation against a plan (dev-docs/plans/*). Use when a user asks to check for gaps, logic errors, or missing tests relative to a plan or Work Items.

Verify a completed implementation against a plan by running gates and checking acceptance criteria. Use when the user asks to verify work items or confirm completion.

Create comprehensive implementation plans and write them to plan files. Use when the user asks for a plan, comprehensive plan, systematic workflow design, or wants decisions documented in a plan file.

Implement or modify VMark React UI with project conventions (Zustand selectors, Tailwind v4, shadcn/ui). Use for components, hooks, stores, and UI behavior changes.

Use when creating, editing, or reviewing a cc-suite advisor agent (a value-over-rules persona under `.cc-suite/agents/`). Covers system-prompt phrasing, model choice, tool restrictions, working-dir scoping, budget/turn limits, and the file format. Use…

Full audit→fix→verify cycle: Claude audits, Codex fixes, Claude verifies. Repeats up to 3 rounds until all issues are resolved or the user stops. Claude does all code reading and judgment; Codex does all file editing.

Ask Claude Code to audit a file or set of files and return structured findings. Claude reads the code with fresh eyes and independent judgment — Codex does not self-review. Supports mini (5-dimension) and full (9-dimension) depth.

Canonical reference for Claude Code plugin artifact schemas, hook events, frontmatter fields, and naming conventions. Used to inject domain knowledge into Codex audit prompts. Run /cc-suite:refresh-knowledge to update from latest docs.

Send a bug or failing test to Claude Code for root-cause analysis and fix. Use when you've hit an error you can't trace, a test is failing for unclear reasons, or a behavior is wrong and the cause is deep in the codebase.

Delegate an implementation task to Claude Code. Use when you want Claude to write, edit, or refactor code directly in the project. Claude has full read/write access and will make the changes autonomously.

Ask Claude Code to produce an implementation plan before you write code. Use when the task is complex, touches multiple files, or has unclear requirements. Claude returns a numbered step-by-step plan with file paths and interfaces — you implement it.

Delegate a code review task to Claude Code via the claude_code MCP tool. Use when you want Claude's judgment on architecture, security, correctness, test coverage, or code quality for files you've just written or modified.

Use when generating or auditing documentation in Docusaurus format — covers config, directory structure, frontmatter conventions, and build commands.

Use when generating or auditing documentation in MkDocs format — covers config, directory structure, frontmatter conventions, and build commands.

Use when generating or auditing documentation in plain Markdown format — covers config, directory structure, frontmatter conventions, and build commands.

Use when generating or auditing documentation in Sphinx format — covers config, directory structure, frontmatter conventions, and build commands.

Use when generating or auditing documentation in VitePress format — covers config, directory structure, frontmatter conventions, and build commands.

Use when writing, auditing, or generating documentation for projects in unsupported languages — covers docstring conventions, API doc extraction, and generic heuristic patterns.

Use when writing, auditing, or generating documentation for Go projects — covers docstring conventions, API doc extraction, and Go-specific patterns.

Use when writing, auditing, or generating documentation for Python projects — covers docstring conventions, API doc extraction, and Python-specific patterns.

Prepare a human bulk-approval of the whole approvable review backlog — show what would be promoted to canonical, take an in-session confirmation, then hand the human the single pre-filled `gazette approve --all --by human` line to fire themselves. Use when…

Let Codex (via cc-suite) deliberate over the bureau review queue as the user's representative — read each unapproved claim, recommend approve or hold, and either hand the human the exact approve command (advisor) or, only where the workspace opted the `codex`…

Orientation for the bureau plugin — the records-office model, the capture → compile → review gate, the trust tiers, the crew, and which bureau: command serves which intent. Read this FIRST before using any bureau: command, or whenever working in a repo that…

The human double-check gate for AI-written memory. Show every cabinet claim not yet approved — with its provenance and automatic check result — and let the human promote it to canonical or reject it. Use when running bureau:review, or when the user asks to…

Answer from the bureau canon with citations and trust tiers — read dossiers as memory, honor each page's status, and never present an unverified claim as fact. Use when running bureau:query, or when the user asks what the project knows / what was decided /…

Sweep the dossiers for semantic inconsistencies that the press's structural check cannot see — free-text contradictions, superseded claims, undocumented gaps, and vocabulary drift. Use when running bureau:lint, before a milestone, or when the user asks to…

Record an architecture decision as a MADR ADR page in the canon. Use when running bureau:adr, or when the user asks to write/record an ADR or an architecture decision, or to supersede a prior decision. Authors a proposed page only — never approves.

Write a faithful, append-only minute for an AI session — intent, decisions, changed files, open threads, and a transcript pointer. Use when filing a session into a bureau workspace (e.g. via bureau:file-session), or when the user asks to record/minute the…

Router skill for Anthropic's news + research feeds — auto-refreshed daily from anthropic.com/news and anthropic.com/research. Use when the user asks about TIME-SENSITIVE Anthropic content: model launches ("did Claude X just release?"), product announcements,…

Router skill for Claude Cowork — the enterprise multi-cloud surface and Office agents. Cowork covers Claude for Work deployed on third- party clouds (Amazon Bedrock, Microsoft Foundry, LLM gateways), enterprise SSO, telemetry, the M365 connector, and policy…

Router skill for Claude Connectors (the user-facing MCP integration surface on claude.com), Claude Desktop extensions (MCPB packaging), MCP Apps for Claude Desktop with their visual + interaction design guidelines, the directory of pre-built integrations…

Router skill for Claude Code (the CLI tool itself). Contains intent hints and a dispatch table that maps a user's question to the surface-specific deep-reference file Claude should Read next. Use when the user asks about Claude Code internals: editing…

Router skill for Anthropic platform-side features that sit above the raw Messages API: Agent Skills format (the spec for `.skill` packages used by platform-managed agents), MCP connectors hosted by Anthropic, tool use (computer use, code execution, bash tool,…

Router skill for the Anthropic Messages API and adjacent surfaces (admin endpoints, compliance, beta features, models catalog) hosted under platform.claude.com/docs/en/api/. Use when the user asks about: POST /v1/messages, tool_use / tool_result blocks,…

Router skill for the Claude Agent SDK — Anthropic's libraries for building autonomous AI agents that wrap the Claude Code CLI runtime. Ships in TypeScript (`@anthropic-ai/claude-agent-sdk` on npm) and Python (`claude-agent-sdk` on PyPI). Covers `query()` /…

Router skill for the Model Context Protocol (MCP) open spec, covering the protocol itself (JSON-RPC framing, capabilities, lifecycle), the client and server roles, the transport layers (stdio / streamable HTTP / SSE), and the core primitives (tools,…

Enforce coverage thresholds AND test quality — coverage without behavioral assertions is meaningless.

Global TDD governance policy. Enforces plan-first development, behavior-driven test quality, and strict completion gates.

Produce findings-first code review with severity ordering, test-gap findings, and test-quality audit.

Orchestrate strict TDD implementation across planner, test designer, spec adversary, implementer, coverage auditor, mutation auditor, and reviewer subagents.

Build a comprehensive test matrix for changed behavior with explicit assertion strategy per case.

Per-language catalog of test runners, coverage tools, coverage formats, mutation tools, and dry-run probe commands. Use when detecting a repository's test tooling or configuring a lane for any language.

Initialize workspace TDD Guardian config — detect test lanes, verify each by dry-run probe, and write the lane configuration.

Test-level taxonomy — which behavior belongs in a unit, integration, e2e, or contract lane, how lanes bind to gate triggers, and how each lane participates in coverage. Use when designing a test matrix, configuring lanes, or deciding where a given test should…

Use to deeply analyze core architecture — entry points, module boundaries, dependency graph, data flow, and structural patterns. Part of the grill deep-dive phase. Also useful standalone when suspecting circular dependencies, inappropriate coupling, or…

Core conventions for all grill analysis skills — output formatting, severity ratings, evidence standards, and untrusted-input handling. Load whenever a grill analysis skill is active.

Use to hunt for edge cases, race conditions, boundary values, partial failures, and implicit assumptions across a codebase. Part of the grill deep-dive phase under Paranoid Mode. Also useful standalone after a production incident from unexpected input, to…

Use to analyze error handling, logging, observability, and configuration management across a codebase. Part of the grill deep-dive phase. Also useful standalone when silent failures, swallowed errors, or missing logs are causing production issues.

Use for initial codebase reconnaissance — quickly survey project structure, tech stack, config files, and existing documentation to establish context before deeper analysis. Always the first skill run during a grill review, and also useful standalone when…

Use when the user asks to grill, roast, audit, interrogate, deep-review, or do a multi-angle architecture review of a codebase or directory. Orchestrates 4-6 specialized analysis skills (recon, architecture, error-handling, security, testing, optionally…

Use to analyze the security surface of a codebase — authentication, authorization, input validation, secrets handling, and dependency vulnerabilities. Part of the grill deep-dive phase. Also useful standalone before an external pen test or security audit, to…

Use to analyze test coverage, test quality, CI/CD setup, and testing infrastructure. Part of the grill deep-dive phase. Also useful standalone when onboarding to a new project and needing to know which parts have coverage and which are completely untested.

Hunt an argument's silent load-bearing premises and the boundaries where its claim breaks — hidden assumptions, over-generalization, boundary failures, and base-rate/context-transfer errors. Part of the reason-grill deep-dive.

Core conventions for all reason-grill analysis skills — the calibration gate, severity scale, repair-cost tags, finding format, three-finding budget, and untrusted-input handling. Load whenever a reason-grill analysis skill is active.

Red-team an argument — build the strongest steelmanned case against the thesis and test whether the argument survives it. Part of the reason-grill deep-dive; also useful before defending a position, to surface the objections it fails to pre-empt.

Test whether an argument's premises are true, supported, and calibrated — unsupported claims stated as fact, confidence miscalibration, cherry-picking, correlation-as-causation, unfalsifiable claims. Part of the reason-grill deep-dive.

Test whether an argument's framing is honest and how it behaves under objection — motte-and-bailey structure, dodged objections, loaded framing, authority/emotion substituting for reasoning, and uncalibrated certainty. Part of the reason-grill deep-dive.

Test the validity of an argument's inference — does the conclusion follow if you grant the premises? Hunts non-sequiturs, circularity, equivocation, and quantifier slips. Part of the reason-grill deep-dive.

Use when the user asks to grill, roast, stress-test, red-team, pressure-test, or deep-review an argument, claim, essay, proposal, memo, or piece of reasoning. Maps the claim, attacks it from five adversarial angles (logic, evidence, counter, assumptions,…

Map an argument before critique — extract the central claim, explicit and implicit premises, inference structure, claim type, and evidence offered. Runs first in a reason-grill interrogation; also useful standalone to disentangle what a piece of writing is…

Core conventions for all mac-it-guy-pro commands and agents — the safety contract, plain-language rules, report formats, and state file layout. Load before any IT task (checkup, cleanup, organize, fix, automate, backup, onboard).

Use when the user wants help looking after their Mac — a health checkup, reclaiming disk space, organising files, diagnosing a problem in plain language, setting up backups, fixing Wi-Fi or a home network, automating a repetitive chore, or understanding what…

Decision logic for home network work — isolating whether a problem is the device, the Wi-Fi, the router, or the ISP before spending money; the fix ladder from free to hardware; router and mesh buying judgement; and the boundaries of whose network may be…

How the IT guy remembers, refreshes, and retires what it knows about this machine — the profile schema, provenance classes, expiry by evidence, the belief ledger, demotion to history, the visit log, and undo manifests. Load when reading, writing, reviewing,…

Exact macOS commands for IT diagnostics and safe actions — disk, memory, startup items, updates, Time Machine, battery, SMART, duplicate detection, Trash-based deletion, HEIC conversion, photo dates, launchd scheduling. Load before running any diagnostic or…

Decision logic for building a personal unrestricted-internet connection from a censored network — which architecture to use (CDN-fronted vs direct), which protocols work and which are detectable, and the boundaries of what to help with. Load before any…

The micro-product contract for the IT Guy toolbox — acceptance criteria, directory layout, README template, registry schema, dry-run requirement, double-clickable wrappers, the evolution ladder, and the pattern catalogue used to offer a user automations they…

How the IT guy explains rather than just fixes — the two teaching modes (just-in-time and deliberate study), the learning-map structure, grounding lessons in the user's own measurements, depth scaling, and the pull-not-push rule. Load before any…