Code Foundations plugin for Grok Build
Code Foundations: software engineering skills for AI
How to install Code Foundations in Grok Build
grok plugin install ryanthedev/code-foundations --trustReview before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.
Then start a new Grok session, or press r in /plugins, to load it.
Command format: Grok Build's plugin guide
What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 23 skills, 4 slash commands, 1 subagent. That's an install check only: we haven't run it in a live Grok session.
What it contains
Skills (23)
aposd-designing-deep-modules— 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 assaposd-reviewing-module-design— 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-complexaposd-simplifying-complexity— 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-raposd-verifying-correctness— 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 invesca-architecture-boundaries— 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 syscc-control-flow-quality— 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-cc-debugging— 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).cc-defensive-programming— 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; ncc-pseudocode-programming— 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 writingcc-quality-practices— 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).cc-refactoring-guidance— 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 thecc-routine-and-class-design— 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 systemclarify— 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 requestcode-clarity-and-docs— 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 docscode-standards— 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, cgof-design-patterns— 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 reperformance-optimization— 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 forplanning— 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.welc-legacy-code— 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 testbuild— Execute an approved plan through gated phases (BUILD → REVIEW → commit) with subagent dispatch. Use when a plan exists in .code-foundations/plans/ and the user wants it implemented — phased implementation, per-phase quality gates, orchestradebug— Runs the scientific debugging method on an active bug — reproduce, locate, hypothesize, fix, verify, search for siblings. Use to chase a failing test, a flaky or intermittent failure, a crash, or any 'why is this broken' investigation, or tplan— Turn a feature request or research doc into a phased, build-ready implementation plan. Use after research, or whenever a change needs decomposition into phases with skills, models, and gates before building.research— Extract and document what the user wants — even when they don't know yet. Use before plan, or standalone when exploring an idea.
Subagents (2)
code-foundations:build-agent— Discovery, design, and implementation in one pass. Scopes phase work, makes design decisions, stubs the interface, implements it, then validates with tests.code-foundations:post-gate-agent— Independent, execution-grounded review of a build phase against its done-when requirements. Runs the suite first, verifies each requirement with evidence and a trace, returns PASS or FAIL with specifi
About this listing
Code Foundations is a community plugin on GitHub by ryanthedev, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 23 skills, 2 subagents. No license stated in the repo, so check with the author before reusing its code. We checked commit ca30ba90ebd3. It's one of 409 listings in the Development category on GrokStacks.
Stacks Weekly: every new Grok Build and Codex plugin, every Tuesday.
One short email for GrokStacks and CodexStacks readers, with each new plugin's install line and what it ships. Subscribe and get the free starter list: 20 Grok Build plugins worth installing first.
You'll get a confirmation email first. Unsubscribe anytime.
Code Foundations FAQ
How do I install Code Foundations in Grok Build?
Run grok plugin install ryanthedev/code-foundations --trust. We install-checked this command in Grok Build. Then start a new Grok session, or press r in /plugins, to load it.
Is Code Foundations an official Grok Build plugin?
No. Code Foundations is a community plugin on GitHub by ryanthedev, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.
What does Code Foundations include?
According to what Grok loaded in our install check, Code Foundations includes 23 skills, 2 subagents: aposd-designing-deep-modules, aposd-reviewing-module-design, aposd-simplifying-complexity, aposd-verifying-correctness, ca-architecture-boundaries, cc-control-flow-quality….
Details
- Type
- Plugin
- Category
- Development
- Source
- Community Claude Code plugin, installs in Grok
- License
- No license stated
- Author
- ryanthedev
- Version
- 6.6.0
- Source repo
- https://github.com/ryanthedev/code-foundations
- Checked commit
ca30ba90ebd3- Checked by GrokStacks
- Install-checked in Grok Build on Oct 18, 2026; not run in a live session
Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.
For maintainers: badge and embeds
Maintain Code Foundations? Add the badge; it links to this page.
Markdown
[](https://grokstacks.com/p/code-foundations/)HTML
<a href="https://grokstacks.com/p/code-foundations/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>Embed card (static HTML and inline CSS, no JavaScript). Preview:
<a href="https://grokstacks.com/p/code-foundations/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">Code Foundations</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 23 skills, 2 subagents</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">Code Foundations: software engineering skills for AI</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>Markdown summary
**[Code Foundations on GrokStacks](https://grokstacks.com/p/code-foundations/)**: Community plugin for Grok Build with 23 skills, 2 subagents. Install: `grok plugin install ryanthedev/code-foundations --trust`More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.
Also in Development
Abap2UI5
Build UI5 Apps Purely in ABAP
Accessibility Agents
Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating inaccessible code.
addyosmani/agent-skills
Production-grade engineering skills for AI coding agents.
Advise Project Approach
A portable project-planning skill for Codex, Claude Code, pi, Hermes, and Agent Skills-compatible harnesses. Evidence before build advice.
Agent Bridge
A local bridge for bidirectional collaboration between Claude Code and Codex. 连接 Claude Code 与 Codex 的本地实时协作桥接工具。
Agent Harness
Our agent harness: Skills, plugins, hooks, and utilities to improve the quality of your agent.