Explore skills

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

Test accountability policy. All failures belong to the current changeset. Commits must include test results. No failures on main.

gh コマンドの動作確認を行う

Complete funnel strategy playbook. Hook-Story-Offer framework, page structure templates, copy rules, objection handling order, QA checklist, and traffic source benchmarks.

Take a screenshot (full screen, region, or monitor) and save to /tmp/claude-screenshots/ for use with @ in prompts. Usage: /cshot [full|region|monitor [N]] [delay_seconds]

🤖 My Claude Code config!

🤖 My Claude Code config!

Add, update, or delete tests for changes in the current commit.

Run the feature-advisor query-time subagent over the full ontology to produce a structured impact assessment for a proposed feature or change. Maintainer asks "I want to add X — what's affected?" The agent reads sidecars + concepts.yaml + implicit-adrs.md + refactoring-scopes.md + doc-gaps.md + test-map.yaml + existing adrs/ + live ODD docs (via WebFetch), and emits `lineage/{repo}/feature-walks/{

Use this skill when the user asks to explain, walk through, or understand a file, function, class, or code concept. Covers high-level summaries, mental models, and pointing out non-obvious behavior. Do NOT use for debugging, refactoring, or writing new code.

Thinking guidelines to reduce common coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Audits an unfamiliar codebase, mapping its architecture, user-facing features, maturity, and risks. This skill is used to inspect repositories, summarize the tech stack, explain structure, list implemented features, assess maturity, or prepare a coding brief from an existing project.