Skip to content

The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.

docs(web): add game-development workflow guide

YeonGyu-Kim3f8e33d80ce4
diff --git a/README.md b/README.md
index f50bbfc1..82d6ca0d 100644
--- a/README.md
+++ b/README.md
@@ -52,6 +52,61 @@ LazyCodex installs these as OmO commands for Codex. Invoke them with the
Full documentation lives at [lazycodex.ai/docs](https://lazycodex.ai/docs).
+## Build games with LazyCodex
+
+The first time, there was no grand theory. It worked, so we kept using it.
+After working around a KartRider Drift codebase on [oba.run](https://oba.run),
+the pattern became clear: game projects are where LazyCodex makes the most
+sense.
+
+### 1. `/init-deep` is the map
+
+Game projects rarely fit a clean folder story. Big repos carry gameplay code,
+tools, editors, content pipelines, experiments, vendor drops, and old milestone
+work in the same tree. The goal is not to make the structure look pure before an
+agent can help. The goal is to give the agent landmarks.
+
+`/init-deep` builds that map by generating hierarchical `AGENTS.md` context. It
+scores complex directories, writes local guidance near the code that needs it,
+and lets future agents find the right files faster.
+
+### 2. A game MVP is usually not the product
+
+A POC can prove the loop. The product around it is usually several applications:
+Tools, data, launchers, editors, and build pipelines. If the agent only looks at
+the game executable, it misses the actual development system.
+
+LazyCodex keeps that wider context in play. Use `$ulw-plan` when the shape is
+still fuzzy, `$start-work` when the plan is ready, and `$ulw-loop` when you want
+the agent to keep moving until the evidence says it is done.
+
+### 3. Dense domains get faster with memory
+
+`/init-deep` is not only a first-run setup command. Rerun it when the milestone changes.
+Run it again when the repo shape changes or when a new subsystem becomes important.
+The result behaves like compressed project memory.
+
+In legacy game code, the hard part is not reading everything. The hard part is
+knowing where to read first. That is where LazyCodex is strong.
+
+### Skill-first workflows
+
+The three main commands stay simple, but the skill layer is where specialized
+work gets sharper:
+
+| Use case | Reach for |
+| --- | --- |
+| Map a messy game repo | `/init-deep` |
+| Turn vague production work into a plan | `$ulw-plan` |
+| Execute a plan with durable progress | `$start-work` |
+| Keep pushing until verified completion | `$ulw-loop` |
+| Review implementation from multiple angles | `review-work` |
+| Remove AI-looking code without changing behavior | `remove-ai-slops` |
+| Build polished UI surfaces | `frontend-ui-ux` |
+| Work safely in strict TypeScript, Rust, Python, or Go | `programming` |
+
+Start at [https://lazycodex.ai](https://lazycodex.ai).
+
<hr />
## πŸ’€ What is this?
diff --git a/packages/web/DESIGN.md b/packages/web/DESIGN.md
index ae12d761..7f9d8404 100644
--- a/packages/web/DESIGN.md
+++ b/packages/web/DESIGN.md
@@ -80,15 +80,21 @@ The landing page is a single scrollable document with the following sections, to
- `$start-work` β€” plan executor
- Each card has a monospace command header, a one-line description, and a syntax example
-5. **Ultrawork explainer**
+5. **Game development + skills guide**
+ - The existing three command cards remain the main pillars and appear before this guide
+ - Adds "Build games with LazyCodex" positioning for large repos with gameplay, tools, data, launchers, editors, and build pipelines
+ - Calls out `/init-deep` as the map for messy project structure
+ - Lists skill-first workflows such as `review-work`, `remove-ai-slops`, `frontend-ui-ux`, `programming`, LSP, AST-grep, rules, and comment-checker
+
+6. **Ultrawork explainer**
- Short paragraph on what `ultrawork` means (OmO discipline mode, parallel agents, auto-verification)
- Link to the docs deep-dive
-6. **Docs CTA**
+7. **Docs CTA**
- Large button: "Read the docs"
- Secondary link: "View on GitHub"
-7. **Footer**
+8. **Footer**
- Sisyphus Labs co-brand strip (night + panel colors)
- Links: GitHub, OmO, sisyphuslabs.ai
- MIT license note
diff --git a/packages/web/app/docs/page.tsx b/packages/web/app/docs/page.tsx
index 3acc83f1..e9354382 100644
--- a/packages/web/app/docs/page.tsx
+++ b/packages/web/app/docs/page.tsx
@@ -1,14 +1,15 @@
+import type { Metadata } from "next";
+import { DocsShell } from "@/components/docs/docs-shell";
+import { SiteFooter } from "@/components/site/site-footer";
+import { SiteHeader } from "@/components/site/site-header";
import { DOC_SECTIONS } from "@/lib/docs-sections";
import { loadDocSource } from "@/lib/docs-source";
-import { SiteHeader } from "@/components/site/site-header";
-import { SiteFooter } from "@/components/site/site-footer";
-import { DocsShell } from "@/components/docs/docs-shell";
-import type { Metadata } from "next";
import "@/app/styles/docs.css";
export const metadata: Metadata = {
title: "Documentation",
- description: "LazyCodex documentation β€” install, ultrawork mode, $ulw-loop, $ulw-plan, $start-work.",
+ description:
+ "LazyCodex documentation β€” install, game-development workflows, skills, ultrawork mode, $ulw-loop, $ulw-plan, $start-work.",
alternates: {
canonical: "/docs",
},
@@ -27,7 +28,7 @@ export default function DocsPage() {
<div className="docs-hero">
<h1 className="docs-hero-title">Documentation</h1>
<p className="docs-hero-tagline">
- Learn how to install, configure, and use LazyCodex for ultrawork.
+ Learn how to install, configure, and use LazyCodex for ultrawork and skill-first workflows.
</p>
</div>
<DocsShell sections={sections}>
diff --git a/packages/web/app/page.tsx b/packages/web/app/page.tsx
index 18841e81..7c68db87 100644
--- a/packages/web/app/page.tsx
+++ b/packages/web/app/page.tsx
@@ -1,11 +1,12 @@
import type { JSX } from "react"
-import { SiteHeader } from "../components/site/site-header"
-import { Hero } from "../components/site/hero"
-import { InstallBlock } from "../components/site/install-block"
import { CommandCards } from "../components/site/command-cards"
-import { UltraworkSection } from "../components/site/ultrawork-section"
import { DocsCta } from "../components/site/docs-cta"
+import { GameDevSection } from "../components/site/game-dev-section"
+import { Hero } from "../components/site/hero"
+import { InstallBlock } from "../components/site/install-block"
import { SiteFooter } from "../components/site/site-footer"
+import { SiteHeader } from "../components/site/site-header"
+import { UltraworkSection } from "../components/site/ultrawork-section"
export default function LandingPage(): JSX.Element {
return (
@@ -25,6 +26,7 @@ export default function LandingPage(): JSX.Element {
</div>
<InstallBlock />
<CommandCards />
+ <GameDevSection />
<UltraworkSection />
<DocsCta />
</main>
diff --git a/packages/web/components/site/game-dev-section.tsx b/packages/web/components/site/game-dev-section.tsx
new file mode 100644
index 00000000..65194bcb
--- /dev/null
+++ b/packages/web/components/site/game-dev-section.tsx
@@ -0,0 +1,64 @@
+import type { JSX } from "react"
+import { SITE_CONFIG } from "../../lib/site-config"
+
+export function GameDevSection(): JSX.Element {
+ return (
+ <section className="mx-auto mt-24 w-full max-w-[1200px] px-4 md:mt-32 md:px-8">
+ <div className="grid gap-8 border-y border-white/10 py-12 md:grid-cols-[minmax(0,0.9fr)_minmax(0,1.1fr)] md:py-16">
+ <div>
+ <p className="font-mono text-xs uppercase text-[color:var(--accent-cyan)]">
+ {SITE_CONFIG.gameDev.kicker}
+ </p>
+ <h2 className="mt-4 text-balance text-[clamp(32px,5vw,56px)] font-medium leading-tight text-[color:var(--text-primary)]">
+ {SITE_CONFIG.gameDev.title}
+ </h2>
+ <p className="mt-6 max-w-[58ch] text-base leading-relaxed text-[color:var(--text-muted)] md:text-lg">
+ {SITE_CONFIG.gameDev.intro}
+ </p>
+ </div>
+
+ <div className="grid gap-3">
+ {SITE_CONFIG.gameDev.points.map((point, index) => (
+ <div
+ key={point.label}
+ className="grid gap-4 rounded-lg border border-white/10 bg-white/[0.03] p-5 md:grid-cols-[72px_1fr]"
+ >
+ <span className="font-mono text-xs uppercase text-[color:var(--text-tertiary)]">
+ {String(index + 1).padStart(2, "0")}
+ </span>
+ <div>
+ <h3 className="text-lg font-medium text-[color:var(--text-primary)]">
+ {point.label}
+ </h3>
+ <p className="mt-2 text-sm leading-relaxed text-[color:var(--text-muted)]">
+ {point.text}
+ </p>
+ </div>
+ </div>
+ ))}
+ </div>
+ </div>
+
+ <div className="mt-6 grid gap-4 rounded-lg border border-[color:var(--accent-cyan)]/20 bg-[color:var(--accent-cyan)]/5 p-5 md:grid-cols-[0.9fr_1.1fr] md:p-6">
+ <div>
+ <h2 className="text-2xl font-medium text-[color:var(--text-primary)]">
+ {SITE_CONFIG.skillWorkflow.title}
+ </h2>
+ <p className="mt-3 text-sm leading-relaxed text-[color:var(--text-muted)]">
+ {SITE_CONFIG.skillWorkflow.summary}
+ </p>
+ </div>
+ <ul className="grid grid-cols-2 gap-2 sm:grid-cols-4">
+ {SITE_CONFIG.skillWorkflow.skills.map((skill) => (
+ <li
+ key={skill}
+ className="rounded-md border border-white/10 bg-black/20 px-3 py-2 font-mono text-xs text-[color:var(--text-secondary)]"
+ >
+ {skill}
+ </li>
+ ))}
+ </ul>
+ </div>
+ </section>
+ )
+}
diff --git a/packages/web/content/docs/skills.md b/packages/web/content/docs/skills.md
new file mode 100644
index 00000000..0c1d19dc
--- /dev/null
+++ b/packages/web/content/docs/skills.md
@@ -0,0 +1,40 @@
+LazyCodex is most useful when the work is bigger than one prompt. Game projects are a good example: the codebase may include gameplay, tools, data, launchers, editors, and build pipelines in one repo.
+
+### Build games with LazyCodex
+
+Start with `/init-deep` when the repository is too large or too old to explain from memory. It generates hierarchical `AGENTS.md` context so agents can find the right files before they change code.
+
+Rerun `/init-deep` when milestones change. A new gameplay loop, content tool, asset pipeline, or launcher can change where the important context lives.
+
+### Skill-first workflows
+
+The three command pillars stay simple:
+
+- `$ulw-loop` keeps moving until verified completion
+- `$ulw-plan` turns fuzzy work into a decision-complete plan
+- `$start-work` executes a plan with durable Boulder progress
+
+Skills add specialist judgment around those pillars:
+
+| Skill | Use it for |
+| --- | --- |
+| `review-work` | Multi-angle post-implementation review |
+| `remove-ai-slops` | Behavior-preserving cleanup of AI-looking code |
+| `frontend-ui-ux` | Designed UI work instead of generic layout filling |
+| `programming` | Strict TypeScript, Rust, Python, or Go discipline |
+| `LSP` | Diagnostics, definitions, references, symbols, and renames |
+| `AST-grep` | Structural search and rewrite across code |
+| `rules` | Project instructions from AGENTS, rules, and instruction files |
+| `comment-checker` | Feedback after edit-like operations |
+
+### Where skills live
+
+OmO can load skills from project and user locations such as `.opencode/skills`, `~/.config/opencode/skills`, `.claude/skills`, `.agents/skills`, and `~/.agents/skills`.
+
+LazyCodex installs the Codex Light setup with:
+
+```bash
+npx lazycodex-ai install
+```
+
+That installer wires the Codex marketplace plugin as `omo@sisyphuslabs` while keeping the public package alias easy to remember.
diff --git a/packages/web/e2e/docs.spec.ts b/packages/web/e2e/docs.spec.ts
index c6e1faf0..cbb08c7e 100644
--- a/packages/web/e2e/docs.spec.ts
+++ b/packages/web/e2e/docs.spec.ts
@@ -32,7 +32,7 @@ test.describe("docs page β€” structure", () => {
}
})
- test("nav lists all six section titles as links or buttons", async ({ page }) => {
+ test("nav lists every section title as links or buttons", async ({ page }) => {
await page.goto("/docs")
const nav = page.getByRole("navigation")
for (const section of DOC_SECTIONS) {
@@ -59,6 +59,21 @@ test.describe("docs page β€” structure", () => {
.first(),
).toBeVisible()
})
+
+ test("documents skills and game-development usage", async ({ page }) => {
+ await page.goto("/docs")
+
+ const body = page.locator("body")
+ await expect(body).toContainText("Build games with LazyCodex")
+ await expect(body).toContainText("/init-deep")
+ await expect(body).toContainText("Skill-first workflows")
+ await expect(body).toContainText("review-work")
+ await expect(body).toContainText("remove-ai-slops")
+ await expect(body).toContainText("frontend-ui-ux")
+ await expect(body).toContainText("LSP")
+ await expect(body).toContainText("AST-grep")
+ await expect(body).toContainText("comment-checker")
+ })
})
test.describe("docs page β€” navigation", () => {
diff --git a/packages/web/e2e/landing.spec.ts b/packages/web/e2e/landing.spec.ts
index c68d360b..a965d890 100644
--- a/packages/web/e2e/landing.spec.ts
+++ b/packages/web/e2e/landing.spec.ts
@@ -53,6 +53,20 @@ test.describe("landing page β€” install + commands", () => {
await expect(page.getByText(command.syntax, { exact: false }).first()).toBeVisible()
}
})
+
+ test("game-development guidance keeps the three command pillars first", async ({ page }) => {
+ await page.goto("/")
+
+ await expect(page.locator("article h2")).toHaveText(COMMANDS.map((command) => command.name))
+ await expect(page.getByText("Build games with LazyCodex", { exact: false })).toBeVisible()
+ await expect(page.getByText("/init-deep", { exact: false }).first()).toBeVisible()
+ await expect(
+ page
+ .getByText("Tools, data, launchers, editors, and build pipelines", { exact: false })
+ .first(),
+ ).toBeVisible()
+ await expect(page.getByText("Skill-first workflows", { exact: false }).first()).toBeVisible()
+ })
})
test.describe("landing page β€” links + footer", () => {
diff --git a/packages/web/lib/docs-content.generated.ts b/packages/web/lib/docs-content.generated.ts
index 3a59930d..fbd888f2 100644
--- a/packages/web/lib/docs-content.generated.ts
+++ b/packages/web/lib/docs-content.generated.ts
@@ -2,6 +2,7 @@
export const DOC_SOURCES: Record<string, string> = {
"overview.md": "<p>LazyCodex is the lazy way to get <a href=\"https://github.com/code-yeongyu/oh-my-openagent\">oh-my-openagent</a> (OmO) up and running inside Codex. Think <a href=\"https://github.com/LazyVim/LazyVim\">LazyVim</a> for <a href=\"https://github.com/folke/lazy.nvim\">lazy.nvim</a>, but for Codex.</p>\n<h3>What you get</h3>\n<p>OmO is a full AI dev team in a harness. It gives you discipline agents (Sisyphus orchestrates Hephaestus, Oracle, and Librarian), parallel execution, multi-model routing, a skills system, hooks and lifecycle, and zero-config defaults. LazyCodex wraps the entire setup so you don&#39;t have to think about it.</p>\n<h3>The one-word workflow</h3>\n<p>You don&#39;t need to ultrathink. Just prompt with <code>{your prompt} ultrawork</code>. One word, and every agent activates.</p>\n<h3>How it fits together</h3>\n<p>LazyCodex is a thin distribution layer. The core engine is <a href=\"https://github.com/code-yeongyu/oh-my-openagent\">OmO</a>. LazyCodex is maintained by <a href=\"https://sisyphuslabs.ai\">Sisyphus Labs</a>.</p>\n<ul>\n<li><a href=\"https://github.com/code-yeongyu/lazycodex\">LazyCodex on GitHub</a></li>\n<li><a href=\"https://github.com/code-yeongyu/oh-my-openagent\">OmO on GitHub</a></li>\n</ul>\n",
"installation.md": "<p>One command gets you running. LazyCodex installs the Codex platform setup for OmO without a global package install.</p>\n<h3>Install</h3>\n<pre><code class=\"language-bash\">npx lazycodex-ai install\n</code></pre>\n<p>This is exactly equivalent to <code>npx --yes --package oh-my-openagent omo install --platform=codex</code>.</p>\n<h3>Autonomous one-liner</h3>\n<pre><code class=\"language-bash\">npx lazycodex-ai install --no-tui --codex-autonomous\n</code></pre>\n<h3>Prerequisites</h3>\n<ul>\n<li><a href=\"https://bun.sh\">Bun</a></li>\n<li>The <a href=\"https://github.com/openai/codex\">OpenAI Codex CLI</a></li>\n</ul>\n<blockquote>\n<p>Do NOT use <code>npm install -g</code> or <code>bun add -g</code>. Always invoke via <code>npx</code>.</p>\n</blockquote>\n<h3>Let an agent do it</h3>\n<p>It is strongly recommended to let an LLM agent run the install and walk the setup for you. The agent handles subscription detection, model selection, and provider auth automatically.</p>\n",
+ "skills.md": "<p>LazyCodex is most useful when the work is bigger than one prompt. Game projects are a good example: the codebase may include gameplay, tools, data, launchers, editors, and build pipelines in one repo.</p>\n<h3>Build games with LazyCodex</h3>\n<p>Start with <code>/init-deep</code> when the repository is too large or too old to explain from memory. It generates hierarchical <code>AGENTS.md</code> context so agents can find the right files before they change code.</p>\n<p>Rerun <code>/init-deep</code> when milestones change. A new gameplay loop, content tool, asset pipeline, or launcher can change where the important context lives.</p>\n<h3>Skill-first workflows</h3>\n<p>The three command pillars stay simple:</p>\n<ul>\n<li><code>$ulw-loop</code> keeps moving until verified completion</li>\n<li><code>$ulw-plan</code> turns fuzzy work into a decision-complete plan</li>\n<li><code>$start-work</code> executes a plan with durable Boulder progress</li>\n</ul>\n<p>Skills add specialist judgment around those pillars:</p>\n<table>\n<thead>\n<tr>\n<th>Skill</th>\n<th>Use it for</th>\n</tr>\n</thead>\n<tbody><tr>\n<td><code>review-work</code></td>\n<td>Multi-angle post-implementation review</td>\n</tr>\n<tr>\n<td><code>remove-ai-slops</code></td>\n<td>Behavior-preserving cleanup of AI-looking code</td>\n</tr>\n<tr>\n<td><code>frontend-ui-ux</code></td>\n<td>Designed UI work instead of generic layout filling</td>\n</tr>\n<tr>\n<td><code>programming</code></td>\n<td>Strict TypeScript, Rust, Python, or Go discipline</td>\n</tr>\n<tr>\n<td><code>LSP</code></td>\n<td>Diagnostics, definitions, references, symbols, and renames</td>\n</tr>\n<tr>\n<td><code>AST-grep</code></td>\n<td>Structural search and rewrite across code</td>\n</tr>\n<tr>\n<td><code>rules</code></td>\n<td>Project instructions from AGENTS, rules, and instruction files</td>\n</tr>\n<tr>\n<td><code>comment-checker</code></td>\n<td>Feedback after edit-like operations</td>\n</tr>\n</tbody></table>\n<h3>Where skills live</h3>\n<p>OmO can load skills from project and user locations such as <code>.opencode/skills</code>, <code>~/.config/opencode/skills</code>, <code>.claude/skills</code>, <code>.agents/skills</code>, and <code>~/.agents/skills</code>.</p>\n<p>LazyCodex installs the Codex Light setup with:</p>\n<pre><code class=\"language-bash\">npx lazycodex-ai install\n</code></pre>\n<p>That installer wires the Codex marketplace plugin as <code>omo@sisyphuslabs</code> while keeping the public package alias easy to remember.</p>\n",
"ultrawork.md": "<p>ultrawork is the headline mode. Typing <code>ultrawork</code> (or the short alias <code>ulw</code>) anywhere in your prompt activates maximum-precision, outcome-first, evidence-driven orchestration.</p>\n<blockquote>\n<p>&quot;One word. Every agent activates. Doesn&#39;t stop until done.&quot;</p>\n</blockquote>\n<h3>Usage</h3>\n<pre><code class=\"language-bash\">ulw add authentication\n</code></pre>\n<h3>What it enforces</h3>\n<ul>\n<li>Strict TDD: RED β†’ GREEN β†’ SURFACE β†’ CLEAN</li>\n<li>At least 3 realistic QA scenarios</li>\n<li>Real manual-QA channels (HTTP call, tmux, browser)</li>\n<li>A binding verification gate that loops until the work is genuinely done</li>\n</ul>\n",
"ulw-loop.md": "<p><code>$ulw-loop</code> is a self-referential development loop that runs until verified completion.</p>\n<h3>How it works</h3>\n<p>The agent works continuously and emits <code>&lt;promise&gt;DONE&lt;/promise&gt;</code> when it believes the task is complete, but that does NOT end the loop. An Oracle must verify the result first. The loop ends only after the system confirms Oracle verified it. If verification fails, it continues with the message: &quot;Oracle verification failed. Continuing ULTRAWORK loop.&quot;</p>\n<h3>Syntax</h3>\n<pre><code class=\"language-bash\">/ulw-loop &quot;task description&quot; [--completion-promise=TEXT] [--strategy=reset|continue]\n</code></pre>\n<h3>Limits</h3>\n<p>The iteration cap is 500 in ultrawork mode (100 in normal mode).</p>\n",
"ulw-plan.md": "<p><code>$ulw-plan</code> is the strategic planning consultant (Prometheus). It turns an idea into a decision-complete work plan. It is a planner, NOT an implementer. When you say &quot;do X&quot; it produces a plan for X and never writes product code.</p>\n<h3>The flow</h3>\n<ol>\n<li>Socratic interview</li>\n<li>Parallel codebase exploration</li>\n<li>Metis gap analysis</li>\n<li>Writes the plan to <code>plans/&lt;slug&gt;.md</code></li>\n<li>Optional Momus high-accuracy review</li>\n</ol>\n<h3>Output</h3>\n<p>Questions, research, and a work plan you can hand to <a href=\"#start-work\"><code>$start-work</code></a>.</p>\n",
diff --git a/packages/web/lib/docs-sections.ts b/packages/web/lib/docs-sections.ts
index eb1d6f89..ba972540 100644
--- a/packages/web/lib/docs-sections.ts
+++ b/packages/web/lib/docs-sections.ts
@@ -1,6 +1,7 @@
export type DocSectionId =
| "overview"
| "installation"
+ | "skills"
| "ultrawork"
| "ulw-loop"
| "ulw-plan"
@@ -15,6 +16,7 @@ export type DocSection = {
export const DOC_SECTIONS: readonly DocSection[] = [
{ id: "overview", file: "overview.md", title: "Overview" },
{ id: "installation", file: "installation.md", title: "Installation" },
+ { id: "skills", file: "skills.md", title: "Skills guide" },
{ id: "ultrawork", file: "ultrawork.md", title: "ultrawork mode" },
{ id: "ulw-loop", file: "ulw-loop.md", title: "$ulw-loop" },
{ id: "ulw-plan", file: "ulw-plan.md", title: "$ulw-plan" },
diff --git a/packages/web/lib/site-config.ts b/packages/web/lib/site-config.ts
index 985804c8..645a4bde 100644
--- a/packages/web/lib/site-config.ts
+++ b/packages/web/lib/site-config.ts
@@ -20,6 +20,32 @@ export const SITE_CONFIG = {
},
ultraworkTagline: "One word. Every agent activates. Doesn't stop until done.",
ultraworkExample: "ulw add authentication",
+ gameDev: {
+ kicker: "Field notes for large repos",
+ title: "Build games with LazyCodex",
+ intro:
+ "Game projects rarely fit a clean folder story. LazyCodex gives agents landmarks before they touch gameplay, tools, data, launchers, editors, and build pipelines.",
+ points: [
+ {
+ label: "/init-deep is the map",
+ text: "Generate hierarchical AGENTS.md context when a repo is too large, old, or cross-cutting to explain from memory.",
+ },
+ {
+ label: "The MVP is not the product",
+ text: "Keep the surrounding apps in scope: Tools, data, launchers, editors, and build pipelines are often where production risk lives.",
+ },
+ {
+ label: "Rerun it at milestones",
+ text: "Rerun it when the milestone changes so the project memory keeps matching the actual shape of the game.",
+ },
+ ],
+ },
+ skillWorkflow: {
+ title: "Skill-first workflows",
+ summary:
+ "The three command pillars stay up front. Skills add the specialist guidance for review, cleanup, UI, language discipline, LSP, AST-grep, rules, and comment-checker feedback.",
+ skills: ["review-work", "remove-ai-slops", "frontend-ui-ux", "programming", "LSP", "AST-grep", "rules", "comment-checker"],
+ },
} as const;
export type SiteConfig = typeof SITE_CONFIG;
diff --git a/packages/web/scripts/generate-docs-content.mjs b/packages/web/scripts/generate-docs-content.mjs
index 11ea7751..28883396 100644
--- a/packages/web/scripts/generate-docs-content.mjs
+++ b/packages/web/scripts/generate-docs-content.mjs
@@ -9,6 +9,7 @@ import { Marked } from "marked";
const SECTIONS = [
{ id: "overview", file: "overview.md" },
{ id: "installation", file: "installation.md" },
+ { id: "skills", file: "skills.md" },
{ id: "ultrawork", file: "ultrawork.md" },
{ id: "ulw-loop", file: "ulw-loop.md" },
{ id: "ulw-plan", file: "ulw-plan.md" },
diff --git a/test/no-launch-gating-text.test.mjs b/test/no-launch-gating-text.test.mjs
index 50d1f02b..01bac5b6 100644
--- a/test/no-launch-gating-text.test.mjs
+++ b/test/no-launch-gating-text.test.mjs
@@ -10,7 +10,7 @@ const BANNED_WORD_GROUPS = [
["coming", "june"],
["currently", "available", "for", "opencode"],
["codex", "edition", "is", "coming"],
- ["waitlist"],
+ ["wait" + "list"],
]
function trackedFiles() {
diff --git a/test/readme-game-dev-content.test.mjs b/test/readme-game-dev-content.test.mjs
new file mode 100644
index 00000000..c340374f
--- /dev/null
+++ b/test/readme-game-dev-content.test.mjs
@@ -0,0 +1,23 @@
+import { readFileSync } from "node:fs"
+import test from "node:test"
+import assert from "node:assert/strict"
+
+const README = readFileSync("README.md", "utf8")
+const HANGUL_PATTERN = /[\u1100-\u11ff\u3130-\u318f\uac00-\ud7af]/u
+
+test("README documents game-development workflows without Hangul", () => {
+ const requiredSnippets = [
+ "Build games with LazyCodex",
+ "/init-deep",
+ "Game projects rarely fit a clean folder story",
+ "Tools, data, launchers, editors, and build pipelines",
+ "Rerun it when the milestone changes",
+ "https://lazycodex.ai",
+ ]
+
+ for (const snippet of requiredSnippets) {
+ assert.match(README, new RegExp(snippet.replace(/[.*+?^${}()|[\]\\]/g, "\\$&")))
+ }
+
+ assert.doesNotMatch(README, HANGUL_PATTERN)
+})