Skill Claude CodeCodex
Economy analysis team: flow design, monetary health, player behavior, exploit risk, and product impact synthesized. Use for economy design, reward systems, marketplace, or monetary policy review.
Skill Claude CodeCodex
Frontend review team: UX quality, implementation health, accessibility, and frontend-backend integration in one recommendation. Use for UI features or frontend-heavy flows.
Skill Claude CodeCodex
Infrastructure team: deployment safety, capacity, observability, platform setup, and data-operational risk in one production-readiness assessment.
Skill Claude CodeCodex
Move/Sui team: smart contract correctness, off-chain integration, security, and economy soundness reviewed together. Use for contract changes affecting integration or economic flows.
Skill Claude CodeCodex
Open source readiness team: licensing, security, contributor experience, and strategic alignment for public collaboration.
Skill Claude CodeCodex
Product evaluation team: user value, feasibility, experience quality, and measurement in one recommendation. Use for feature proposals, go/no-go decisions, or scope negotiation.
Skill Claude CodeCodex
Adversarial review team: security, scalability, economic exploits, and behavior-based abuse analysis. Use for pre-launch or high-stakes risk analysis from attacker perspective.
Skill Claude CodeCodex
Author a new skill (role, team, or workflow) in this pack's conventions, then wire it into routing and docs. Use when adding, splitting, or formalizing a capability so it lands consistent and discoverable instead of ad hoc.
Skill Claude CodeCodex
Current-state capture workflow: orient a new owner to one bounded system, explain what it is and is not, and map the best next inspection path from code reality.
Skill Claude CodeCodex
Interface design comparison: produce 3+ competing API or module designs, compare them, and recommend one before coding. Use when multiple plausible interface shapes exist.
Skill Claude CodeCodex
Production incident workflow: detect, triage, fix, verify, postmortem. Use when something is broken in production and needs structured response with clear handoff artifacts.
Skill Claude CodeCodex
Bug handoff workflow: packages investigation findings into a durable markdown artifact with reproduction, root-cause summary, TDD fix plan, and ownership. Use when a bug needs a clean artifact for follow-up.