Skill Claude CodeCodex
This skill should be used whenever the user asks to investigate unclear bugs, defend or reject PR review comments, triage CI failures or flaky tests, review risky/security/database/concurrency/external-API changes or multi-file refactors, or make any claim that needs evidence before patching. It enforces a falsifiable…
Skill Claude CodeCodex
This skill should be used whenever the user authorizes multi-step coding implementation: applying a plan, finishing a feature, implementing review feedback, writing tests, making a refactor, fixing a bug whose cause is already confirmed, or turning a specification into working code. It enforces a Plan → Do → Study →…
Skill Claude CodeCodex
This skill should be used whenever implementation or review depends on external, version-sensitive facts: libraries, SDKs, APIs, CLIs, cloud services, security advisories, changelogs, release notes, or documentation that may have changed. The skill anchors local versions, ranks source quality, runs an executable probe…
Skill Claude CodeCodex
This skill should be used whenever the user asks to "read", "review", "explore", "understand", "explain", "全文レビュー", "意味を分析", or "コード探索" in depth, or whenever implementation requires understanding existing code's intent before changing it. The skill forces per-symbol meaning analysis — splitting mechanical behavior…
Skill Claude CodeCodex
This skill should be used whenever the user asks for a serious security audit, vulnerability review, bug bounty triage, threat-model-driven code review, protocol/spec conformance audit, auth/authz or tenant-isolation review, exploitability analysis, CVE/advisory impact assessment, or security-sensitive PR review when…
Skill Claude CodeCodex
This skill should be used whenever the user wants a plan, claim, design, decision, PR, or their own understanding adversarially pressure-tested before committing — grill me, poke holes in this, challenge my thinking, play devil's advocate, red-team my plan, stress-test this, 詰めて, 反論して, この設計の穴を突いて — or when an agent…
Skill Claude CodeCodex
This skill should be used whenever the user asks for a non-obvious approach, an alternative architecture, a research direction, a product or monetization idea, an agent-skill design, or any "not just the obvious solution" / "発想を広げたい" / "普通じゃない解法" / "brainstorm alternatives" / "アイデア出し" request where the agent is likely…
Skill Claude CodeCodex
This skill should be used whenever the user needs to name a product, SaaS tool, brand, library, open source project, CLI, bot, or app, or asks to rename or rebrand a product or project, find a brand name, pick a product name, or escape generic AI-slop names. It enforces a metaphor-driven process that establishes a…
Skill Claude CodeCodex
This skill should be used whenever the user asks what to build next, what feature, tool, or product is missing, where the opportunities are in a codebase or domain, or makes any 0→1 origination request — 次に何を作るべきか, what should we build, this repo is missing something, find the gaps, surface opportunities — where the…