xiaolai
- 268 skills
- 0 followers
- 918 repo stars
- last month last updated
- ▌ Workflow · xiaolaiOrchestrate strict TDD implementation across planner, test designer, spec adversary, implementer, coverage auditor, mutation auditor, and reviewer subagents.
- ▌ Lane Policy · xiaolaiTest-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 live.
- ▌ Policy Core · xiaolaiGlobal TDD governance policy. Enforces plan-first development, behavior-driven test quality, and strict completion gates.
- ▌ Review Gate · xiaolaiProduce findings-first code review with severity ordering, test-gap findings, and test-quality audit.
- ▌ Test Matrix · xiaolaiBuild a comprehensive test matrix for changed behavior with explicit assertion strategy per case.
- ▌ Coverage Gate · xiaolaiEnforce coverage thresholds AND test quality — coverage without behavioral assertions is meaningless.
- ▌ Mutation Gate · xiaolaiValidate test strength with mutation testing and report weak assertions. Covers the Stryker family (JS/TS, .NET, Scala), PIT (JVM), Infection (PHP), mutmut and cosmic-ray (Python), go-mutesting and gremlins (Go), cargo-mutants (Rust), mutant (Ruby), and muter (Swift).
- ▌ Tooling Catalog · xiaolai bundlePer-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.
- ▌ MCP Spec · xiaolai bundleRouter 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, resources, prompts, sampling, roots, completion). Use when the user asks about: writing an MCP server (in any language), writing an MCP client, the JSON-RPC protocol framing, the initialize handshake, capability negotiation, the stdio transport, the streamable HTTP transport, the SSE transport, defining a tool / resource / prompt, sampling, roots, or completion. Includes the TypeScript SDK (`@modelcontextprotocol/sdk`) and Python SDK (`mcp`). Skip: Anthropic's hosted MCP connector (use anthropic-platform-features), the user-facing Claude Connectors directory (use claude-connectors), Claude Code's `.mcp.json` config (use claude-code → SKILL-mcp).
- ▌ Claude Code · xiaolai bundleRouter 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 .claude/settings.json or settings.local.json, authoring or debugging hooks (PreToolUse, PostToolUse, Stop, SubagentStop, Notification, UserPromptSubmit, PreCompact, SessionStart, SessionEnd, etc.), writing slash commands or agents, configuring MCP servers in .mcp.json, building plugins or marketplaces, setting ANTHROPIC_* / CLAUDE_* env vars, troubleshooting permission modes, understanding the ~/.claude/ directory layout, or asking "what does <feature> in Claude Code do". Skip: questions about the Anthropic Messages API (use anthropic-api), the Claude Agent SDK (use claude-agent-sdk), the MCP protocol spec (use mcp-spec), or general shell / git / programming topics not specific to Claude Code internals.
- ▌ Anthropic API · xiaolai bundleRouter 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, count_tokens, message batches, streaming responses, prompt caching, prompt cache TTL / breakpoints, system prompts, anthropic-beta headers, the admin API (organizations / workspaces / API keys / invites), compliance endpoints (data residency, audit logs, retention), beta-only features behind a beta header, or the models catalog (model IDs, deprecation dates, context window sizes). Skip: questions about Claude Code (use claude-code skill), the Claude Agent SDK (use claude-agent-sdk), platform features beyond the raw API such as Agent Skills format or tool-use guides (use anthropic-platform-features), MCP connector docs (claude-connectors), or per-language auto-generated SDK reference (use anthropic-sdk's TypeScript / Python types directly via your IDE).
- ▌ Claude Cowork · xiaolai bundleRouter 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 controls. Office agents covers Claude in Excel and Slack-style office integrations. Use when the user asks about: deploying Claude for Work on Bedrock or Microsoft Foundry, integrating an LLM gateway, configuring enterprise SSO, enabling telemetry / audit logs, connecting M365, applying enterprise policies, Claude in Excel, or Slack-style office agent integrations. Skip: raw API on Bedrock / Vertex (use anthropic-platform-features), user-facing connectors directory (use claude-connectors), Claude Code CLI in enterprise contexts (use claude-code).
- ▌ Anthropic Pulse · xiaolai bundleRouter 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, partnership news, region launches, new research papers, recent policy positions, or "what's new from Anthropic?" / "what did Anthropic just announce?" / "any recent research on X?" Skip: deep technical reference (use the other 7 skills — claude-code, anthropic-api, etc.); historical news older than ~30 items (link out to anthropic.com instead); detailed paper content (the digest carries title + summary + URL — Claude WebFetches the paper for depth on demand).
- ▌ Claude Agent Sdk · xiaolai bundleRouter 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()` / `ClaudeSDKClient`, hooks (PreToolUse / PostToolUse / Stop / etc.), subagents, MCP servers (stdio / HTTP / SSE / SDK in-process), permission modes, the sandbox (Docker / Kubernetes), structured outputs (JSON Schema validation), session capture / resume / fork, and session storage adapters (`SessionStore`, `InMemorySessionStore`, S3/Redis/Postgres). Use when the user asks about: importing `@anthropic-ai/claude-agent-sdk` in TypeScript or `from claude_agent_sdk import ...` in Python, writing an agent that uses `query()` or `ClaudeSDKClient`, registering hooks via the SDK (`hooks: { PreToolUse: [...] }` / `hooks={"PreToolUse": [...]}`), defining MCP servers in SDK options, configuring `permissionMode` / `permission_mode`, building subagents with `AgentDefinitio
- ▌ Claude Connectors · xiaolai bundleRouter 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 (GitHub, Google Workspace, Microsoft 365, Slack, …), the user-facing Agent Skills surface, and the user-facing Plugins surface. Use when the user asks about: enabling a connector in the Claude app, building a custom connector, packaging a Desktop extension (MCPB), MCP Apps visual / interaction design rules, submitting to the connectors directory, OAuth + token handling for connectors, the GitHub / Google / Microsoft / Slack connector integrations, authoring user-installable Skills, or installing plugins via the Claude app. Skip: low-level MCP protocol spec (use mcp-spec), MCP servers run by Claude Code CLI (use claude-code), MCP connector exposed by the API (use anthropic-platform-features → SKILL-agents-and-tools).
- ▌ Anthropic Platform Features · xiaolai bundleRouter 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, define-your-own tools), build-with-claude features (extended thinking, message batches, citations, Amazon Bedrock, Google Vertex, embeddings, fast mode, context editing), manage-claude operations (workload identity federation, billing, identity), and the Managed Agents product. Use when the user asks about: writing an Agent Skill `.skill` package, Anthropic's hosted MCP connector, MCP Tunnels (connecting private-network MCP servers without opening inbound ports), the computer-use tool, the code_execution tool, bash tool, extended thinking, message batches, prompt caching strategy at the platform level, citations, deploying via Bedrock or Vertex, embeddings models, fast-mode behavior, context editing strategies, WIF setup, billing / cost reports, identity
- ▌ My Skill · xiaolaiTemplate starter for an Agent Skill — replace this entire description with one that names the concrete intent triggers ("Use when the user asks about X, Y, Z") and lists negative-intent Skip clauses. The platform's skill matcher reads this field — write it for matching, not for marketing. Stay under 1024 chars.
- ▌ Adr · xiaolaiRecord 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.
- ▌ Lint · xiaolaiSweep 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 check the canon for contradictions / consistency / drift.
- ▌ Guide · xiaolaiOrientation 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 has a bureau workspace (a canon/ directory + a BUREAU.md), so you draw on the project's canon instead of re-deriving or guessing.
- ▌ Recall · xiaolaiAnswer 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 / what the canon says about something.
- ▌ Review · xiaolaiThe 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 approve / vet / sign off on what the AI wrote to memory before it is trusted as fact.
- ▌ Scribe · xiaolaiThe live note-taker — summarize the current session's decisions and open threads on demand or at checkpoints, and (in a bureau workspace) append them to the session's running minute. Use when running bureau:note, or when the user asks to take a note / minute this / summarize where we are.
- ▌ Capture · xiaolaiWrite 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 current session.
- ▌ Compile · xiaolaiDistil minutes into consistency-checked dossiers — the canonical SSOT — writing provenance links back to the sessions that introduced each claim. Use when running bureau:compile, or when the user asks to turn the logbook into canon / update the cabinets / build the knowledge base from sessions.
- ▌ Approve All · xiaolaiPrepare 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 running bureau:approve-all, or when the user asks to approve everything / approve the whole queue / bulk-approve at once. The AI never runs approve and never signs `--by human`.
- ▌ Codex Review · xiaolaiLet 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` authority in, commit under `--by codex` (delegate). Use when running bureau:codex-review, or when the user asks to have Codex screen / pre-review / decide the bureau backlog for them.
- ▌ Dbs · xiaolaidontbesilent 商业工具箱主入口。根据你的问题自动路由到最合适的诊断工具。 触发方式:/dbs、/商业、「帮我看看」 Main entry point for dontbesilent business toolkit. Routes to the right diagnostic skill. Trigger: /dbs, "help me with my business"
- ▌ Dbs Hook · xiaolaidontbesilent 短视频开头优化。诊断开头问题 + 生成优化方案。 触发方式:/dbs-hook、/hook、「帮我优化开头」「开头怎么写」 Short video opening optimization with diagnosis and solutions. Trigger: /dbs-hook, "optimize my opening", "how to write opening"
- ▌ Dbs Action · xiaolaidontbesilent 执行力诊断。用阿德勒心理学框架诊断你「知道该做什么但就是不做」的真正原因。 触发方式:/dbs-action、/action、「我知道该怎么做但就是不做」「为什么我总是拖延」 Execution block diagnosis using Adlerian psychology framework. Trigger: /dbs-action, "I know what to do but can't do it", "why do I procrastinate"
- ▌ Dbs Content · xiaolaidontbesilent 内容创作诊断。选题通过后,诊断怎么把这个选题做成好内容。 触发方式:/dbs-content、/内容诊断、「这个内容怎么做」「帮我看看这个文案」 Content creation diagnosis. After topic passes, diagnose how to turn it into good content. Trigger: /dbs-content, "how should I create this content", "review my copy"
- ▌ Dbs AI Check · xiaolaidontbesilent AI 写作特征识别。扫描文案中的 AI 生成痕迹,输出检测报告。默认只诊断不改。 触发方式:/dbs-ai-check、/AI检测、「帮我看看有没有 AI 味」「检测一下 AI 特征」 AI writing fingerprint detection. Scans copy for AI-generated patterns and outputs a diagnostic report. Diagnosis only by default. Trigger: /dbs-ai-check, "check for AI writing", "does this sound like AI"
- ▌
- ▌ Dbs Benchmark · xiaolaidontbesilent 对标分析。用五重过滤法帮你找到值得模仿的对标,排除一切关于「我」的噪音。 触发方式:/dbs-benchmark、/对标、「帮我找对标」「我该模仿谁」 Benchmark analysis using dontbesilent's five-filter method. Trigger: /dbs-benchmark, "find me a benchmark", "who should I copy"
- ▌ Dbs Diagnosis · xiaolaidontbesilent 商业模式诊断。两种模式:问诊(消解你的问题)和体检(拆解你的商业模式)。 触发方式:/dbs-diagnosis、/问诊、「帮我看看商业模式」「诊断一下我的业务」「我有个商业问题」 Business model diagnosis using dontbesilent's ontological framework. Two modes: consultation (dissolve your question) and checkup (analyze your business model). Trigger: /dbs-diagnosis, "diagnose my business model", "I have a business question"
- ▌ Dbs Xhs Title · xiaolai小红书标题公式工具。从 75 个验证过的爆款公式中,帮你挑对的、用对的、理解为什么用这个。 触发方式:/dbs-xhs-title、/小红书标题、「帮我起个小红书标题」「小红书标题公式」 Xiaohongshu title formula tool. Pick the right formula from 75 proven templates. Trigger: /dbs-xhs-title, "xiaohongshu title", "RED title formula"
- ▌ Dbs Slowisfast · xiaolaidontbesilent 慢就是快。帮创业者找到看起来更慢但长期更快的方法,用摩擦建造资产。 触发方式:/dbs-slowisfast、/慢就是快、「有没有更慢的方法」「我是不是太快了」 Slow-is-fast diagnosis. Help entrepreneurs find seemingly slower methods that build assets through friction. Trigger: /dbs-slowisfast, "is there a slower way", "am I going too fast"
- ▌ Dbs Deconstruct · xiaolaidontbesilent 概念拆解。用维特根斯坦 + 奥派经济学的方法,把模糊的商业概念拆到原子级别。 触发方式:/dbs-deconstruct、/拆概念、「帮我拆解这个概念」「这个词到底什么意思」 Concept deconstruction using Wittgenstein + Austrian economics framework. Trigger: /dbs-deconstruct, "deconstruct this concept", "what does this really mean"
- ▌ Dbs Agent Migration · xiaolaiAgent 工作台迁移。把任意项目整理成 Claude Code / Codex 双端一致、可长期维护的 Agent 工作台:审计规则文件、识别真源、统一命名并生成 bridge。 触发方式:/dbs-agent-migration、/agent迁移、「迁移到 Codex」「迁移到 Claude Code」「统一 AGENTS.md」「整理 skill bridge」「我的 Agent 工作台很乱」「帮我统一 Claude 和 Codex」 Agent workspace migration. Turn any project into a maintainable Claude Code / Codex dual-host workspace by auditing rule files, establishing source-of-truth skills, normalizing names, and generating bridges. Trigger: /dbs-agent-migration, /agent-migration, "migrate to Codex", "migrate to Claude Code", "fix AGENTS.md", "organize skill bridges"
- ▌ Dbs Chatroom Austrian · xiaolai哈耶克 × 米塞斯 × Claude 三人对话。奥派经济学视角的多角色讨论。 触发方式:/dbs-chatroom-austrian、/chatroom-austrian、/奥派、「奥派聊天室」 Austrian economics chatroom. Hayek × Mises × Claude debate. Trigger: /dbs-chatroom-austrian, /chatroom-austrian, /奥派, "Austrian chat"
- ▌ Mapping · xiaolaiUse when mapping source code files to their documentation counterparts — find which docs cover which code, detect gaps, and resolve doc-to-code relationships.
- ▌ Detection · xiaolaiUse when detecting a project's programming language and documentation framework from filesystem markers — package.json, Cargo.toml, pyproject.toml, mkdocs.yml, etc.
- ▌ Standards · xiaolaiUse when evaluating documentation quality — check completeness, accuracy, freshness, and adherence to project documentation standards.
- ▌ Lang Go · xiaolaiUse when writing, auditing, or generating documentation for Go projects — covers docstring conventions, API doc extraction, and Go-specific patterns.
- ▌ Lang Rust · xiaolaiUse when writing, auditing, or generating documentation for Rust projects — covers docstring conventions, API doc extraction, and Rust-specific patterns.
- ▌ Fw Mkdocs · xiaolaiUse when generating or auditing documentation in MkDocs format — covers config, directory structure, frontmatter conventions, and build commands.
- ▌ Fw Sphinx · xiaolaiUse when generating or auditing documentation in Sphinx format — covers config, directory structure, frontmatter conventions, and build commands.
- ▌ Lang Python · xiaolaiUse when writing, auditing, or generating documentation for Python projects — covers docstring conventions, API doc extraction, and Python-specific patterns.
- ▌ Lang Generic · xiaolaiUse when writing, auditing, or generating documentation for projects in unsupported languages — covers docstring conventions, API doc extraction, and generic heuristic patterns.
- ▌ Fw Vitepress · xiaolaiUse when generating or auditing documentation in VitePress format — covers config, directory structure, frontmatter conventions, and build commands.
- ▌ Fw Docusaurus · xiaolaiUse when generating or auditing documentation in Docusaurus format — covers config, directory structure, frontmatter conventions, and build commands.
- ▌ Lang Typescript · xiaolaiUse when writing, auditing, or generating documentation for TypeScript projects — covers docstring conventions, API doc extraction, and TypeScript-specific patterns.
- ▌ Fw Plain Markdown · xiaolaiUse when generating or auditing documentation in plain Markdown format — covers config, directory structure, frontmatter conventions, and build commands.
- ▌ Init · xiaolai bundleInitialize cc-suite for the current project — sets up the AGENTS.md bridge, registers Codex, Claude, and Antigravity MCP surfaces, and generates a .cc-suite.md config. Skill counterpart to /cc-suite:init.
- ▌ Audit · xiaolai bundleAsk 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.
- ▌ Repair · xiaolai bundleNon-interactive re-run of all cc-suite bridge and registration scripts. No questions asked — idempotent escalation step after the diagnose skill finds issues it could not fix. Skill counterpart to /cc-suite:repair.
- ▌ Verify · xiaolai bundleAsk Claude Code to verify that a list of reported issues has been fixed. Continues the same Claude session from a prior audit if session_id is available, so Claude has full context of what it flagged. Returns FIXED / NOT FIXED / PARTIAL / REGRESSED per issue.
- ▌ Diagnose · xiaolai bundleDiagnose the cc-suite setup in the current project. Runs the full health check, explains every issue, and fixes what can be fixed automatically. Skill counterpart to /cc-suite:diagnose.
- ▌ Audit Fix · xiaolai bundleFull 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.
- ▌ Claude Plan · xiaolai bundleAsk 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.
- ▌ Agent Design · xiaolaiUse 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 proactively whenever the user asks to "add an agent", "make an advisor", "write a reviewer", or edits anything under `.cc-suite/agents/`.
- ▌ Claude Debug · xiaolai bundleSend 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.
- ▌ Claude Review · xiaolai bundleDelegate 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.
- ▌ Claude Implement · xiaolai bundleDelegate 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.
- ▌ Claude Code Conventions · xiaolaiCanonical 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.
- ▌ MCP Dev · xiaolai bundleBuild or update MCP server/client integrations for VMark. Use when configuring MCP servers, adding MCP tools, or updating MCP-related docs and settings.
- ▌ Planning · xiaolai bundleCreate 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.
- ▌ Plan Audit · xiaolaiAudit 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.
- ▌ Tiptap Dev · xiaolai bundleExpert guidance for building rich text editors with Tiptap - a headless, framework-agnostic editor built on ProseMirror. Use when creating custom nodes, marks, or extensions for Tiptap, implementing input rules or paste rules, working with the Tiptap commands API, building React integrations with useEditor, extending existing extensions, or creating custom node views.
- ▌ Plan Verify · xiaolaiVerify 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.
- ▌ Release Gate · xiaolai bundleRun VMark release gates and summarize results. Use when asked to run full quality gates (lint/test/build), verify readiness, or produce a gate report.
- ▌ React App Dev · xiaolai bundleImplement or modify VMark React UI with project conventions (Zustand selectors, Tailwind v4, shadcn/ui). Use for components, hooks, stores, and UI behavior changes.
- ▌ Tauri App Dev · xiaolai bundleExpert guidance for building cross-platform desktop applications with Tauri 2.0 and Rust. Use when developing Tauri apps including commands and IPC, file system operations, window management, state management, system tray, menus, plugin development, security configuration (capabilities/permissions), bundling/distribution, and auto-updates. Covers patterns for editor applications requiring file dialogs, native menus, and frontend-backend communication.
- ▌ Tiptap Editor · xiaolai bundleTiptap editor API patterns for vmark WYSIWYG development. Use when working with editor commands, node traversal, selection handling, or format operations.
- ▌ CSS Design Tdd · xiaolaiTest-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.
- ▌ Shortcut Audit · xiaolai bundleAudit keyboard shortcuts in VMark code vs dev docs. Use when asked to review, reconcile, or optimize shortcuts, or when updating shortcut documentation.
- ▌ Translate Docs · xiaolaiTranslate 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 (src-tauri/locales/en.yml) that need multi-language support.
- ▌ Workflow Audit · xiaolaiAudit GitHub Actions workflows for correctness, security, and unattended reliability. Use when asked to audit workflows, check CI health, review workflow security, or before committing workflow changes.
- ▌ Tauri MCP Testing · xiaolai bundleE2E 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 apps.
- ▌ MCP Server Manager · xiaolai bundleDiscover, register, and verify MCP servers. Use when a user asks to connect/add/install/remove an MCP server, or when you need to manage project MCP configuration.
- ▌ Rust Tauri Backend · xiaolai bundleImplement or modify VMark's Rust/Tauri backend. Use when adding Tauri commands, menu items, filesystem integration, or platform behaviors in src-tauri.
- ▌ Tauri V2 Integration · xiaolai bundleImplement or adjust VMark frontend <-> Tauri v2 integration. Use when adding invoke/emit bridges, menu accelerators, or IPC-related UI behaviors.
- ▌ Tauri MCP Test Runner · xiaolai bundleRun Tauri MCP-driven E2E checks for VMark. Use when asked to execute or update automated UI flows that must use Tauri MCP tools (not browser DevTools), or when validating behavior in a running desktop session.
- ▌ Eou Audit · xiaolaiAudit 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 model; report goes to foundry/audits/eou-audits/." </example> <example> Context: Re-audit after applying an ECP. user: "$eou-audit foundry/eous/audit-foundry.yml" assistant: "Re-running. Rule 94 (executor != approver) is hard-checked first." </example>
- ▌ Ecp Propose · xiaolaiCreate a formal EOU Change Proposal from a diagnosed failure or refactor option, capturing simulation, regression case, audit, and approval requirements per rule 92. <example> Context: $eou-diagnose has produced a diagnosis recommending a change. Owner wants to convert it into an actionable ECP. user: "$ecp-propose foundry/audits/incidents/inc-0042.diagnosis.yml" assistant: "I'll read the diagnosis, target_eou, and proposed change; draft an ECP under foundry/self-evolution/ecp/proposed/ with simulation, regression case, audit, and approval blocks. Status starts at proposed." </example> <example> Context: User wants an ECP for a refactor option produced by $eou-refactor. user: "$ecp-propose ./refactor-options/ro-split-audit-eou.yml" assistant: "I'll draft the ECP. If the target requires a constitution change, I'll stop and direct you to the constitutional ECP process instead." </example>
- ▌ Eou Promote · xiaolaiEvaluate whether an EOU should be promoted, deprecated, or retired based on evidence, maturity model, audits, run traces, and owner approval. Produces a recommendation only — does not execute any lifecycle transition (that is the role of activate/retire execution, which requires human approval). <example> Context: An EOU has been at pilot stage for two weeks; owner wants to know if it qualifies for active promotion. user: "$eou-promote eou-diagnose" assistant: "I'll check evidence against the maturity-model gates (audit pass, named owner, regression coverage, trace presence) and write a lifecycle recommendation. If gates are not met, recommendation is hold/demote, not activate." </example> <example> Context: User wants to evaluate retirement of an unused EOU. user: "$eou-promote eou-old-validator" assistant: "I'll evaluate retirement evidence (successor documented or owner decision recorded). I produce a recommendation, never the retirement itself." </example>
- ▌ Eou Specify · xiaolaiConvert an approved candidate (from a candidate set) into a formal EOU spec at lifecycle_stage draft, populating all six classification facets, context manifest, execution steps, stop conditions, validation, failure modes, blast radius, and responsibility. <example> Context: A candidate has been accepted in audit-candidate-eou-set; owner wants to draft the formal spec. user: "$eou-specify foundry/self-evolution/candidate-sets/cs-generate-eou-candidates-20260520-1430.yml#audit-step-coverage" assistant: "I'll resolve the candidate id, draft a complete EOU spec at lifecycle_stage draft under foundry/eous/, and never set lifecycle_stage active (that requires approved ECP and human owner)." </example> <example> Context: User wants to REPAIR an existing partial spec. user: "$eou-specify foundry/eous/audit-step-coverage.yml --mode repair" assistant: "In REPAIR mode I leave fields that already satisfy schema constraints alone and only fill empty or placeholder-containing fields." </example>
- ▌ Eou Diagnose · xiaolaiDiagnose an EOU failure using the F-code taxonomy and recommend the smallest-blast-radius repair, producing either a diagnosis (path to $ecp-propose) or a no-change record. <example> Context: An incident has been filed; owner wants a structured diagnosis before deciding whether to open an ECP. user: "$eou-diagnose foundry/incidents/inc-0042.yml" assistant: "I'll classify the failure under one or more F-codes, rank repair options by blast radius, and emit either a diagnosis YAML (decision: change) or a no-change record under foundry/audits/incidents/." </example> <example> Context: User wants to diagnose from an audit finding rather than a full incident. user: "$eou-diagnose foundry/audits/eou-audits/eou-promote.audit.yml" assistant: "I'll diagnose the audit's findings; if evidence is insufficient for a change, I'll write a no-change record explicitly rather than silently doing nothing." </example>
- ▌ Eou Refactor · xiaolaiGenerate candidate EOU refactor options (split, merge, scope-reduction, authority-downgrade, step-extraction, validator-addition, stop-condition-injection, responsibility-separation) from an audit finding or incident. Produces options only; applying any option requires an ECP through $ecp-propose. <example> Context: An audit flagged that one EOU conflates two distinct judgments. Owner wants refactor options before opening an ECP. user: "$eou-refactor foundry/audits/eou-audits/audit-foundry.audit.yml" assistant: "I'll generate refactor options from the canonical patterns in foundry/refactoring-patterns.yml, weighing blast radius and constitutional fit, then write options under foundry/self-evolution/refactor-options/." </example> <example> Context: User asks for a specific refactor of an EOU with too-broad authority. user: "$eou-refactor eou-promote" assistant: "I'll generate options including authority-downgrade variants. None are applied; downstream $ecp-propose converts a chosen option into a proper change
- ▌ Eou Validate · xiaolaiValidate the structural integrity of Foundry schemas, registry entries, EOU specs, generating-EOU envelopes, and recursive-governance constraints. Produces a validation report; does not repair found violations (that is the job of $eou-specify in repair mode or $eou-refactor). <example> Context: Owner wants to know if the foundry tree passes structural validation before opening a PR. user: "$eou-validate" assistant: "I'll run scripts/validate_foundry.py and parse the output into a categorized validation report under foundry/audits/validation/. Failures are listed but not auto-repaired." </example> <example> Context: After a schema change, owner wants to confirm no specs drifted. user: "$eou-validate --strict-no-legacy" assistant: "I'll run validation with legacy engine copies treated as errors (not warnings). Useful pre-release to catch lingering pre-v0.5.0 layout." </example>
- ▌ Foundry Audit · xiaolaiAudit the EOU Foundry as a whole — not individual EOUs, but the system: schema drift across rule/validator/skill/docs layers, self-approval risk, generation overreach, weakened validators, missing trace, orphan EOUs, stale active EOUs without ECP history. <example> Context: Owner wants a portfolio-level health check before a quarterly release. user: "$foundry-audit" assistant: "I'll audit the whole Foundry. Checks include schema/validator/skill consistency, no-self-approval enforcement across active EOUs, vocabulary drift in canonical functions, and lifecycle/evidence triangle compliance (trace gate, activation evidence, maturity claim vs evidence)." </example> <example> Context: User wants to find which active EOUs have no run traces or no-trace justifications. user: "$foundry-audit" assistant: "Among other checks, I'll surface every EOU at lifecycle_stage active that fails the ECP-0014 trace gate. Report goes to foundry/audits/foundry-audits/." </example>
- ▌ Audit Judgment · xiaolaiAudit 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 F17), catches silent decisions on contested cases (F14), and runs counterfactual-swap audit as the V1 anti-theater defense. <example> Context: An EOU with judgment_authorized:true has accumulated several run traces with value_invocations. The owner wants to verify the invocations are load-bearing, not citation theater. user: "$audit-judgment compose-dish" assistant: "I'll load compose-dish.yml, its app's captured_workflow, and the run traces under foundry/runs/compose-dish/. I'll check each value_invocation entry against F14-F17, then run counterfactual-swap audit on up to 5 sampled invocations. Verdict report goes to foundry/audits/judgment-audits/compose-dish.judgment-audit.yml." </example> <example> Context: An EOU with judgment_authorized:false is passed
- ▌ Eou Foundry Init · xiaolaiUse when the user asks to initialize, scaffold, or create a new EOU-governed application. Creates a sibling directory with foundry/, instance copies of plugin templates, a starter constitution, and an initial git repo. Refuses to overwrite an existing directory.
- ▌ Audit Candidate Eou Set · xiaolaiAudit 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 wants to know which candidates survive audit before promotion. user: "$audit-candidate-eou-set foundry/self-evolution/candidate-sets/cs-generate-eou-candidates-20260520-1430.yml" assistant: "I'll run the eight tests (boundary, non-overlap, minimality, authority, operational value, counter-generation, set composition, high-stakes) and write the audit report under foundry/audits/candidate-set-audits/." </example> <example> Context: User wants to audit a candidate set that contains a generating EOU without a corresponding audit path. user: "$audit-candidate-eou-set ./my-candidates.yml" assistant: "I'll audit. Heads-up that if any candidate has authority_level approve/publish or proposes weakening validators, I'll escalate to FAIL regardless of other test outc
- ▌ Generate Eou Candidates · xiaolaiGenerate a minimal, ranked candidate EOU set from a messy workflow under Foundry V2 generation-envelope constraints. Candidates are proposal-only at lifecycle_stage candidate, with arguments_against and minimality results recorded per candidate; activation is forbidden at this stage. <example> Context: User has a workflow description and wants candidate EOUs to consider before specifying any. user: "$generate-eou-candidates Compile-chapter workflow: fetch source, parse, render, validate, publish." assistant: "I'll extract decision boundaries (not visible activity labels), test minimality per candidate (rule/validator/regression case alternatives), produce ≤ 7 candidates with arguments_against, and write a candidate-set artifact at foundry/self-evolution/candidate-sets/." </example> <example> Context: User points the skill at an existing YAML workflow description. user: "$generate-eou-candidates ./workflows/book-build.yml" assistant: "I'll load the workflow, run registry-diff against existing EOUs to avoid dup
- ▌ Generate Regression Cases · xiaolaiConvert incident reports and audit failures into candidate regression cases that prevent re-occurrence — each case captures a concrete observable symptom, the target EOU, the failure class (F-code), and an expected-behavior predicate. Cases are written as candidates; activation requires human owner approval. <example> Context: A diagnosis was filed for a path-drift incident; owner wants regression coverage so the failure cannot return silently. user: "$generate-regression-cases foundry/incidents/inc-0042.yml" assistant: "I'll extract the observable symptom, classify it under the F-code taxonomy, and write a regression case under foundry/self-evolution/regression/cases/. activation_status defaults to candidate." </example> <example> Context: User wants regression cases for a batch of audit findings. user: "$generate-regression-cases foundry/audits/eou-audits/*.audit.yml" assistant: "I'll iterate each finding, generate at most one regression case per observable symptom, and refuse to generate cases for findings
- ▌ Generate Captured Workflow From References · xiaolaiSynthesize 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 explicit constraints. For users entering an unfamiliar craft domain who cannot articulate a workflow unaided, and for any user who needs the constitutional layer made explicit before downstream EOU generation begins. <example> Context: A user wants to open a small seasonal restaurant but has never run one. user: "$generate-captured-workflow-from-references cooking — goal: small seasonal restaurant; references at refs/cooking.yml" assistant: "I'll load the goal and references, validate that all 5 role slots are filled with ≥1 user-contributed reference each, deconstruct the references for hidden judgments, failure modes, decision boundaries, and surface a 3–8 priority-ordered domain_values block. The output is a captured_workflow.yml that $generate-eou-candidates can consume." </example> <example> Context: An expert filmmaker wants to make their co
- ▌ Hunt Sqli · xiaolaiHunting skill for sqli vulnerabilities. Built from 8 public bug bounty reports. Use when hunting sqli on any target.
- ▌ Hunt Ssrf · xiaolaiHunting skill for ssrf vulnerabilities. Built from 9 public bug bounty reports. Use when hunting ssrf on any target.
- ▌ Hunt Ssti · xiaolaiHunt server-side template injection (SSTI) across Jinja2 (Flask/Django), Twig (Symfony), Freemarker (Java), ERB (Rails), Spring, Velocity, Mako, Thymeleaf, Smarty. Detection probes use double-curly and dollar-curly math expressions evaluated server-side. Once an engine is fingerprinted, escalate to RCE via the engine-specific class-walker, callback-registrar, or Execute-utility patterns documented in disclosed reports. Detection patterns: error messages reveal engine, blank or numeric eval reveals expression mode. Targets: email templates, PDF/report generators, CMS preview features, error pages with user input. Use when hunting RCE via template rendering, when content shows engine fingerprints, when finding endpoints that compose strings with user input before render.