Browse skills

Decompose a specification file into shell plans with YAML frontmatter. Each shell captures the wiring invariants (Produces, Consumes, Covers) and high-level Implementation Steps without committing to file paths. Use when the user asks to "draft plan shells", "create plan shells", "break spec into shells", "decompose spec into sessions", "draft shells from spec", "generate shells from spec", or "make shells from spec".

Expand a shell plan into a full implementation plan. Verifies Consumes against the current codebase, runs a fresh pattern survey, escalates open questions, and fills in concrete file references and verification. Use when the user asks to "expand a shell", "expand plan shell", "fill in the shell", "expand the shell", or "concretize the shell".

Migrate legacy plan and shell files in .turbo/ to the current format with YAML frontmatter. Handles three formats: inline prompt plans (.turbo/prompt-plans/ or .turbo/prompts.md with prompts embedded in the index), shell-based prompt plans (.turbo/prompt-plans/ index + separate shell files in .turbo/plans/), and regular plans without frontmatter. Use when the user asks to "migrate turboplans", "migrate turbo plans", "upgrade plan format", "add frontmatter to plans", or "convert old plans".

Pick the next ready plan shell and carry it through planning: expand, refine, self-improve, halt. Use when the user asks to "pick next plan shell", "next shell", "continue project", "what's next", "next implementation step", or "continue with the plan".

Use mmx to generate text, images, video, speech, and music via the MiniMax AI platform. Use when the user wants to create media content, chat with MiniMax models, perform web search, or manage MiniMax API resources from the terminal.

AI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.

Pick the next shell whose dependencies are satisfied and carry it through planning: expand, refine, self-improve, halt. Use when the user asks to "pick next shell", "next shell", "continue project", "what's next", "next implementation step", or "continue with the plan".

Expand a shell into a full implementation plan. Verifies Consumes against the current codebase, runs a fresh pattern survey, escalates open questions, and fills in concrete file references and verification. Use when the user asks to "expand a shell", "expand shell", "fill in the shell", "expand the shell", or "concretize the shell".

Use when reviewing, validating, or auditing IfcOpenShell Python code for correctness. Runs systematic checks for schema compatibility errors, incorrect API usage (direct attribute modification vs api.run), entity reference invalidation, performance anti-patterns, and IFC standard compliance. Prevents shipping code that works on one schema but fails on another. Keywords: code review, validation, audit, IfcOpenShell, API usage, schema compatibility, entity reference, performance, code quality, check my IFC script, review IfcOpenShell code.

Production-grade test automation skills for 46 frameworks across E2E, unit, mobile, BDD, visual, and cloud testing in 15+ languages.

Use when a task requires exhaustive unabridged output, complete files, or strict prevention of placeholders and skipped code.

Use when generating elite GSAP-heavy frontend pages with strict AIDA structure, wide hero typography, and gapless bento grids.

Use when designing expensive agency-grade interfaces with premium fonts, spatial rhythm, soft depth, and fluid microinteractions.

Relationship-aware daily gift engine with five-stage creative pipeline — editorial judgment, synthesis, concept generation, visual strategy, and rendering in H5, image, or video

Use when building high-agency frontend interfaces with strict design taste, calibrated color, responsive layout, and motion rules.

Use when creating raw industrial or tactical telemetry UIs with rigid grids, stark typography, CRT effects, and high-density data.

Generate production-ready mise.toml setups for local development, CI/CD pipelines, and toolchain standardization.

Use when upgrading existing websites or apps by auditing generic UI patterns and applying premium design fixes without rewrites.

Use when modeling MEP (Mechanical, Electrical, Plumbing) systems in IFC -- HVAC, piping, electrical circuits, distribution elements, ports, and connections. Prevents the common mistake of not creating ports for flow connections between elements. Covers IfcSystem, IfcDistributionElement, flow segments, fittings, and MEP property sets. Keywords: MEP, HVAC, piping, electrical, IfcSystem, IfcDistributionElement, port, connection, flow segment, fitting, mechanical, plumbing, duct, ventilation, connect pipes.

Create MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks.