Development

Explain complex code via Codex exec. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code. Not for: code review (use codex-code-review), exploration (use code-explore). Output: structured explanation at chosen depth.

Code review using Codex exec. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.

Use Codex CLI (not MCP) to review uncommitted changes. Codex explores the codebase independently with full disk read access.

Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.

Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations.

Dual-perspective code investigation. Use when: deep code analysis needing both Claude and Codex perspectives. Not for: quick exploration (use code-explore), code review (use codex-code-review). Output: integrated findings from dual analysis.

Pure Claude code investigation. Fast codebase exploration, trace execution paths, understand architecture, diagnose issues. No Codex dependency.

Claude Code config health check + plugin sync. Use when: auditing .claude/ structure, checking naming, verifying hook setup, detecting plugin version drift, syncing installed assets. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix recommendations.

Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.

This skill reviews completed work and records lessons learned. Use after completing a feature, when capturing insights before they fade, for periodic reflection on progress, or to graduate lessons to higher scopes. Triggers include "let's do a retro", "what did we learn", "review what happened", "capture lessons from", "graduate lessons".

This skill should be used when the user asks to "review backlog", "analyze backlog quality", "backlog health", "recommend items", or invokes /compass-rose:backlog. Reviews backlog items and analyzes quality to recommend best items to work on.

System design patterns and architectural decision frameworks for web applications and iOS native apps. Use when making technology choices, selecting architecture patterns, designing APIs, choosing databases, planning authentication, or architecting mobile app backends. Provides comparison matrices for informed decision-making.

Swift and SwiftUI development patterns for building native iOS/iPadOS applications. Use when implementing views, view models, data persistence, networking, concurrency, and navigation. Covers Swift 6.2, SwiftUI, SwiftData, iOS 26 features including Liquid Glass and Foundation Models.

React and Next.js development patterns for building modern web applications. Use when implementing components, pages, hooks, state management, data fetching, forms, and client-side authentication. Covers TypeScript, App Router, Server Components, and best practices.

Context management intelligence for Claude Code sessions. ACTIVATE when context filling up, phase transitions detected, user mentions "running out of context" or "conversation too long". Suggests strategic compaction timing - manual compact at phase transitions beats auto-compact at arbitrary points.

This skill should be used when the user asks to "rename function", "refactor code", "rename symbol across codebase", "change function signature", "restructure code safely", or mentions Serena's rename_symbol or replace_symbol_body tools.

This skill should be used when the user asks to "navigate code efficiently", "find function definition", "understand file structure", "explore codebase", "get symbols overview", "find symbol usages", or mentions Serena's LSP tools like get_symbols_overview, find_symbol, find_referencing_symbols.

Node.js backend development patterns for Express, NestJS, Fastify, and Hono. Use when implementing APIs, authentication, middleware, services, and server-side logic with Node.js and TypeScript. Provides project structure, code patterns, and best practices.

This skill should be used when the user asks to "save project context", "load memories", "persist knowledge", "remember this for next session", "update architecture notes", or mentions Serena's write_memory, read_memory, list_memories, edit_memory tools.

Project brief and PRD patterns for non-technical project documentation. Use when running /my_project, creating project briefs, defining product requirements, or asking about value propositions and target audiences.

CLAUDE.md generation patterns using project.md and brand.md context. Use when creating CLAUDE.md, running /my_setup, optimizing Claude Code configuration, or asking about technical documentation for Claude Code.

Platform-agnostic brand identity creation using 12 Jungian archetypes. Use when running /my_brand, creating brand.md, selecting color palettes, defining typography, or asking about brand personality and voice guidelines.

Update inline documentation for uncommitted code changes. Use after modifying code or when documentation needs sync.

Review uncommitted code changes for bugs, security vulnerabilities, and quality issues. Use before commits or when asked to review code.