Catalog
Every x402, MPP, MCP, and skill listing we've indexed, normalized, and enriched.
bootstrap-xcode-app-project
Bootstrap a new native Apple app project for macOS, iOS, or iPadOS when the user wants to start, begin, create, or bootstrap an Xcode app project. Use for new SwiftUI-first app repositories on macOS, with optional XcodeGen generation preference and repo-baseline setup guidance. D
bootstrap-swift-package
Bootstrap new Swift Package Manager repositories with consistent defaults, generated AGENTS guidance, validation, and customizable bootstrap settings. Use when creating a new Swift package, choosing platform or version presets, scaffolding its initial structure, or maintaining th
author-swift-docc-docs
Author and review DocC content for Swift package and Xcode app or framework repositories, including symbol comments, articles, extension files, landing pages, topic groups, and light tutorial-aware review. Use when the user wants help writing or reviewing DocC content, checking D
apple-ui-accessibility-workflow
Guide Apple UI accessibility implementation and review for SwiftUI-first code, with UIKit and AppKit bridge guidance plus explicit verification expectations and testing handoffs. Use when the user wants help making Apple UI accessible, reviewing accessibility semantics, shaping t
ultracook
This skill should be used when the user has an approved spec or unambiguous task with a high-blast-radius footprint and wants the whole pipeline (cook → press → age → cure → age → cure → age, all `--auto`) to run forward in fresh-context isolation per phase — phrases like "/ultra
press
This skill should be used right after `/cook` produces green changes, when the user wants the test surface hardened before review or shipping — phrases like "press the changes", "harden this", "check coverage", "strengthen the tests", "are the tests good enough", "press before /a
pasteurize
This skill should be used when the user has a hard bug, flaky failure, or performance regression — phrases like "diagnose this", "debug this", "why is X broken", "the test fails intermittently", "/pasteurize", or a pasted stack trace / repro without a stated cause. Runs a six-pha
mold
This skill should be used when the user has a fuzzy idea, half-formed feature, or design direction and wants to converge on a spec — phrases like "let's design X", "I'm thinking about Y", "what should the API for Z look like", "shape this into a spec", "I want to add a feature th
melt
This skill should be used when a git merge, rebase, or cherry-pick has produced conflicts and the user wants them resolved — phrases like "melt the conflicts", "fix the merge conflicts", "resolve the rebase conflicts", "what's conflicting after the merge", "/melt", "fix the cherr
hard-cheese
This skill should be used when the user wants a metacognitive vibecheck gate before code is shared for review or a pull request is opened — phrases like "/hard-cheese", "/cheese --hard", "gate this before I push", "vibecheck me", "make sure I understand this diff", "epistemic-deb
cure
This skill should be used when the user has an `/age` report (or any list of review findings, CI failures, or a "fix these" instruction) and wants the selected items resolved — phrases like "fix these findings", "/cure <slug>", "address the high-stake items", "act on the age repo
culture
This skill should be used when the user wants to think out loud, rubber-duck a design, walk through trade-offs, or explore an ambiguous problem WITHOUT producing production code or specs — phrases like "let's talk through X", "rubber duck this with me", "I'm trying to decide betw
cook
This skill should be used when the user has an approved spec, pasted requirements, or a focused unambiguous implementation request and wants the code written — phrases like "implement this", "build this feature", "write the code", "cook this spec", "make it work", "/cook .cheese/
cheez-write
This skill should be used when the user asks to edit, replace, modify, update, change, delete, or insert code in a file — phrases like "replace this function", "delete lines 44-89", "update validateToken", "change the implementation", "add this import", "fix this bug" (when fixin
cheez-search
This skill should be used when the user asks to find a symbol, definition, caller, import, or text pattern in the codebase — phrases like "where is X defined", "what calls Y", "find all usages of Z", "trace this function", "find the TODO comments", "search for this error string".
cheez-read
This skill should be used when the user asks to read, view, show, open, or display the contents of a file or directory — phrases like "read src/auth.ts", "show me this file", "what's in this directory", "view lines 44-89", "look at the imports". Replaces cat / head / tail / less
cheese
This skill should be used as the unified entry point when the user drops in any input — idea, spec path, file path, PR or issue, stack trace, bug report, or just `/cheese` — and wants the workflow routed. Phrases include "/cheese", "what should I do with this", "help me get start
cheese-factory
This skill should be used when the user has an approved spec that decomposes into 5+ independent behavioural curds and wants the whole pipeline run in parallel with reviewable PRs at the end — phrases like "/cheese-factory .cheese/specs/<slug>.md", "send through the factory", "pa
briesearch
This skill should be used whenever the user asks to research, look up, compare, or investigate something external to the immediate codebase — phrases like "research X", "look up the API for Y", "compare libraries", "what does the doc say about Z", "find examples of how to do W",
age
This skill should be used when the user wants a code review on a diff, PR, branch, or path — phrases like "review this", "/age", "is this safe to merge", "find bugs", "spot security issues", "check for slop", "review my PR", "look for problems", "what's wrong with this code". Run
roast
深度思维烤问引擎——通过渐进式追问挖掘用户内心深处的构思，暴露谬误、局限、潜能和潜意识中的盲点。触发条件：(1) 用户说'烤问我'、'挑战我的想法'、'帮我想清楚'、'roast me'、'challenge my thinking'、'审视一下'；(2) 用户在描述一个想法/计划/决策但逻辑模糊或自相矛盾；(3) 用户使用 /roast 命令。适用于：创业想法、研究方向、产品设计、人生决策、论文论点、技术方案、任何需要深度思考的场景。不触发：用户明确只需要执行（不需要质疑）、情绪崩溃时（先安抚再烤问）。
roast-ja
深層思考ロースティングエンジン——段階的な追問でユーザーの深層にある構想を掘り起こし、誤謬・限界・潜在能力・潜在意識の盲点を暴露する。トリガー条件：(1)ユーザーが「ロースト」「考えを挑戦して」「深く考えさせて」と言った時；(2)アイデアや計画を説明しているがロジックが曖昧または矛盾している時；(3)/roast コマンド使用時。適用：起業アイデア、研究方向、製品設計、人生の決断、論文の論点、技術アーキテクチャ等。トリガーしない：明確に実行のみ必要な時、感情的に不安定な時。
roast-en
Deep thought roasting engine — progressively interrogates your thinking to uncover fallacies, blind spots, hidden assumptions, and buried potential. Triggers when: (1) user says 'roast me', 'challenge my thinking', 'help me think this through', 'poke holes'; (2) user describes an
workflow-builder
Takes a repeating task from your work, breaks it into Cowork steps, and builds it into a documented, reusable workflow — optionally turning it into a custom skill. For converting manual repeating tasks into automated systems, when documenting a process for consistent execution, o