pimenov/codex-first-skills-pack
11 skills
$npx skills add pimenov/codex-first-skills-packSkillInstalls
api-and-interface-designDesigns stable API, interface, schema, event, CLI, module, and service contracts before implementation so callers, consumers, and future agents can depend on them safely. Use when creating or changingcode-review-and-qualityReviews code changes across correctness, tests, readability, architecture, security, and performance before they are merged, shipped, or called done. Use when the user asks for a code review, when revcontext-engineeringCurates focused project and session context before answering, planning, editing, debugging, reviewing, deploying, or handing off work. Use when starting or resuming work in a repo/workspace, switchingdebugging-and-error-recoveryGuides systematic root-cause debugging and recovery instead of guessing fixes. Use when tests fail, builds break, commands error, logs or consoles show errors, runtime behavior differs from expectatiodeprecation-and-migrationPlans safe deprecation, migration, sunset, replacement, and removal of old systems, APIs, features, schemas, flags, cron jobs, integrations, configs, libraries, UI flows, and operational processes. Usdoubt-driven-reviewRuns an adversarial review gate for non-trivial or high-stakes decisions before they stand. Use when Codex is about to claim something is safe, correct, reversible, production-ready, scalable, idempotincremental-implementationBreaks large or multi-file implementation work into small verified slices that keep the project working after each step. Use when building a feature, bugfix, refactor, migration, integration, UI flow,planning-and-task-breakdownTurns ambiguous, large, multi-step, or handoff-prone work into sequenced tasks with outcomes, dependencies, stop-lines, acceptance criteria, and the right durable layer. Use when planning a feature, bsource-driven-developmentGrounds framework, library, SDK, API, CLI, and cloud-service implementation decisions in current official sources before code or recommendations. Use when building, debugging, reviewing, or explainingspec-driven-developmentDefines the implementation contract before planning or coding so work is built against explicit goals, users, scope, non-goals, assumptions, acceptance criteria, and verification. Use when creating ortest-driven-developmentDrives behavior changes through tests or explicit focused checks before implementation. Use when implementing new logic, fixing a bug, changing behavior, adding edge-case handling, modifying validatio