plan
Create implementation plans from spec via iterative codebase research and strategic questions. Produces mini-PR plans optimized for iterative development. Use after $spec or when you have clear requirements. Tr...
Découvrez les skills Documentation, comparez leurs dépôts et consultez leurs instructions.
Create implementation plans from spec via iterative codebase research and strategic questions. Produces mini-PR plans optimized for iterative development. Use after $spec or when you have clear requirements. Tr...
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code...
Audit test coverage for code changes. Identifies untested logic and provides specific test recommendations. Read-only analysis. Use before PR or after implementation. Triggers: review coverage, check tests, tes...
Audit code for testability design patterns. Identifies business logic entangled with IO, hard-coded dependencies, and mocking friction. Suggests functional core / imperative shell separation. Read-only analysis...
Execute implementation plans in-place with verification loops. Implements chunks sequentially, runs quality gates, auto-fixes failures. Use after $plan or with inline tasks. Triggers: implement, build, code, ex...
Comprehensive multi-wave web research with strategic source selection. Gathers information from official docs, community resources, and advanced sources. Use for deep technical research, API documentation, best...
Audit code for over-engineering, premature optimization, and cognitive complexity. Identifies unnecessary abstractions, YAGNI violations, and overly complex solutions. Read-only analysis. Triggers: review simpl...
Sync skills from claude-code-plugins vibe-workflow to this codex-workflow repo. Adapts Claude Code features to Codex equivalents. Use when vibe-workflow has updates to sync.
Audit TypeScript/typed code for type safety issues. Identifies any abuse, missing type guards, and opportunities to make invalid states unrepresentable. Read-only. Triggers: review types, type safety, check typ...
Audit documentation accuracy against code changes. Identifies stale docs, incorrect examples, and missing documentation. Read-only analysis. Use before PR or after implementation. Triggers: review docs, check d...
Build requirements specification through structured discovery interview. Use when defining scope, gathering requirements, or specifying WHAT work should accomplish - features, bugs, refactors, infrastructure, m...
Manage wedding vendors including registration, profiles, services, and communication. Use when working with vendors, vendor data, vendor services, vendor onboarding, vendor listings, or vendor-related database...
Generate wedding advice, planning ideas, and inspiration content for OpusFesta Events platform. Use when creating blog posts, planning guides, inspiration galleries, wedding tips, or advice content.
Use when writing Pull Request titles or commit messages to follow the Korean action word convention.
Use when creating or modifying NestJS service files that interact with MikroORM.
Use when writing tests for NestJS + MikroORM with transaction rollback and real DB integration.
Use when creating or modifying DTO files in the `dto/` folder.
Use when creating or modifying MikroORM entity files in the `entities/` folder.
Multi-perspective AI council for designing, validating, and improving trading strategies with 5 specialized agents.
Institutional-grade strategy validation, walk-forward analysis, and regime-aware testing.
Institutional-grade monitoring of alpha exhaustion, execution capacity, and regime drift.
Institutional-grade data cleaning, tick physics auditing, and gap reconstruction.
Minimizing slippage, benchmarking fills, and detecting toxic flow.
Institutional-grade management of systemic risk, hidden correlations, and black-swan stress testing.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.