ryanthedev/code-foundations

Code Foundations: software engineering skills for AI

366Stars on the repository
30Mods indexed here, across every type
1mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

placeholder-skill

01

ryanthedev/code-foundations

Skill Claude CodeCodex

Placeholder skill directory required by skill-eval's runeval tool signature. This benchmark runs configurations=['withoutskill'] only — we are measuring raw model tiers, not a skill — so this file's content is never mounted or read by a subject session.

366 1mo ago A 54 tokens

build-doctrine

02

ryanthedev/code-foundations

Skill Claude CodeCodex

Implements a coding task from a written spec with Done-When acceptance items. Use when given a spec to implement: stub the interface, implement it, then write tests that validate the Done-When items and any important behavior beyond them.

366 1mo ago A 52 tokens

build-doctrine

03

ryanthedev/code-foundations

Skill Claude CodeCodex

Implements a coding task from a written spec with Done-When acceptance items. Use when given a spec to implement: for each Done-When item, write a failing test first, then the minimum code to make it pass (red-green).

366 1mo ago A 53 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Guides module and API design using APOSD principles: generates multiple design alternatives, compares them on information hiding and interface depth, and produces a documented design decision. For creating new module/API design; not for assessing existing designs (use aposd-reviewing-module-design) or routine-level…

366 1mo ago A 76 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Assesses existing module and interface design for complexity symptoms: information leakage, shallow interfaces, pass-through layers, and unknown unknowns. Produces a structured assessment — not transformations (use aposd-simplifying-complexity to edit) and not new-design generation (use aposd-designing-deep-modules).

366 1mo ago A 70 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Transforms complex code by applying APOSD's pull-complexity-downward principle: resolves error hierarchies, collapses configuration, and moves caller-side logic into modules. Produces edited code; not for assessment-only review (use aposd-reviewing-module-design) or designing new modules from scratch (use…

366 1mo ago A 80 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Verifies implementation completeness across functional correctness, error handling, concurrency, and security dimensions using APOSD's post-implementation checklist. Run after a coding task is nominally complete, not during active bug investigation (use cc-debugging).

366 1mo ago A 55 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Applies Clean Architecture's dependency-direction and SRP-by-actor rules to system-level boundary design: separates business logic from infrastructure, identifies actor-coupling risks, and enforces inward-pointing dependency arrows. For system scope (multiple components, layers, or services), not routine or module…

366 1mo ago A 74 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Audits and restructures control flow using Code Complete's nesting, cyclomatic complexity, loop design, guard-clause, and boolean simplification rules. Covers deep nesting, loop exit design, index naming, and callback chains. For statement-level flow inside a routine; not for routine/class structure (use…

366 1mo ago A 86 tokens

cc-debugging

10

ryanthedev/code-foundations

Skill Claude CodeCodex

Applies Code Complete's scientific debugging method: STABILIZE → LOCATE → HYPOTHESIZE → EXPERIMENT → FIX → TEST → SEARCH. For active bug investigation, not QA process design or test coverage planning (use cc-quality-practices).

366 1mo ago A 57 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Applies Code Complete's defensive programming rules: barricade design, assertion vs error-handling selection, input validation policy, and correctness-vs-robustness strategy for the current context. For hardening code at trust boundaries; not for diagnosing an active failure (use cc-debugging) or post-completion…

366 1mo ago A 79 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Structures routine design through pseudocode-first iteration: clarifies naming and purpose before any code, catches design flaws cheaply, and prevents compile-debug loops on poorly understood routines. For designing a routine before writing it; not for assessing routines that already exist (use…

366 1mo ago C 64 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Applies Code Complete's QA process design: selects defect-detection techniques by phase, sizes the test suite, and designs review and inspection processes. For QA planning and process design, not active bug investigation (use cc-debugging).

366 1mo ago A 52 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Guides safe refactoring using Code Complete's fix-first-then-refactor discipline: decides between refactor, rewrite, and fix-first; enforces separate commits; applies small-change rigor to high-error-rate one-liners. Not for diagnosing the bug itself (use cc-debugging), transforming working code's complexity (use…

366 1mo ago A 94 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Applies Code Complete's routine and class design rules at the routine level: cohesion classification, parameter-count thresholds, LSP inheritance verification, and containment-vs-inheritance decision. For routine and class scope, not system architecture (use ca-architecture-boundaries).

366 1mo ago A 59 tokens

clarify

16

ryanthedev/code-foundations

Skill Claude CodeCodex

Decomposes underspecified requests by classifying gaps (missing info, ambiguity, false premises) and generating targeted clarifying questions. Produces a confirmed problem statement before any implementation begins. For sharpening a request that already exists; not for open-ended requirement discovery from a vague…

366 1mo ago A 64 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Audits and improves code clarity and documentation using APOSD's obviousness rules: naming quality, comment accuracy, AI-facing doc completeness, and the comments-first workflow for new code. Not for generating project-wide convention docs (use code-standards) or structural simplification of the code itself (use…

366 1mo ago A 78 tokens

code-standards

18

ryanthedev/code-foundations

Skill Claude CodeCodex

Generates or updates docs/code-standards.md by scanning the codebase for actual conventions. Produces an example-rich standards file optimized for LLM consumers, grounded in the project's real patterns. Not for auditing one file's naming, comments, or clarity (use code-clarity-and-docs).

366 1mo ago A 66 tokens

gof-design-patterns

19

ryanthedev/code-foundations

Skill Claude CodeCodex

Maps code symptoms — exploding subclass combinations, switch-on-type dispatch, tangled object construction, incompatible interfaces, one-to-many update cascades — to the matching Gang of Four pattern, then loads that pattern's structural recipe from its 23 reference files. For selecting and implementing a design…

366 1mo ago A 91 tokens

ryanthedev/code-foundations

Skill Claude CodeCodex

Applies measure-first performance optimization: profiles to find hot spots, applies algorithm and data-structure improvements before micro-optimizations, and validates each change prevents regression. For single-process code tuning; not for correctness bugs (use cc-debugging) or concurrency, distributed, and real-time…

366 1mo ago A 69 tokens

planning

21

ryanthedev/code-foundations

Skill Claude CodeCodex

Implements the Standard/Full planning pipeline for Medium and Complex tasks: multi-step discovery, phase decomposition with skill matching, cross-cutting concerns, and plan emission with Gate fields.

366 1mo ago A 38 tokens

welc-legacy-code

22

ryanthedev/code-foundations

Skill Claude CodeCodex

Safely modifies untested legacy code by getting it under test first: characterization tests, seam identification, sprout/wrap techniques, and pinch-point testing before any production changes. Not for refactoring code that already has test coverage (use cc-refactoring-guidance).

366 1mo ago A 59 tokens