Loading...
Loading...
Found 12,971 Skills
Maintaining the story knowledge base: creating, updating, and organizing wiki-style reference pages in kb/. Use when capturing finalized story knowledge, updating character profiles, documenting world mechanics, or restructuring the kb.
Implement a task with automated LLM-as-Judge verification for critical steps
Systematically fix all failing tests after business logic changes or refactoring
Evaluate solutions through multi-round debate between independent judges until consensus
Fill web forms by fetching form fields from a URL, deep-searching the user's local knowledge base for relevant info, and generating a markdown document with all answers pre-filled. Use when the user provides a URL to a web form (conference application, speaker submission, event registration, profile form) and wants help filling it out from their existing materials. Also trigger when the user mentions "填网页表", "fill web form", "网页填表", "表单填写", "申请表填写", "conference application", "speaker submission", "讲师申请", "报名表", or provides a URL with "form", "feedback", "apply", "register", "submit" in the path.
Convert photos into animated GIF stickers in Funko Pop / Pop Mart style via the MiniMax API. Useful for personalized chat stickers and avatar packs.
UI/UX design patterns and best practices. Pattern library + heuristic checks for shipping clean, usable interfaces.
Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.
Turn a vague idea or task into a confirmed Working Brief by interviewing the user one question at a time, each with a recommended answer, then (only when the user chooses) plan execution with cost-effective model routing. Use when the user invokes Ask Me, wants to clarify scope or requirements before work begins (เคลียร์โจทย์ วางขอบเขต ทำ brief), or asks to execute a WORKING-BRIEF.md.
Implement an approved spec or focused unambiguous task through stale-safe source edits. Use when the user wants code written — "implement this", "cook this spec", "/cook .cheese/specs/<slug>.md", or "fix this bug" when the fix is clear; also when the user just says "go" or "ship it" with a spec or clear acceptance criteria in scope. Runs standalone on an unambiguous task — a spec helps but is not required. Do NOT use for fuzzy planning (`/mold`), no-write discussion (`/culture`), or review-only work (`/age`).
Apply fixes from an /age report, finding list, or CI failure, then run the project's test/lint/build gates and hand a clean cure to /plate for commit/publication. Use when the user wants selected findings resolved. Do NOT use for review (route to /age), test authoring (route to /press), or direct publication (route to /plate).
Converge a fuzzy idea or half-formed feature into an approved spec through an iterative, grounded design dialogue. Use when the user has a fuzzy idea or design direction — phrases like "let's design X", "I'm thinking about Y", "what should the API for Z look like", "shape this into a spec", "what would it take to build/set up X", "I want to add a feature that…", "/mold". Use even when the user is "just thinking out loud" if they want the dialogue to leave behind a written artifact. Do NOT use for free-form discussion with no artifact intent (`/culture`), direct implementation (`/cook`), or research-only questions (`/briesearch`).