pimenov

pimenov/codex-first-skills-pack

Instructions file CodexOpenCode

AGENTS.md instructions for pimenov/codex-first-skills-pack, covering agents.md, scope, rules and style.

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Designs 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 changing public/internal APIs, SDK surfaces, webhooks, GraphQL/REST/RPC routes, database or message contracts, module…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Reviews 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 reviewing a PR/diff/commit/agent-produced code, after implementation or bugfix before final confidence, when deciding…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Curates 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, switching tasks, output quality degrades, the codebase is unfamiliar or large, source-of-truth is unclear, docs/code/runtime may…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Guides 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 expectation, a bug is reported, a prior fix did not work, CI/deploy/smoke checks fail, or something worked before and stopped…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Plans safe deprecation, migration, sunset, replacement, and removal of old systems, APIs, features, schemas, flags, cron jobs, integrations, configs, libraries, UI flows, and operational processes. Use when retiring legacy code, replacing an implementation, removing a public/internal interface, migrating consumers…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Runs 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, idempotent, secure, or compliant; when work touches production, auth, permissions, secrets, billing, public APIs, migrations…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Breaks 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, or operational change that could become a large diff; when more than one file/module is touched; when scope is fuzzy…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Turns 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, bugfix campaign, refactor, migration, deploy prep, client/internal work packet, Linear issue set, or when the user asks…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Grounds framework, library, SDK, API, CLI, and cloud-service implementation decisions in current official sources before code or recommendations. Use when building, debugging, reviewing, or explaining version-sensitive technical work; when the user asks for latest/current/correct/documented behavior, актуальные docs…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Defines 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 or changing a feature, product workflow, API, integration, migration, user-facing behavior, cross-team handoff, or any…

pimenov/codex-first-skills-pack

Skill Claude CodeCodex

Drives 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 validation, refactoring behavior-sensitive code, or after debugging identifies a root cause that needs a regression guard. Also…