Explore skills

Use AFTER first-round planning is complete, to do META-PLANNING — what wasn't planned that should have been? What pitfalls don't surface in the first round due to existing context bias, context rot, plan mode system prompt biases, or other distortions? Triage importance, surface escape routes (subagent assessment, backups, operator ready for ctrl+C, anything). NOT a duplicate of plan mode or commo

GAN thinking mode — when delivering X, also run an adversarial pipe asking "is X fundamentally flawed as a concept? achievable with existing means via refactor? do bugs/vulns exist in X?". Two timings — pre-ship (in-vacuum, no real-world signal yet) and post-ship (with feedback signal). DELIBERATE REFRAME of the chengyu: the literal Chinese is "two pipes simultaneously" (parallel-cooperative), but

Use when an output is at risk of verbosity — the TLDR-outside / details-inside discipline. Distinguished from chengyu-great-wisdom-looks-foolish on the representation axis — 大智若愚 = resist performative complexity, 言簡意賅 = resist sprawl. Orthogonal failure modes; you can be performatively-clever AND brief, or non-clever AND verbose.

Use when user asks for a rough draft, first pass, brainstorm, MVP, stub, sketch, or proposes to "draft a PR for review and refinement before sending upstream" — anywhere the user is throwing a brick (deliberately rough work) to elicit jade (refinement, feedback, selection)

Use when a failure, debate, or process is mid-unfolding and the urge is to intervene immediately — but premature intervention loses information. Let the failure reach its natural shape so the full signal is captured before patching. Strict caveat against the modern schadenfreude reading; this is observation discipline, not indifference.

Consult official Claude Code documentation from docs.claude.com using selective fetching. Use this skill when working on Claude Code hooks, skills, subagents, MCP servers, or any Claude Code feature that requires referencing official documentation for accurate implementation. Fetches only the specific documentation needed rather than loading all docs upfront.

Use Google Gemini for parallel code reviews, complex task validation, and second opinions. Runs Gemini CLI non-interactively to provide alternative perspectives on code quality, implementation decisions, and technical solutions.

Minimal test skill for E2E testing

Systematically verify documentation claims against codebase reality. Use when auditing docs, before releases, after refactors, or when documentation drift is suspected. Two-pass approach with pattern expansion ensures comprehensive detection of false claims, dead references, and gaps.

Create high-converting, visually distinctive landing pages. Use when building marketing pages, product launches, SaaS homepages, or any single-page conversion-focused website. Guides section-by-section composition with anti-AI-slop principles.

Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions, high fan-out, refactor candidates, code quality audit, graph query syntax, Cypher

Xcode Cloud CI/CD configuration, workflows, custom scripts, testing, deployment, and optimization. Use when setting up or troubleshooting Xcode Cloud pipelines.