One engineering workflow across Claude Code, Codex, Copilot, and Gemini CLI. A portable persona canon, process skills, and safety guardrails, kept in sync by design.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Scaffold an Architecture Decision Record (ADR) for a concrete decision that's already been made or is being made now. Use when the user says "ADR for X", "write up that decision", "ADR по ", or wants to record a choice for future readers. Different from /rfc — RFC explores options; ADR commits to one.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Orient fast in unfamiliar code — a new repo, a subsystem you don't own, or a PR touching code you don't know — and produce a short, high-signal map: what it is, entry points, architecture sketch, domain glossary, key seams, risky areas, how to run and test, known tradeoffs. Use for "map this repo", "orient me in this…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
A workflow for turning current code changes into small, logically grouped Git commits. A commit is a saved set of changes in Git that can be reviewed or reverted together.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Scan an entire codebase (or a chosen subtree) for over-engineering — premature abstraction, speculative generality, needless layering, wrapper-only modules, dead config/flags, indirection without payoff — and return a prioritized, deletion-oriented report. Use for "audit complexity", "find over-engineering", "where…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Collect the deliberate-simplicity tradeoff annotations left in the code (// TRADEOFF(ceiling: ...; upgrade: ...): ...) across the repo into a single ledger — location, ceiling, upgrade path, note. Use for "debt ledger", "list tradeoffs", "what shortcuts did we take", "debt-ledger". Pairs with the TRADEOFF convention…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
A step-by-step method for finding the actual cause of a software failure. It starts with a repeatable example, tests possible explanations, and verifies the fix.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
A writing guide for removing patterns that make text look AI-generated while keeping its meaning, facts, and intended tone.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Apply the "laziest solution that actually works" enforcement ladder when writing or proposing code — question whether the work needs to exist (YAGNI), reach for stdlib / native platform / already-installed deps before custom code, prefer one line over fifty. Supports intensity lite | full (default) | ultra. Use when…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Turn a risky migration or refactor into a safe, incremental, reversible plan that keeps user-visible behavior stable — framework upgrades, design-system swaps, API version migrations, legacy-to-modern replacement. Produces the invariant, the current-to-target seam, a migration shape (strangler / adapter /…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Shape a module so a small, stable interface hides substantial implementation — deep modules, information hiding, and the test for whether an abstraction earns its keep. Use when designing or reviewing a module or interface boundary, extracting a helper or wrapper, or deciding whether an abstraction is worth it…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
A pull-request review process that classifies findings as Critical, Important, or Optional. A pull request is a proposed code change submitted for review before it is merged into the project.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
A tool for drafting a GitHub pull request’s description from the current branch’s changes and the repository’s own template. It returns the result as raw Markdown that can be pasted into GitHub.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Second-pass re-review of a PR that already has review comments. Re-reads the diff and new commits against the existing open threads, marks each as addressed / partial / not addressed, resolves the addressed ones, and then either approves (only when everything is clean) or drafts new inline comments. Use when the user…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Gather evidence from primary sources to decide a concrete technical question — compare libraries, frameworks, APIs, or approaches — and produce a cited decision matrix with a recommendation and its uncertainty, ready to hand to an RFC or ADR. Use for "research X", "compare A vs B", "which library should we use"…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Draft an architecture RFC using the user's canonical 10-section format (Problem → Context → Constraints → Assumptions → Options → Trade-offs → Recommendation → Risks → Migration Strategy → Open Questions). Use when the user asks for an "RFC", "design doc", "architectural proposal", or "RFC по ". Optimized for the…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
A staged process for finding and fixing security weaknesses in an application. It first maps the relevant attack surface, then prepares an ordered remediation checklist before making approved changes.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
A short written definition of a change's goal, exclusions, acceptance criteria, and unanswered questions. Acceptance criteria are the observable conditions that determine whether the work is finished.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Onboarding entrypoint for this kit. Explains what the persona wizard does and hands you the exact command to generate your own persona (persona.md, CLAUDE.md, recommended-skills.md) from the shared templates. Use when the user says "/start", "get started", "onboard me", "set up my persona", or is new to the workspace.…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Testing checklist — test pyramid, what to test vs skip, DAMP over DRY, the TDD red-green-refactor loop for new code, failing-test-first for bug fixes, Vitest / React Testing Library patterns. Use when writing or reviewing tests, deciding test coverage for a change, driving new code test-first, fixing a bug (regression…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Web performance checklist — Core Web Vitals (LCP/INP/CLS), TTFB diagnosis, and frontend levers (JS/CSS/fonts/images/network/rendering) plus backend (DB N+1, API latency, caching, infra). Use when optimizing performance, diagnosing a slow page or unresponsive interaction, setting a performance budget, or reviewing a…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Web application security checklist — OWASP Top 10 + LLM Top 10, threat modeling (STRIDE), auth/authz, input validation, secrets, security headers, CORS, data protection, and supply-chain hygiene. Use when reviewing security, hardening a feature, threat-modeling, or before merging security-sensitive changes (auth, user…
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Use for architectural decisions, RFCs, ADRs, system design, trade-off analysis, migration planning, and complex technical decisions that need Staff-level reasoning. Returns a structured recommendation rather than implementation code.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
Use when preparing a compact handoff, task brief, implementation context, or review packet before a complex change, PR review, debugging session, or agent delegation.
yuri-semenenko/ai-engineering-workspace
Skill Claude CodeCodex
A step-by-step method for finding the confirmed root cause of broken behavior, failed tests, errors, or production regressions before changing code.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: