@erclx/aitk 0.51.0 → 0.53.0

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "aitk",
   "description": "Automated governance, versioning, and discovery tools for Claude Code.",
-  "version": "0.51.0",
+  "version": "0.53.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/claude/skills/claude-design-extract/SKILL.md

@@ -33,6 +33,7 @@ Read these from the project root on both paths, skipping any that do not exist:
 - `CLAUDE.md`: voice, personality, spelling rules
 - `.claude/REQUIREMENTS.md`: the `## Personality` paragraph, worldview, non-goals
 - `.claude/standards/prose.md`: tone constraints
+- `.claude/standards/markdown.md`: punctuation and formatting constraints
 
 Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.
 
@@ -54,7 +55,7 @@ Use the returned content as the target shape. Keep every section heading and eve
 
 ## Step 4: fill the template
 
-Walk each section once. Follow `.claude/standards/prose.md` throughout: no em dashes, no semicolons, no marketing buzzwords. Use commas or separate sentences instead.
+Walk each section once. Follow `.claude/standards/markdown.md` for punctuation and `.claude/standards/prose.md` for word choice throughout: no em dashes, no semicolons, no marketing buzzwords. Use commas or separate sentences instead.
 
 Mark any cell not traced to a source value by appending ` ? verify` inside the cell value, never as a trailing column. The cell stays inside the table shape: `| #ffffff ? verify |`. A trailing `| ? verify` after the row breaks the parser. A prose section takes its uncertainty inline instead, for example `Proposed 150ms ease-out, not yet confirmed.`, because a trailing tag on a sentence renders raw in the preview.
 

package/claude/skills/claude-docs/SKILL.md

@@ -97,7 +97,7 @@ For each doc with relevant changes, apply updates following these rules. Read a
 
 - Update only the sections affected by session decisions.
 - Do not rewrite sections unrelated to what changed.
-- Follow `.claude/standards/prose.md` for all edits.
+- Follow `.claude/standards/prose.md` and `.claude/standards/markdown.md` for all edits.
 
 Write each updated file immediately. Claude Code's tool permission dialog is the confirmation gate. Do not wait for user input.
 

package/claude/skills/claude-memory-capture/SKILL.md

@@ -23,7 +23,8 @@ Read in parallel from the project root, skipping any that do not exist:
 - `CLAUDE.md`: Memory section rules, including save thresholds and file format overrides
 - `.claude/memory/index.md`: existing index, to avoid duplicates
 - `.claude/context/index.md`: the domain catalog Step 3 routes against
-- `.claude/standards/prose.md`: prose conventions applied to memory file bodies
+- `.claude/standards/prose.md`: voice and banned words applied to memory file bodies
+- `.claude/standards/markdown.md`: punctuation and formatting applied to memory file bodies
 
 Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.
 

package/claude/skills/claude-standards-audit/SKILL.md

@@ -9,6 +9,7 @@ description: Audits changed markdown files against every authoring standard that
 
 - Resolve the base ref first, per Diff baseline below, then scope the file list exactly as Step 1 does, fallback included. If no markdown files changed, stop: `✅ No markdown changes to audit.` A guard that reads bare local `main`, or that skips the unusable-baseline fallback, passes the skill clean on a branch it never read.
 - If neither `.claude/standards/prose.md` nor `${CLAUDE_SKILL_DIR}/../../standards/prose.md` is present, stop: `❌ prose.md standard not found. Install toolkit standards first.` Test the file rather than the directory, since a project that installed standards before a given file existed keeps the directory without ever receiving that file.
+- Apply the same test to `markdown.md`, stopping with its own name. It carries the character bans and the formatting rules, so a run reaching only `prose.md` reports word choice against a clean file and calls the pass complete.
 
 ## Diff baseline
 
@@ -72,7 +73,7 @@ Read each applicable standard once. For each changed file, audit against every r
 - **Pattern rules**: grep the file for every token the standard bans. Grep is authoritative. Reading alone misses occurrences.
 - **Judgment rules**: check each rule in context against the standard that states it.
 
-Every changed markdown file gets the prose pattern pass, since `.claude/standards/prose.md` applies to all of them. Take the banned tokens from that standard at read time rather than from a list held here.
+Every changed markdown file gets the prose pattern pass, since `.claude/standards/prose.md` and `.claude/standards/markdown.md` both apply to all of them. Take the banned tokens from those standards at read time rather than from a list held here. The banned words sit in the first and the banned characters in the second, so a pass reading one file finds half the tokens.
 
 ## Step 4: report
 
@@ -81,8 +82,9 @@ Group findings by file with line references, naming the standard each one comes
 ```markdown
 path/to/file.md
 
-- L12: `prose.md`, em dash in prose
-- L34: `prose.md`, semicolon used to join clauses
+- L12: `markdown.md`, em dash in prose
+- L34: `markdown.md`, semicolon used to join clauses
+- L51: `prose.md`, vague qualifier `simply`
 - L67: `context.md`, decision entry names no rejected alternative
 ```
 

package/claude/skills/create-skill/SKILL.md

@@ -9,7 +9,8 @@ disable-model-invocation: true
 Read these files from the project root in parallel:
 
 - `.claude/standards/skill.md`: skill structure, skill types, frontmatter fields, invocation rules
-- `.claude/standards/prose.md`: prose conventions for skill body text
+- `.claude/standards/prose.md`: voice and banned words for skill body text
+- `.claude/standards/markdown.md`: punctuation and formatting for skill body text
 
 Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.
 

package/claude/skills/create-snippet/SKILL.md

@@ -7,10 +7,11 @@ description: Creates a new snippet file in `snippets/` or `.claude/snippets/`. U
 
 Creates one snippet file. Read these files in parallel:
 
-- `.claude/standards/prose.md` from the project root: prose conventions for all generated text
+- `.claude/standards/prose.md` from the project root: voice and banned words for all generated text
+- `.claude/standards/markdown.md` from the project root: punctuation and formatting for all generated text
 - `${CLAUDE_SKILL_DIR}/references/snippets.md`: authoring conventions, invocation channels, use patterns
 
-Read `${CLAUDE_SKILL_DIR}/../../standards/prose.md` instead when the project does not have it.
+Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.
 
 ## Guards
 

package/claude/skills/create-snippet/references/snippets.md

@@ -13,7 +13,8 @@ Governs a snippet file: what one is for, whether a prompt qualifies as one, how
 Does not govern:
 
 - Skill folders, which carry frontmatter, references, and scripts a snippet has none of: `skill.md`
-- Voice, punctuation, and formatting in snippet prose: `prose.md`
+- Voice and word choice in snippet prose: `prose.md`
+- Punctuation and formatting in snippet prose: `markdown.md`
 
 ## What a snippet is
 

package/claude/skills/create-standard/SKILL.md

@@ -7,7 +7,8 @@ description: Creates a new standard file in `standards/` or `.claude/standards/`
 
 Creates one standard file. Read these files in parallel:
 
-- `.claude/standards/prose.md` from the project root: prose conventions for all generated text
+- `.claude/standards/prose.md` from the project root: voice and banned words for all generated text
+- `.claude/standards/markdown.md` from the project root: punctuation and formatting for all generated text
 - `.claude/standards/standard.md` from the project root: the meta-standard for shape, frontmatter, and structure
 
 Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.

package/claude/skills/docs-sync/SKILL.md

@@ -7,7 +7,8 @@ description: Rewrites stale `README.md` and `docs/*.md` sections based on change
 
 Read these files from the project root in parallel:
 
-- `.claude/standards/prose.md`: prose conventions for all generated text
+- `.claude/standards/prose.md`: voice and banned words for all generated text
+- `.claude/standards/markdown.md`: punctuation and formatting for all generated text
 - `.claude/standards/readme.md`: README structure, required sections, and content rules
 
 Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.

package/claude/skills/git-issue/SKILL.md

@@ -12,7 +12,8 @@ Format an issue from session context following the issue standard, then file it
 Read these in parallel:
 
 - `${CLAUDE_SKILL_DIR}/references/issue.md`: issue title, labels, body sections, and banned phrases
-- `.claude/standards/prose.md` from the project root: prose conventions for all generated text
+- `.claude/standards/prose.md` from the project root: voice and banned words for all generated text
+- `.claude/standards/markdown.md` from the project root: punctuation and formatting for all generated text
 
 Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.
 

package/claude/skills/git-issue/references/issue.md

@@ -14,7 +14,8 @@ Does not govern:
 
 - Pull request title and body: `pr.md`
 - Whether a phase label may appear in issue text: `versioning.md`
-- Voice, punctuation, and banned words in issue prose: `prose.md`
+- Voice and banned words in issue prose: `prose.md`
+- Punctuation and formatting in issue prose: `markdown.md`
 
 ## Title
 

package/claude/skills/git-pr/SKILL.md

@@ -11,7 +11,8 @@ Read these files in parallel:
 
 - `${CLAUDE_SKILL_DIR}/references/branch.md`: branch format, valid types, and constraints
 - `${CLAUDE_SKILL_DIR}/references/pr.md`: structure, rules, and banned phrases
-- `.claude/standards/prose.md` from the project root: prose conventions for all generated text
+- `.claude/standards/prose.md` from the project root: voice and banned words for all generated text
+- `.claude/standards/markdown.md` from the project root: punctuation and formatting for all generated text
 - `.claude/standards/versioning.md` from the project root: phase label vs semver discipline
 
 Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.

package/claude/skills/git-pr/references/pr.md

@@ -15,7 +15,8 @@ Does not govern:
 - Commit subject format, which shares the title form: `commit.md`
 - Branch naming: `branch.md`
 - Whether a phase label or a semver tag may appear in a title or body: `versioning.md`
-- Voice, punctuation, and banned words in pull request prose: `prose.md`
+- Voice and banned words in pull request prose: `prose.md`
+- Punctuation and formatting in pull request prose: `markdown.md`
 
 ## Title
 

package/claude/skills/git-split/references/pr.md

@@ -15,7 +15,8 @@ Does not govern:
 - Commit subject format, which shares the title form: `commit.md`
 - Branch naming: `branch.md`
 - Whether a phase label or a semver tag may appear in a title or body: `versioning.md`
-- Voice, punctuation, and banned words in pull request prose: `prose.md`
+- Voice and banned words in pull request prose: `prose.md`
+- Punctuation and formatting in pull request prose: `markdown.md`
 
 ## Title
 

package/claude/skills/git-stage/SKILL.md

@@ -8,7 +8,8 @@ description: Groups staged files by concern and generates one conventional commi
 Read these files in parallel:
 
 - `${CLAUDE_SKILL_DIR}/references/commit.md`: format, types, scopes, and constraints
-- `.claude/standards/prose.md` from the project root: prose conventions for all generated text
+- `.claude/standards/prose.md` from the project root: voice and banned words for all generated text
+- `.claude/standards/markdown.md` from the project root: punctuation and formatting for all generated text
 
 Read a standard from `${CLAUDE_SKILL_DIR}/../../standards/` instead when the project does not have it.
 

package/docs/agents/context-audit-checks.md

@@ -13,7 +13,9 @@ The required-section check reports what does not declare `## Overview` and `## L
 
 Which unit answers depends on the folder. Entries of the folder named under `.claude/` are one domain each, so each answers for itself and a finding names the entry. Entries of a folder a domain split into describe that one domain between them, so any sibling answers and a finding names the folder. Holding a split folder to the rule per file would report every child beside its `overview.md`, and rolling the named folder up would let one conforming entry stand in for every other domain sitting next to it.
 
-It reports rather than gates, the closer call because a missing section reads more like a fact than the other judgments. What settles it is that the standard sanctions omitting `## Layout` from a domain owning no paths in the repo, and no measure separates that from an entry that forgot it. A domain covering only external tools is that case, and it reports on every run. The JSON record carries the findings as `missingSections` and the list as `checkpoints.requiredSections`.
+It reports rather than gates by default, the closer call because a missing section reads more like a fact than the other judgments. What settles it is that the standard sanctions omitting `## Layout` from a domain owning no paths in the repo, and no measure separates that from an entry that forgot it. A domain covering only external tools is that case, and it reports on every run. The JSON record carries the findings as `missingSections` and the list as `checkpoints.requiredSections`.
+
+`--gate` promotes the finding to a failing exit code, which the seed stage runs and no other caller does. That mode needs an answer to the sanctioned omission above, so a file declaring `stub: true` in its frontmatter is dropped before the check and reported nowhere. Both are described in `context-audit.md`.
 
 ## Length and depth
 

package/docs/agents/context-audit.md

@@ -1,6 +1,6 @@
 ---
 title: Context audit
-description: Running the audit, its flags and folder scope, the exit codes, and the citation gate that is the only failing one
+description: Running the audit, its flags and folder scope, the exit codes, the citation gate, and the widened gate the seed stage runs
 ---
 
 # Context audit
@@ -13,6 +13,7 @@ aitk context audit --json
 aitk context audit --citations-only
 aitk context audit --folder context,diagrams
 aitk context audit --folder docs
+aitk context audit tooling/base/seeds --gate
 ```
 
 | Option             | Behavior                                                             |
@@ -20,6 +21,9 @@ aitk context audit --folder docs
 | `--json`           | Add a machine-readable record on stdout, keeping the frame           |
 | `--folder <list>`  | Comma-separated folder names (default: the three below)              |
 | `--citations-only` | Run the gating citation check alone, printing nothing when it passes |
+| `--gate`           | Fail on a missing required section or index drift as well            |
+
+`--citations-only` and `--gate` refuse together. The first runs the citation check alone, so the two findings the second adds are never measured, and a run honoring both would exit clean on a file short a required section.
 
 ## Folder scope
 
@@ -31,7 +35,36 @@ A run where no requested name resolves refuses, whichever list it read. Naming t
 
 ## Exit codes
 
-Exit codes are `0` for a clean run, `1` for a refusal, and `2` for an unresolved citation. Only the citation check sets a failing code. Required-section, length, depth, bullet weight, table, provenance, and index findings print and return `0`, because each is a judgment and failing a push on one would make the check something to route around.
+Exit codes are `0` for a clean run, `1` for a refusal, and `2` for a gating finding. An unresolved citation gates under every mode. Length, depth, bullet weight, table, and provenance findings print and return `0` under every mode, because each is a judgment and failing a push on one would make the check something to route around.
+
+Required-section and index findings sit between the two. Both are answerable from the file rather than weighed, so `--gate` promotes them to failing codes while a bare run leaves them advisory. The toolkit runs the bare form against itself and the widened form against the seed tree, described below.
+
+## The seed gate
+
+`bun run check` runs `--gate` against every `tooling/<stack>/seeds/` directory carrying a `.claude/` folder, discovered per run so a new stack is covered without a script edit. The seed tree installs into every scaffolded project, so a seed breaking the standard it seeds teaches the wrong shape to each one, and no rule path reaches the tree to report it.
+
+The widened gate is correct here and wrong at the project root. A seed is authored once and read by every target, while a context entry in a live project is edited under time pressure by the people who own it. A missing section in the first is a defect shipping outward, and in the second it is a threshold worth reporting and not worth blocking a push over.
+
+Coverage follows the index-plus-entry contract, so it reaches seeded entries and the indexes beside them. Seed files sitting directly under `.claude/`, currently `ARCHITECTURE.md`, `DESIGN.md`, and `REQUIREMENTS.md`, belong to no audited folder and stay outside it.
+
+The stage prints the entries it measured per root and warns on a root that measured none. A root can resolve an audited folder and hold no entry in it, which `tooling/claude/seeds` does today, so a single pass line over the set would report coverage of a tree nothing opened.
+
+It reads the exit code rather than pass against fail, since the two failing codes mean opposite things. A root carrying a `.claude/` that resolves no audited folder refuses at 1 and warns, while a seed short a required section gates at 2 and fails the push. A new stack seeding `.claude/` alone therefore reports what it is rather than a violation it does not have.
+
+### Exempting a skeleton
+
+A seed that deliberately omits a required section sets `stub: true` in its frontmatter, and the section check then skips it. Every other measure still reads the file, since a stub is exempt from owing sections rather than from being well formed.
+
+```markdown
+---
+title: Architecture
+stub: true
+---
+```
+
+Only `true` counts. A field holding anything else reads as a seed that meant to turn the exemption off, so a typo cannot silence the gate. Both install paths strip the field on the way into a target, which keeps toolkit bookkeeping out of a project whose own tooling would never read it. A block holding nothing else is dropped whole.
+
+The exemption exists because the section check has a false-positive class. A standard may sanction omitting a section, and no measure separates that from a file that forgot it, which is why the finding stays advisory everywhere the widened gate is not running. No seed sets the field today.
 
 ## The citation gate
 

package/docs/agents/index.md

@@ -12,7 +12,7 @@ CLI catalog and invocation rules for agents, split by command domain. Start with
 - [Command catalog](commands.md): Every project-level command and every domain subcommand, plus the shape each domain exposes
 - [Comments](comments.md): Comment density by language and kind, the two structural exclusions, and how the degradation sweep finds its vocabulary
 - [Context audit checks](context-audit-checks.md): What each non-gating check reports, the unit each checkpoint is measured in, and which folders each check reaches
-- [Context audit](context-audit.md): Running the audit, its flags and folder scope, the exit codes, and the citation gate that is the only failing one
+- [Context audit](context-audit.md): Running the audit, its flags and folder scope, the exit codes, the citation gate, and the widened gate the seed stage runs
 - [Docs](docs.md): How aitk docs resolves the toolkit's own reference surface from an install root, and how a split domain is named
 - [Indexes](indexes.md): Flags, exit codes, and JSON shape for aitk indexes regen, plus when it auto-stages what it rewrote
 - [Install and sync](install-and-sync.md): What each install and sync verb writes, refuses, or leaves alone, and how drift is attributed in a target project

package/docs/agents/install-and-sync.md

@@ -144,6 +144,12 @@ needs a stamp and seeds carry none, so a file history cannot attribute stays
 `drifted`. Reconcile the section with `claude-seed-sync`, which merges one
 section at a time rather than replacing a file the project edits.
 
+A markdown seed installs rewritten rather than copied, since the `stub: true`
+marker the toolkit's own seed gate reads is stripped on the way in. The
+comparison above runs against what the install would write, so a marked seed a
+target never touched still reports `matching`. Every other seed copies byte for
+byte.
+
 `superseded` names a file a newer seed folder replaced, such as `.claude/TASKS.md`
 against the `.claude/tasks/` that now ships. The entry carries `replacedBy` and
 nothing else, and the file is never deleted, since the content belongs to the

package/docs/ai-workflow.md

@@ -76,7 +76,7 @@ Run one orchestrator at a time. The board is gitignored, so a second session rea
 
 Before a handoff, the orchestrator checks the plan against the tree rather than reading it: grep each construct it names and count the sites, confirm every phase label it cites is still open, and open each file it describes. A plan goes stale from whatever merged after it was written, and reading cannot catch that.
 
-`.claude/plans/`, `.claude/review/`, and `.claude/memory/` all resolve at the main worktree root, so artifacts created in any session are visible from any sibling worktree. See [Claude Code and git worktrees](../wiki/claude-worktrees.md) for the full rule and the domain-level fan-out guidance.
+`.claude/plans/`, `.claude/review/`, and `.claude/memory/` all resolve at the main worktree root, so artifacts created in any session are visible from any sibling worktree. See [Claude Code and git worktrees](../wiki/claude/claude-worktrees.md) for the full rule and the domain-level fan-out guidance.
 
 A plan that ships is archived, never deleted. `aitk:claude-docs` moves it to `.claude/plans-archive/` and retargets the task file's `Plan:` line at the new location, so a completed task still leads to the reasoning behind it. Both folders are gitignored, which is why a deleted plan had no recovery path. A plan cited by more than one task stays put until the last of them closes, since moving it early would strand every other pointer.
 

package/docs/operating-model.md

@@ -10,7 +10,7 @@ A way to build fast and reliably across parallel Claude Code sessions without a
 loop and without losing the human review gate. One warm session plans and
 reviews. Cold worker sessions build. The human launches workers and merges. This
 page covers the roles and the loop. For the worktree mechanism (isolation, merge
-order, port collisions), see [Claude Code and git worktrees](../wiki/claude-worktrees.md).
+order, port collisions), see [Claude Code and git worktrees](../wiki/claude/claude-worktrees.md).
 
 ## Two roles
 
@@ -105,11 +105,11 @@ at two or three worker tracks and split them across the stack so they do not
 collide on the same files. Unit checks run freely in many worktrees at once.
 Only fixed-port work (a dev server, an end-to-end run, a screenshot) and
 singleton resources (one local model server, one GPU) serialize. See
-[Claude Code and git worktrees](../wiki/claude-worktrees.md) for merge order and the
+[Claude Code and git worktrees](../wiki/claude/claude-worktrees.md) for merge order and the
 port-collision detail.
 
 ## Related
 
-- [Claude Code and git worktrees](../wiki/claude-worktrees.md) for the isolation and fan-out mechanics
-- [Claude Code subagents](../wiki/claude-subagents.md) for in-session parallelism without worktrees
+- [Claude Code and git worktrees](../wiki/claude/claude-worktrees.md) for the isolation and fan-out mechanics
+- [Claude Code subagents](../wiki/claude/claude-subagents.md) for in-session parallelism without worktrees
 - `.claude/context/claude-plugin/skill-strategy.md` for how the skills in the loop are categorized

package/docs/visual-design-workflow.md

@@ -8,9 +8,9 @@ category: Workflow
 
 Three tiers cover the range from prose-only design docs to a fully graphical design source of truth. Pick one per project based on how UI-heavy the work is, whether stakeholders review visuals, and whether a designer is involved. Tiers stack, so moving up does not invalidate work done at a lower tier.
 
-The tier framework sits alongside [Claude Design](../wiki/claude-design.md), [visual wireframes](../wiki/visual-wireframes.md), [community skills and plugins](../wiki/community-skills.md), and [community MCP servers](../wiki/community-mcp-servers.md). Those pages catalog the tooling. This page decides when to reach for what.
+The tier framework sits alongside [Claude Design](../wiki/claude/claude-design.md), [visual wireframes](../wiki/tools/visual-wireframes.md), [community skills and plugins](../wiki/tools/community-skills.md), and [community MCP servers](../wiki/tools/community-mcp-servers.md). Those pages catalog the tooling. This page decides when to reach for what.
 
-Two tools anchor tier 1 and tier 2. [Stitch](../wiki/stitch.md) is the agent-addressable default through its MCP server at `stitch.googleapis.com/mcp`, with a free tier of 400 daily credits that covers daily iteration. [Claude Design](../wiki/claude-design.md), released 2026-04-17 and priced inside Claude subscriptions, is the ceiling tool reserved for codebase extraction and the richly annotated handoff bundle. Each covers a different job, they are not swappable.
+Two tools anchor tier 1 and tier 2. [Stitch](../wiki/tools/stitch.md) is the agent-addressable default through its MCP server at `stitch.googleapis.com/mcp`, with a free tier of 400 daily credits that covers daily iteration. [Claude Design](../wiki/claude/claude-design.md), released 2026-04-17 and priced inside Claude subscriptions, is the ceiling tool reserved for codebase extraction and the richly annotated handoff bundle. Each covers a different job, they are not swappable.
 
 ## Tier 0: prose only
 
@@ -51,16 +51,16 @@ Impeccable, if installed, keeps its own root `DESIGN.md` and `PRODUCT.md` in the
 
 ### Tools
 
-- Stitch via MCP at `stitch.googleapis.com/mcp`. Default pick for agent-driven visual generation. Free tier of 400 daily credits. See [Stitch](../wiki/stitch.md).
-- Excalidraw canvas server on localhost plus the `yctimlin/mcp_excalidraw` MCP shim, for projects that need an agent to draw, read back, and revise a canvas. See [visual wireframes](../wiki/visual-wireframes.md) for setup and footguns.
-- Playwright MCP for browser-side verification. See [Playwright](../wiki/community-mcp-servers.md#playwright-microsoft).
-- Chrome DevTools MCP for live frontend debugging. See [Chrome DevTools](../wiki/community-mcp-servers.md#chrome-devtools-google).
-- Claude Design as the ceiling option for codebase extraction or polished handoff bundles. See [Claude Design](../wiki/claude-design.md).
+- Stitch via MCP at `stitch.googleapis.com/mcp`. Default pick for agent-driven visual generation. Free tier of 400 daily credits. See [Stitch](../wiki/tools/stitch.md).
+- Excalidraw canvas server on localhost plus the `yctimlin/mcp_excalidraw` MCP shim, for projects that need an agent to draw, read back, and revise a canvas. See [visual wireframes](../wiki/tools/visual-wireframes.md) for setup and footguns.
+- Playwright MCP for browser-side verification. See [Playwright](../wiki/tools/community-mcp-servers.md#playwright-microsoft).
+- Chrome DevTools MCP for live frontend debugging. See [Chrome DevTools](../wiki/tools/community-mcp-servers.md#chrome-devtools-google).
+- Claude Design as the ceiling option for codebase extraction or polished handoff bundles. See [Claude Design](../wiki/claude/claude-design.md).
 
 ### Skills
 
 - Everything from tier 0
-- A frontend design skill to steer visual quality. Pick one of [Impeccable](../wiki/community-skills.md#pbakausimpeccable), [UI/UX Pro Max](../wiki/community-skills.md#nextlevelbuilderui-ux-pro-max-skill), or Anthropic's `frontend-design` plugin. Impeccable is the strongest default because of its curated anti-patterns.
+- A frontend design skill to steer visual quality. Pick one of [Impeccable](../wiki/tools/community-skills.md#pbakausimpeccable), [UI/UX Pro Max](../wiki/tools/community-skills.md#nextlevelbuilderui-ux-pro-max-skill), or Anthropic's `frontend-design` plugin. Impeccable is the strongest default because of its curated anti-patterns.
 
 ### When to pick
 
@@ -91,9 +91,9 @@ Design happens in a graphical tool. `.claude/DESIGN.md` either regenerates from
 
 ### Tools
 
-- Figma desktop app with the [Figma Dev Mode MCP](../wiki/community-skills.md#figma-mcp-and-code-to-canvas) for teams with a dedicated designer already on Figma. Bidirectional sync and Code to Canvas capture.
-- Claude Design with its Claude Code handoff bundle for teams without an existing Figma investment and for solo founders or PMs driving design themselves. One-way handoff, no bidirectional sync. See [Claude Design](../wiki/claude-design.md).
-- Stitch via MCP as a low-cost complement to either, used for bulk screen generation driven by Claude Code. See [Stitch](../wiki/stitch.md).
+- Figma desktop app with the [Figma Dev Mode MCP](../wiki/tools/community-skills.md#figma-mcp-and-code-to-canvas) for teams with a dedicated designer already on Figma. Bidirectional sync and Code to Canvas capture.
+- Claude Design with its Claude Code handoff bundle for teams without an existing Figma investment and for solo founders or PMs driving design themselves. One-way handoff, no bidirectional sync. See [Claude Design](../wiki/claude/claude-design.md).
+- Stitch via MCP as a low-cost complement to either, used for bulk screen generation driven by Claude Code. See [Stitch](../wiki/tools/stitch.md).
 - Playwright and Chrome DevTools MCPs as in tier 1
 
 ### Skills
@@ -128,9 +128,9 @@ Zero or one yes: tier 0. Two or three: tier 1. Four: tier 2. Resist over-tiering
 
 ## References
 
-- [Stitch](../wiki/stitch.md): Gemini-powered design product with the MCP server that anchors tier 1
-- [Claude Design](../wiki/claude-design.md): first-party hosted design product and handoff bundle
+- [Stitch](../wiki/tools/stitch.md): Gemini-powered design product with the MCP server that anchors tier 1
+- [Claude Design](../wiki/claude/claude-design.md): first-party hosted design product and handoff bundle
 - `.claude/context/claude-plugin/skill-strategy.md`: how to decide between workflow and domain-knowledge skills
-- [Visual wireframes](../wiki/visual-wireframes.md): Excalidraw research and setup for the tier 1 wireframe companion
-- [Community skills and plugins](../wiki/community-skills.md): catalog of frontend design skills and integrations
-- [Community MCP servers](../wiki/community-mcp-servers.md): catalog of MCPs referenced across all tiers
+- [Visual wireframes](../wiki/tools/visual-wireframes.md): Excalidraw research and setup for the tier 1 wireframe companion
+- [Community skills and plugins](../wiki/tools/community-skills.md): catalog of frontend design skills and integrations
+- [Community MCP servers](../wiki/tools/community-mcp-servers.md): catalog of MCPs referenced across all tiers

package/docs/zshrc-aliases.md

@@ -56,7 +56,7 @@ Use `clp` in any other repository where you want the toolkit skills available. W
 
 Use `cls` or `clps` to save Opus usage on routine sessions. Switch mid-session with `/model` to avoid restarting.
 
-Use `clw <name>` for features that will take more than one session. A worktree isolates the branch, the transcripts, and the `/resume` history. See [Claude Code and git worktrees](../wiki/claude-worktrees.md) for fan-out rules.
+Use `clw <name>` for features that will take more than one session. A worktree isolates the branch, the transcripts, and the `/resume` history. See [Claude Code and git worktrees](../wiki/claude/claude-worktrees.md) for fan-out rules.
 
 Use `clc` to resume the last session without a picker. Use `clr` when you have several sessions and need to pick by name or recency. Outside the toolkit repo, `clpc` is the same shortcut as `clc` with the plugin loaded.
 

package/governance/rules/claude/500-prose.md

@@ -1,5 +1,5 @@
 ---
-description: Route markdown edits to the prose standard for voice, structure, formatting, and punctuation
+description: Route markdown edits to the prose standard for voice, language, and frontmatter wording
 paths:
   - '**/*.md'
 ---
@@ -8,5 +8,6 @@ paths:
 
 ## Authority
 
-- Follow `.claude/standards/prose.md` for all prose: voice, structure, formatting, language, and banned punctuation. It is the single source.
-- Read it before a substantial prose edit. Do not work the bans from memory.
+- Follow `.claude/standards/prose.md` for voice, language, and the wording of a `title` or `description`. It is the single source.
+- Read it before a substantial prose edit. Do not work the banned words from memory.
+- Punctuation, formatting, and file references are a separate topic. `501-markdown` routes them.

package/governance/rules/claude/501-markdown.md

@@ -0,0 +1,13 @@
+---
+description: Route markdown edits to the markdown standard for headings, lists, punctuation, and file references
+paths:
+  - '**/*.md'
+---
+
+# Markdown mechanics standards
+
+## Authority
+
+- Follow `.claude/standards/markdown.md` for headings, paragraph and list structure, code spans, punctuation, emphasis, and file references. It is the single source.
+- Read it before a substantial markdown edit. Do not work the banned characters from memory.
+- Voice, language, and frontmatter wording are a separate topic. `500-prose` routes them.

package/governance/stacks/base.toml

@@ -1,2 +1,2 @@
 extends = ""
-rules = ["000-constitution", "010-testing", "020-concurrency", "030-error-handling", "040-performance", "050-logging", "060-naming", "070-planning", "080-config-comments", "090-code-comments", "500-prose", "510-context", "520-wireframes", "530-requirements", "540-architecture", "550-design", "555-tasks", "560-diagrams", "570-skill", "580-readme", "590-rule-authoring", "591-standard-authoring"]
+rules = ["000-constitution", "010-testing", "020-concurrency", "030-error-handling", "040-performance", "050-logging", "060-naming", "070-planning", "080-config-comments", "090-code-comments", "500-prose", "501-markdown", "510-context", "520-wireframes", "530-requirements", "540-architecture", "550-design", "555-tasks", "560-diagrams", "570-skill", "580-readme", "590-rule-authoring", "591-standard-authoring"]

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/aitk",
   "type": "module",
-  "version": "0.51.0",
+  "version": "0.53.0",
   "description": "Infrastructure and quality tooling for developer workflows",
   "license": "MIT",
   "bin": {

package/scripts/core/install-check.sh

@@ -79,7 +79,7 @@ log_step "Assert scaffold"
 # The snippets path has to name a slug the default preset still carries, since
 # init resolves snippets through `essentials`. Editing that preset without
 # editing this line fails the gate on a correct install.
-for path in "CLAUDE.md" ".claude/snippets/decision-help.md" ".claude/standards/prose.md" ".claude/wiki/index.md" ".claude" ".claude/context/index.md" ".claude/wireframes/index.md" ".claude/diagrams/index.md" \
+for path in "CLAUDE.md" ".claude/snippets/decision-help.md" ".claude/standards/prose.md" ".claude/standards/markdown.md" ".claude/wiki/index.md" ".claude" ".claude/context/index.md" ".claude/wireframes/index.md" ".claude/diagrams/index.md" \
   ".prettierrc" ".editorconfig" ".lintstagedrc" ".husky/pre-commit" ".github/workflows/verify.yml" "scripts/verify.sh" \
   ".claude/rules/core/000-constitution.md"; do
   if [ ! -e "$TARGET_DIR/$path" ]; then

package/scripts/core/verify.sh

@@ -116,6 +116,28 @@ assert_hero_pair() {
   [ "$html_commit" = "$png_commit" ]
 }
 
+# Whatever stacks the repo currently carries, so a new one is covered without an
+# edit here. A seed root holding no `.claude/` seeds nothing a standard governs.
+collect_seed_roots() {
+  local dir
+  for dir in "$PROJECT_ROOT"/tooling/*/seeds; do
+    [ -d "$dir/.claude" ] || continue
+    printf '%s\n' "${dir#"$PROJECT_ROOT"/}"
+  done
+}
+
+# Entries the audit actually measured, summed across the folders it resolved.
+# `--json` carries one `"entries":<n>` per folder object, and the top-level key
+# of that name holds an array, so the numeric match reaches folders alone.
+#
+# A root can resolve a folder and measure nothing in it, which is a passing gate
+# over an empty set. The stage prints this per root rather than reporting one
+# verdict for every root, or a tree nobody measured reads as a tree that passed.
+seed_entry_count() {
+  printf '%s' "$1" | grep -o '"entries":[0-9]\+' | grep -o '[0-9]\+' |
+    awk '{ total += $1 } END { print total + 0 }'
+}
+
 assert_no_drift() {
   local paths=$1
   local err_msg=$2
@@ -183,6 +205,67 @@ main() {
   run_check "cd $PROJECT_ROOT && bun src/cli.ts context audit --citations-only" "A cited context path does not resolve. Run bun src/cli.ts context audit."
   log_info "Context citations resolve"
 
+  # The stage above audits this repository. Its seed tree ships into every
+  # scaffolded project, so a seed breaking the standard it seeds propagates
+  # instead of sitting still, and no rule path reaches the tree to report it.
+  # `--gate` fails on the two findings beside citations that are facts, a
+  # missing required section and index drift, and leaves the thresholds
+  # advisory for the reason the stage above leaves them so. A passing run stays
+  # silent because the audit prints a frame that would nest inside this one.
+  log_step "Seed standards"
+  local seed_roots seed_root seed_output seed_frame seed_entries seed_measured seed_status
+  seed_roots=$(collect_seed_roots)
+  if [ -z "$seed_roots" ]; then
+    log_info "Skipped, no seed root carries .claude/"
+  else
+    seed_measured=0
+    while IFS= read -r seed_root; do
+      # `--json` puts the record on stdout and the frame on stderr, so the
+      # passing run stays silent and the failing one is re-run for its frame
+      # rather than parsed out of a stream this script would have to strip.
+      seed_status=0
+      seed_output=$(cd "$PROJECT_ROOT" && bun src/cli.ts context audit "$seed_root" --gate --json 2>/dev/null) || seed_status=$?
+
+      # The audit separates 1 from 2 and they mean opposite things. 2 is a seed
+      # breaking the standard it seeds. 1 is the audit refusing, which a seed
+      # root carrying no audited folder produces, and reporting that as a
+      # violation sends a reader hunting one that does not exist. Discovery is
+      # what puts this in reach, since a new stack seeding `.claude/` alone
+      # arrives here with no edit to this script.
+      case $seed_status in
+      0) ;;
+      1)
+        log_warn "$seed_root: no audited folder under .claude/, nothing measured"
+        continue
+        ;;
+      *)
+        # `|| true` because the re-run exits non-zero by construction, and
+        # `set -e` would take the script down before log_error names the root.
+        seed_frame=$(cd "$PROJECT_ROOT" && bun src/cli.ts context audit "$seed_root" --gate 2>&1 || true)
+        echo "$seed_frame" | pipe_output
+        if [ "$seed_status" -eq 2 ]; then
+          log_error "A seed breaks the standard governing the folder it seeds: $seed_root"
+        else
+          log_error "The seed audit exited $seed_status against $seed_root, which is neither a pass nor a finding."
+        fi
+        ;;
+      esac
+
+      seed_entries=$(seed_entry_count "$seed_output")
+      seed_measured=$((seed_measured + seed_entries))
+
+      if [ "$seed_entries" -eq 0 ]; then
+        log_warn "$seed_root: no entry under an audited folder, nothing measured"
+      else
+        log_info "$seed_root: $seed_entries entries measured"
+      fi
+    done <<<"$seed_roots"
+
+    if [ "$seed_measured" -eq 0 ]; then
+      log_warn "No seed entry was measured. The stage covered nothing."
+    fi
+  fi
+
   # Presence of a required file is a fact, so it gates. The name, description,
   # folder, and requirement-section measures beside it report and are read from a
   # bare run. `bun src/cli.ts` for the reason the stage above uses it, and the