oleg494

oleg494/coding-kit

Instructions file CodexOpenCode

AGENTS.md instructions for oleg494/coding-kit, covering coding-kit — agent soul, 1. identity, 2. red lines, 3. reflexes and 4. routing — how to answer.

oleg494/coding-kit

Skill Claude CodeCodex

Use when the user wants to: design/redesign modules and layers, choose between a library and your own code, understand why a project became a god file, add an abstraction "just in case", evolve a DB schema without data loss, or review architecture. Covers: YAGNI until second need, stdlib-first, modules by change…

oleg494/coding-kit

Skill Claude CodeCodex

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

oleg494/coding-kit

Skill Claude CodeCodex

Use BEFORE a commit or change review, when you need to understand "what this N-file change will break": blast radius over the diff, affected execution paths, dead code, architectural hubs/bridges, weak spots, rename with preview. Do not use for code search — CRG is for structural diff analysis, not navigation.

oleg494/coding-kit

Skill Claude CodeCodex

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

oleg494/coding-kit

Skill Claude CodeCodex

Use when designing, redesigning, or reviewing marketplace, seller, operations, finance, logistics, or analytics dashboards: information hierarchy, KPIs, filters, charts, tables, honest data visualization, design tokens, responsive behavior, loading/empty/error states, and post-change UI verification in the running…

oleg494/coding-kit

Skill Claude CodeCodex

Use when the user says: «it doesn't work», «still broken», «hung/stuck», «disappeared after the update», «it used to work», «the metric is zero but the UI is fine» — or when an incident needs to be analyzed, the root cause of a hang found, and whether a process was actually restarted verified. Covers: facts before…

oleg494/coding-kit

Skill Claude CodeCodex

Use when creating or refactoring a product UI system, shared components, themes, tokens, or dashboard styling. Keeps color, typography, spacing, states, and responsive rules coherent without introducing a large component abstraction prematurely.

oleg494/coding-kit

Skill Claude CodeCodex

Always-on. Cross-chat memory (database, not conversation): record decisions, errors, patterns in the global Wiki (/.memory). Use on "record"/"save"/"remember"/"запиши"/"сохрани"/"запомни"/"в память"/"память" or "what do we know about X"/"напомни". Hierarchy: portable → /.memory/Wiki/; project-specific → WORK/ /docs/.…

oleg494/coding-kit

Skill Claude CodeCodex

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.

oleg494/coding-kit

Skill Claude CodeCodex

Always-on. Response format rules (not a persona): direct engineering tone, result first, evidence-based, no fluff, no "I would recommend". Code > words. Observation > assumption.

oleg494/coding-kit

Skill Claude CodeCodex

Adversarial verification of finished work: re-runs the claimed verifications, diffs what changed, detects false "done" claims, delivers an evidence-based verdict (VERIFIED / VERIFIED WITH CAVEATS / REFUTED). Use after any agent or model claims work is complete — "/fable-judge", "judge this work", "verify what it did".…

oleg494/coding-kit

Skill Claude CodeCodex

A step-by-step problem-solving loop (classify the ask, define done, gather evidence, decide, act surgically, verify by observation, report outcome-first). Use when the user says "/fable-method", "use the fable method", or "approach this like Fable", or proactively when starting any multi-step task that no…

oleg494/coding-kit

Skill Claude CodeCodex

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.

oleg494/coding-kit

Skill Claude CodeCodex

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

oleg494/coding-kit

Skill Claude CodeCodex

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

oleg494/coding-kit

Skill Claude CodeCodex

Use when the user wants to: pay/buy/subscribe, receive or spend a bonus/promo code/referral, check a balance or limit, get a refund, or when any logic for deducting/crediting/quotas changes — even if the request does not name money explicitly («give me more minutes», «why was I charged twice», «enter a promo code»).…

oleg494/coding-kit

Skill Claude CodeCodex

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

oleg494/coding-kit

Skill Claude CodeCodex

Lazy senior-dev mode for any coding task (write, refactor, fix, review): climb the minimalism ladder — skip it, reuse it, stdlib, native, installed dependency, one line, then the minimum that works. Deletion over addition, no unrequested abstractions, one runnable check for non-trivial logic. Use for any code change…

oleg494/coding-kit

Skill Claude CodeCodex

Use for ANY "how to do it" decision: choosing an approach/tool/library/standard, designing, "what if", adopting a new mechanism — when the answer must not come out of your head. Covers: the production-first order (formulate the question → web search as the industry does → verify your hypothesis → do it the industry…

oleg494/coding-kit

Skill Claude CodeCodex

Use for ANY non-trivial action — always-on skill. Multi-step thinking (5 steps ahead), evidence-first protocol, complexity classifier, skill-first mandate, memory-first protocol. This is the core of the agent's thinking: do not write code/a solution without this skill.

oleg494/coding-kit

Skill Claude CodeCodex

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.

oleg494/coding-kit

Skill Claude CodeCodex

Use when completing tasks, implementing major features, or before merging to verify work meets requirements.

oleg494/coding-kit

Skill Claude CodeCodex

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when personal data or privacy compliance (GDPR, CCPA) is involved.