@erclx/canon 4.127.0 → 5.2.0

package/standards/skill.md

@@ -17,7 +17,6 @@ Does not govern:
 
 - What a `REQUIREMENT.md` must answer, its sections, and its template: `skill-requirement.md`
 - Path-scoped coding rules, which load on a file match rather than on a request match: `rule.md`
-- Single-purpose chat prompts carrying no frontmatter, references, or scripts: `snippets.md`
 - Voice, rhythm, and sentence construction in a skill body: the `write-human` skill
 - Punctuation, formatting, and word choice in a skill body: `markdown.md`
 - The transform from a branch name to a slug a skill carries in a filename: `slug.md`
@@ -128,7 +127,7 @@ allowed-tools: <tools required>
 
 - Avoid flags that dispatch between alternate flows. The model misreads them and runs the vanilla path. Dry-run-style toggles are fine. For alternate flows, prefer a separate skill or manual invocation of two skills in sequence.
 - When a skill should fire from multiple callers, rely on description matching with strong trigger phrases. Do not hardcode `Skill` calls in sibling skills that could trigger it naturally.
-- Before collapsing a manual multi-step flow into a skill, ask what the manual pauses do. Where a pause carries external timing, error-surfacing, or judgment weight, prefer a snippet or explicit per-step confirmation.
+- Before collapsing a manual multi-step flow into a skill, ask what the manual pauses do. Where a pause carries external timing, error-surfacing, or judgment weight, prefer explicit per-step confirmation.
 
 ### Output and tuning
 

package/standards/wiki.md

@@ -37,7 +37,8 @@ A page failing either is non-conforming even when it satisfies every shape rule
 
 ## Naming
 
-- Name a page with a `claude-` prefix before the kebab subject.
+- Name a page by its kebab subject alone. The vendor folder it sits in already names the vendor, so a prefix repeats the folder.
+- The `codebase-layout` skill carries the same rule for every folder in a project, beyond the wiki.
 
 ## Sourcing
 

package/tooling/base/reference.md

@@ -4,7 +4,7 @@
 
 The base layer covers every project the toolkit scaffolds, whatever language sits on top. It ships formatting, spelling, shell linting, conventional commits, git hooks, CI, and one maintenance script. Every other stack extends it, so a decision made here is one every stack inherits.
 
-A repository with several language roots layers this stack once at the root and skips it per subtree, since git honors only one `core.hooksPath` and a re-dropped husky silently breaks. `canon docs target-scenarios` carries the recipe.
+A repository with several language roots layers this stack once at the root and skips it per subtree, since git honors only one `core.hooksPath` and a re-dropped husky silently breaks. `canon docs scenarios` carries the recipe.
 
 ## What ships as golden configs
 
@@ -97,4 +97,4 @@ Sticky negative knowledge. Do not relearn.
 
 `bun run check` repairs a checkout rather than gating one. It runs `format` first to auto-fix drifted code, then asserts only what the formatters could not fix. The pull request workflow calls `check:format`, `check:spell`, and `check:shell` directly, and those three are the gate.
 
-`scripts/verify.sh`'s `Markdown bans` stage is the exception: it gates rather than repairs. It runs `canon markdown audit` over every tracked markdown file except `CHANGELOG.md`, since a generated changelog carries commit subjects nobody wrote against the ban set, and exits `2` on a finding or `3` on a shipped-empty ban set, failing `bun run check` and the `pre-push` hook that calls it. A refusal to measure exits `1` and is logged as a skip rather than a failure, as does a corpus with no file left to check once `CHANGELOG.md` is set aside. The stage needs `canon` on PATH. `canon docs target-projects` names the install command. Without it, the stage is skipped and logged, and coverage falls back to the three checks above.
+`scripts/verify.sh`'s `Markdown bans` stage is the exception: it gates rather than repairs. It runs `canon markdown audit` over every tracked markdown file except `CHANGELOG.md`, since a generated changelog carries commit subjects nobody wrote against the ban set, and exits `2` on a finding or `3` on a shipped-empty ban set, failing `bun run check` and the `pre-push` hook that calls it. A refusal to measure exits `1` and is logged as a skip rather than a failure, as does a corpus with no file left to check once `CHANGELOG.md` is set aside. The stage needs `canon` on PATH. `canon docs projects` names the install command. Without it, the stage is skipped and logged, and coverage falls back to the three checks above.

package/tooling/claude/reference.md

@@ -82,7 +82,7 @@ The first entry covers the whole record root, so a record folder added later nee
 ## CLAUDE.md
 
 - Ships as a seed with placeholder project name, description, and key paths. Fill these in after init.
-- Section layout: `Context`, `Indexes`, `Markdown`, `Key paths`, `Spelling`, `Snippets`, `Tasks`, `Memory`. Each section groups rules that share a surface so skills can detect, extend, or skip by heading.
+- Section layout: `Context`, `Indexes`, `Markdown`, `Key paths`, `Spelling`, `Tasks`, `Memory`. Each section groups rules that share a surface so skills can detect, extend, or skip by heading.
 - The memory rules favor signal over volume. Saving only after a second occurrence or an explicit user correction keeps entries focused on patterns worth preventing, not first-occurrence slips. The 3-line cap stops the built-in auto-memory from drifting into narrative writeups that bury the rule underneath the recovery story.
 - The `Context` section points at `.claude/` state docs one line. `plan-feature` does the parallel read when invoked. The seed intentionally does not re-list every file.
 

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

@@ -1,39 +0,0 @@
----
-name: create-snippet
-description: Why a snippet needs its shape read from the reference and its write surface resolved before anything is drafted
----
-
-# Create snippet requirement
-
-## Gap
-
-Without this skill, a snippet is drafted the way any other markdown file is drafted, so it arrives carrying frontmatter, headings, and a fill-in placeholder. None of the invocation channels strip those. Typing `>slug` in a chat inserts the scaffolding verbatim, and the file that was meant to be one instruction reads as a document.
-
-The write surface is the second failure. The toolkit authors at `snippets/` and a target project may still hold a stale `.claude/snippets/` copy from before that domain's install channel retired, so a session picks whichever folder it noticed first. A toolkit snippet written into the consumed copy fails the drift assertion that regenerates that folder. A snippet written there in a target project is correct and looks identical, which is why the surface has to be resolved from what the project has rather than guessed.
-
-Inside the project surface, a third failure sits one level deeper. A project-authored snippet sharing a name with a toolkit one used to be indistinguishable from it, back when `canon snippets sync` walked that folder and could not tell which side owned the file. That verb retired with the domain's install channel, so nothing reads ownership by location there any more, but the `project/` subfolder still separates the two by eye, which is worth keeping even with no sync left to protect from.
-
-## Must
-
-- Read the bundled snippet reference before drafting, since the shape rules are what the invocation channels depend on
-- Resolve the write surface from which snippet folder the project has, rather than from whichever one the session noticed first
-- On the project surface, write under its `project/` subfolder, keeping a project-authored file visually apart from a toolkit-installed one
-- Confirm the slug and the full body with the user before writing
-- Emit the written path in full, so the terminal can resolve it
-- State what the resolved surface implies after writing, since a root file needs the consumed copy regenerated and a project-local one needs copying to the toolkit to ship
-
-## Must not
-
-- Restate the snippet authoring conventions in the body, which the bundled reference owns and which would drift from it
-- Write a standard, which answers to a different authoring contract
-
-## Guards
-
-- Neither snippet folder exists: stop, since there is nowhere for the snippet to live
-
-## Out of scope
-
-- Editing a snippet that already exists
-- A standard, which `create-standard` owns
-- Installing and syncing the snippets the toolkit ships, which the `canon snippets` commands own
-- What a snippet is and how it is invoked, which the bundled snippet reference states

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

@@ -1,30 +0,0 @@
----
-name: create-snippet
-description: Creates a new snippet file in `snippets/` or `.claude/snippets/`. Use when asked to "create a snippet", add a snippet, write a reusable prompt, or make a new snippet. Do NOT use to edit an existing snippet.
----
-
-# Create snippet
-
-Creates one snippet file. Read these files in parallel:
-
-- `${CLAUDE_SKILL_DIR}/../../standards/markdown.md`: punctuation and formatting for all generated text
-- The `write-human` skill: voice, rhythm, and sentence construction for all generated text
-- `${CLAUDE_SKILL_DIR}/../../standards/snippets.md`: authoring conventions, invocation channels, use patterns
-
-## Guards
-
-- If neither `snippets/` nor `.claude/snippets/` exists, stop: `❌ No snippets/ or .claude/snippets/ directory found.`
-
-## Steps
-
-1. Resolve the write surface: `snippets/` at the root if present, which is the toolkit's own authoring source. Otherwise `.claude/snippets/`, a stale copy a target project holds from before its install channel retired.
-2. Draft the content from the user's description. The snippet reference governs structure, invocation, and authoring conventions.
-3. Confirm the slug and full content with the user before writing
-4. Write the file. On the root surface: `<surface>/<category>/<slug>.md`, or `<surface>/<slug>.md` when the snippet takes no category. On the `.claude/` surface: the same shape nested one level deeper under `project/`, a convention kept for its own sake now that nothing syncs that folder.
-
-## After writing
-
-Emit the full path on its own line.
-
-- Root surface: this is the toolkit's authoring source. Remind the user to run `bun run check` to regenerate the consumed copy under `.claude/`.
-- `.claude/` surface: the file is project-local, under `.claude/snippets/project/`. Remind the user to copy it to the toolkit repo, under `snippets/<category>/<name>.md`, if it should ship to every project.

package/scripts/snippets/create.sh

@@ -1,156 +0,0 @@
-#!/usr/bin/env bash
-set -e
-set -o pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="${PROJECT_ROOT:-$(dirname "$(dirname "$SCRIPT_DIR")")}"
-
-source "$PROJECT_ROOT/scripts/lib/ui.sh"
-trap close_timeline EXIT
-
-SNIPPETS_SOURCE="$PROJECT_ROOT/snippets"
-
-show_help() {
-  echo -e "${GREY}┌${NC}"
-  echo -e "${GREY}├${NC} ${WHITE}Usage:${NC} canon snippets create"
-  echo -e "${GREY}│${NC}"
-  echo -e "${GREY}│${NC}  Creates a new snippet: prompts for category and name, writes the file."
-  echo -e "${GREY}│${NC}"
-  echo -e "${GREY}│${NC}  ${WHITE}Options:${NC}"
-  echo -e "${GREY}│${NC}    -h, --help    ${GREY}# Show this help message${NC}"
-  echo -e "${GREY}└${NC}"
-  exit 0
-}
-
-list_categories() {
-  echo "base (root, no prefix)"
-  find "$SNIPPETS_SOURCE" -mindepth 1 -maxdepth 1 -type d -exec basename {} \; | sort
-  echo "new category"
-}
-
-slug_error() {
-  local slug="$1"
-  local path="$2"
-  if [ -z "$slug" ]; then
-    echo "name cannot be empty"
-    return
-  fi
-  if [[ ! "$slug" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then
-    echo "kebab-case only (e.g. my-snippet)"
-    return
-  fi
-  if [ -f "$path" ]; then
-    echo "file already exists: $path"
-    return
-  fi
-  echo ""
-}
-
-ask_new_category() {
-  while true; do
-    ask "Category name?" "CATEGORY_INPUT"
-    if [ -z "$CATEGORY_INPUT" ]; then
-      log_warn "Category name cannot be empty"
-      continue
-    fi
-    if [[ ! "$CATEGORY_INPUT" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then
-      log_warn "Invalid category: kebab-case only (e.g. my-category)"
-      continue
-    fi
-    if [ -d "$SNIPPETS_SOURCE/$CATEGORY_INPUT" ]; then
-      log_warn "Category '$CATEGORY_INPUT' already exists"
-      continue
-    fi
-    CATEGORY_NAME="$CATEGORY_INPUT"
-    break
-  done
-}
-
-ask_name() {
-  local category="$1"
-  local is_base="$2"
-  local label
-  local error
-
-  label="Snippet name?"
-
-  while true; do
-    ask "$label" "NAME_INPUT"
-    local dest_path
-    if [ "$is_base" = "true" ]; then
-      dest_path="$SNIPPETS_SOURCE/$NAME_INPUT.md"
-    else
-      dest_path="$SNIPPETS_SOURCE/$category/$NAME_INPUT.md"
-    fi
-    error=$(slug_error "$NAME_INPUT" "$dest_path")
-    if [ -z "$error" ]; then
-      NAME="$NAME_INPUT"
-      break
-    fi
-    log_warn "Invalid name: $error"
-  done
-}
-
-cmd_create() {
-  local categories=()
-  mapfile -t categories < <(list_categories)
-
-  select_option "Category?" "${categories[@]}"
-  local selected="$SELECTED_OPTION"
-
-  local category
-  local is_base="false"
-
-  if [ "$selected" = "base (root, no prefix)" ]; then
-    is_base="true"
-    category="base"
-  elif [ "$selected" = "new category" ]; then
-    ask_new_category
-    category="$CATEGORY_NAME"
-  else
-    category="$selected"
-  fi
-
-  ask_name "$category" "$is_base"
-  local name="$NAME"
-
-  local dest_path
-  local install_path
-  if [ "$is_base" = "true" ]; then
-    dest_path="$SNIPPETS_SOURCE/$name.md"
-    install_path="snippets/$name"
-  else
-    dest_path="$SNIPPETS_SOURCE/$category/$name.md"
-    install_path="snippets/$category/$name"
-  fi
-
-  log_info "Installs as: @${install_path}"
-
-  log_step "Creating file"
-
-  if [ "$is_base" = "false" ]; then
-    mkdir -p "$SNIPPETS_SOURCE/$category"
-  fi
-
-  printf '<!-- TODO: write %s prompt -->\n' "$slug" >"$dest_path"
-
-  if [ "$is_base" = "true" ]; then
-    log_add "snippets/$name.md"
-  else
-    log_add "snippets/$category/$name.md"
-  fi
-}
-
-main() {
-  if [ "$1" = "-h" ] || [ "$1" = "--help" ]; then
-    show_help
-  fi
-
-  cmd_create
-
-  trap - EXIT
-  echo -e "${GREY}└${NC}\n"
-  echo -e "${GREEN}✓ Snippet created${NC}"
-}
-
-main "$@"

package/snippets/align.md

@@ -1,12 +0,0 @@
-Check alignment before acting, not after. State three lines, then proceed.
-
-- Outcome: what will be true when this is done
-- Scope: what this deliberately does not touch
-- Assumption: the one inference that would change the work if it is wrong
-
-Act without waiting, unless being wrong about the assumption wastes the work rather than costing an edit.
-
-- Three lines, not three paragraphs
-- Name the inference you are least sure of, not the safest one
-- Do not ask what the request already answers
-- Silence is agreement

package/snippets/claude/decision-memo.md

@@ -1,39 +0,0 @@
-Produce a decision memo for a research or should-we question. This is the decision-heavy counterpart to `plan-feature`, which plans a build. Write one file per independent concern under `.canon/plans/feature-<slug>.md`, or answer inline when the plan is small. Use the same plans folder as `plan-feature`.
-
-Read the current state from the code and docs before recommending. Do not assume it.
-
-Output this shape per memo:
-
-```markdown
-# <slug title>
-
-<the question in one or two lines>
-
-## Summary
-
-- <goal in one line>
-- <deliverables in one line>
-- <key tradeoff in one line>
-
-## Finding
-
-<what the current state actually is, from reading the code and docs>
-
-## Item A: <decision>
-
-**Current state.** <what exists today>
-
-**Recommendation.** <the pick, with the tradeoff in one sentence>
-
-**Options.** <the real alternatives, only when the choice is the user's to make>
-
-**Feasibility.** <what is not buildable as asked and why, omit when all options are buildable>
-
-**Questions.**
-
-1. <question>
-   - Suggested: <best-practice default derived from context>
-   - Answer:
-```
-
-Repeat the `## Item` block per decision. Keep chat to the file pointer plus the questions. Recommend, do not enumerate, unless the user's preference is the deciding factor.

package/snippets/claude/feature-recap.md

@@ -1,19 +0,0 @@
-Recap the implementation this session completed. Read the plan file referenced in the session (usually `.canon/plans/feature-<slug>.md`) and produce a verification block.
-
-Output this shape, nothing else:
-
-```markdown
-**Deliverable 1**: <name from the plan>
-
-- `path/to/file`: one-line reason
-
-**Deliverable 2**: <name from the plan>
-
-- `path/to/file`: one-line reason
-
-**Verified**: <what was smoke-tested or `Nothing tested in session.`>
-
-**Open**: <unresolved questions, deferred items, or `None.`>
-```
-
-Group files by deliverable, not by directory. Keep each line scannable. Do not restate the plan body.

package/snippets/claude/figma-steps.md

@@ -1,24 +0,0 @@
-Read the relevant spec from `canon/DESIGN.md` and any other design files needed. Write step-by-step Figma instructions to produce the component exactly.
-
-For each step, specify:
-
-- The exact tool or keyboard shortcut to activate
-- Which panel or field to click
-- The exact value to enter
-
-When a step has multiple sub-actions or lists several items, use nested bullets instead of stacking them in one sentence.
-
-Cover in order:
-
-- Frame or group setup (dimensions, corner radius, fill)
-- Each layer or shape (type, size, position, fill, stroke)
-- Alignment and spacing rules
-- Export settings
-
-Throughout:
-
-- Use exact values from the spec
-- Do not restate design rationale
-- Use Title Case for all layer and frame names
-- Use Figma terminology throughout, not code or CSS equivalents
-- Reuse existing frames or components from the same Figma document by name instead of rebuilding from scratch

package/snippets/compact-summary.md

@@ -1,5 +0,0 @@
-Summarize the research or findings above into a compact, scannable block.
-
-- State the main takeaways directly
-- Skip background context the reader already has
-- Use short headings and tight bullets where multiple items exist

package/snippets/decision-help.md

@@ -1,6 +0,0 @@
-Apply senior-level judgment. Pick the best option from the discussion so far. State the pick in one sentence, then the reason and the main tradeoff in one or two sentences.
-
-- Minimal and necessary only
-- No nice-to-haves
-- No padding
-- No alternatives unless they change the recommendation

package/snippets/meta-prompt.md

@@ -1,14 +0,0 @@
-Turn the idea below into a production-grade system prompt.
-
-Give it a role of one to three lines, a constraints section, and an output format carrying a template plus one worked example. Add a validation checklist when the prompt involves multi-step logic, edge cases, or error handling. Omit that checklist for a single-purpose prompt.
-
-Group constraints under domain headings when they span two or more domains and total five or more. Use flat must-do and must-not-do lists otherwise. Keep dos and don'ts together under the topic they belong to.
-
-Use `{{DOUBLE_BRACES}}` for values the end user fills in at runtime.
-
-Constraints:
-
-- Use imperative voice. Write `Do X`, never `You should` or `Try to`.
-- Make every constraint verifiable from the output. Reject subjective qualifiers like `appropriate`, `concise`, or `well-structured`.
-- Match prompt length to task complexity. A single-purpose task gets a minimal prompt.
-- Never write `maybe`, `consider`, or `depending on`. Be definitive.

package/snippets/research-prompt.md

@@ -1,7 +0,0 @@
-Generate a self-contained research prompt for another AI chat. Include:
-
-- State what I am trying to do and why
-- List what I have already tried and the results
-- Specify questions that need answers
-
-Write it in first person. Assume the reader has no context from this session.

package/snippets/session-notes.md

@@ -1,11 +0,0 @@
-Write session notes for this conversation using this format:
-
-```markdown
-# Session notes: <topic>
-
-## <title>
-
-<what was decided and why>
-```
-
-Only include decisions made in this session. Output only the markdown block, nothing else.

package/snippets/snippets.toml

@@ -1,5 +0,0 @@
-[essentials]
-names = [
-    "align",
-    "decision-help",
-]

package/snippets/step-by-step.md

@@ -1,10 +0,0 @@
-Give me step-by-step instructions.
-
-For each step:
-
-- State what to do in one sentence.
-- Include the exact value, command, or input where precision matters.
-- Note any output to save or verify before moving on.
-- When the step has multiple sub-actions or lists several items, use nested bullets instead of stacking them in one sentence.
-
-Group related steps under a heading if the process has distinct phases. Flag any step that is irreversible or that blocks later steps.

package/snippets/web-research.md

@@ -1,21 +0,0 @@
-Search the web for the topic or question added after this snippet. Fetch the most relevant pages. Synthesize findings into a decision-ready block using this format:
-
-```markdown
-Topic: [what was researched]
-Recommendation: [one clear answer or choice]
-
-Options considered:
-
-- [Option A]: why considered, why chosen or rejected
-- [Option B]: why considered, why chosen or rejected
-
-Key constraints:
-
-- [constraint that shaped the decision]
-
-Sources:
-
-- [URL]: what it confirmed
-```
-
-Output only the block. Do not add commentary before or after it.

package/src/commands/snippets.ts

@@ -1,90 +0,0 @@
-import type { Command } from 'commander'
-import { registerPassThroughVerbs } from '@/commands/pass-through'
-import { checkoutMismatchWarning, PROJECT_ROOT } from '@/project-root'
-import { BASE_CATEGORY } from '@/snippets/categories'
-import { buildSnippetsCatalog } from '@/snippets/list'
-import { intro, logInfo, logStep, logWarn, outro } from '@/ui'
-
-const PASS_THROUGH_VERBS = ['create'] as const
-
-interface ListOptions {
-  readonly categories?: boolean
-  readonly entries?: boolean
-  readonly json?: boolean
-}
-
-export function register(program: Command): void {
-  const snippets = program
-    .command('snippets')
-    .description('Snippets commands (create, list)')
-    .helpOption('-h, --help', 'Show this help message')
-
-  snippets
-    .command('list')
-    .description('List snippet presets, categories, and entries')
-    .helpOption('-h, --help', 'Show this help message')
-    .option('--categories', 'Only list presets and category names')
-    .option('--entries', 'Only list entry slugs grouped by category')
-    .option('--json', 'Emit machine-readable JSON')
-    .action((opts: ListOptions) => {
-      process.exitCode = runList(opts)
-    })
-
-  registerPassThroughVerbs(snippets, 'snippets', PASS_THROUGH_VERBS)
-}
-
-/**
- * `JSON.stringify` replaces a `printf` template that interpolated names into a
- * JSON string literal unescaped, so a slug or category carrying a quote emitted
- * output no consuming skill could parse.
- *
- * The frame opens after the `--json` return, since the bash verb only ever
- * emitted section headers and the pass-through above it owned the `┌`.
- */
-function runList(opts: ListOptions): number {
-  // The warning is a frame-interior line, so it goes out after `intro` on the
-  // path that opens one and bare on the `--json` path, which returns first and
-  // opens none. One position cannot serve both.
-  const mismatch = checkoutMismatchWarning(process.cwd())
-  const catalog = buildSnippetsCatalog(PROJECT_ROOT)
-
-  if (opts.json) {
-    if (mismatch !== undefined) logWarn(mismatch)
-    process.stdout.write(`${JSON.stringify(catalog)}\n`)
-    return 0
-  }
-
-  intro('canon snippets list')
-  if (mismatch !== undefined) logWarn(mismatch)
-
-  const showCategories = opts.entries !== true
-  const showEntries = opts.categories !== true
-
-  if (showCategories) {
-    if (catalog.presets.length > 0) {
-      logStep('Presets')
-      for (const preset of catalog.presets) {
-        logInfo(`${preset.name} (${preset.slugs.length} entries)`)
-      }
-    }
-
-    logStep('Categories')
-    for (const category of catalog.categories) {
-      logInfo(`${category.name} (${category.entries.length} entries)`)
-    }
-  }
-
-  if (showEntries) {
-    logStep('Entries')
-    for (const category of catalog.categories) {
-      for (const entry of category.entries) {
-        logInfo(
-          category.name === BASE_CATEGORY ? entry : `${category.name}/${entry}`,
-        )
-      }
-    }
-  }
-
-  outro()
-  return 0
-}

package/src/snippets/categories.ts

@@ -1,66 +0,0 @@
-import { readdirSync } from 'node:fs'
-import { join } from 'node:path'
-import { isDirectory } from '@/target'
-
-export const BASE_CATEGORY = 'base'
-/** A real category resolving to zero entries, for a caller declining on purpose. */
-export const NONE_CATEGORY = 'none'
-
-export function snippetsSourceDir(root: string): string {
-  return join(root, 'snippets')
-}
-
-/**
- * Lists the folder categories. `base` is the synthetic name for snippets
- * sitting directly under `snippets/`, so it is not a directory and callers
- * prepend it themselves.
- *
- * Nothing is filtered: toolkit-internal snippets are authored under `internal/`,
- * which this never reads, so every category found here is publishable.
- */
-export function listFolderCategories(root: string): string[] {
-  const dir = snippetsSourceDir(root)
-  if (!isDirectory(dir)) return []
-
-  return readdirSync(dir, { withFileTypes: true })
-    .filter((entry) => entry.isDirectory())
-    .map((entry) => entry.name)
-    .sort()
-}
-
-export function listCategories(root: string): string[] {
-  return [BASE_CATEGORY, ...listFolderCategories(root)]
-}
-
-export function categoryDir(root: string, category: string): string {
-  const source = snippetsSourceDir(root)
-  return category === BASE_CATEGORY ? source : join(source, category)
-}
-
-/**
- * Tests for a directory rather than mere existence. `snippets/` holds files
- * alongside its category folders, so an argument naming one of them resolves
- * to a real path that cannot be scanned as a category.
- *
- * An empty category refuses rather than resolving, since `join(source, '')`
- * is `source` and would otherwise report the base directory as the category,
- * widening an unset value to every base entry instead of naming none.
- */
-export function categoryExists(root: string, category: string): boolean {
-  if (category === '') return false
-  return isDirectory(categoryDir(root, category))
-}
-
-/**
- * Lists one category's entry slugs. Only the immediate level is read, matching
- * the `find -maxdepth 1` the bash used, so a nested folder is its own category
- * rather than part of its parent.
- */
-export function listEntries(root: string, category: string): string[] {
-  const dir = categoryDir(root, category)
-  if (!isDirectory(dir)) return []
-
-  return [...new Bun.Glob('*.md').scanSync({ cwd: dir, onlyFiles: true })]
-    .map((name) => name.slice(0, -'.md'.length))
-    .sort()
-}

package/src/snippets/list.ts

@@ -1,32 +0,0 @@
-import { listCategories, listEntries } from '@/snippets/categories'
-import { loadPresets } from '@/snippets/presets'
-
-export interface CategoryCatalogEntry {
-  readonly name: string
-  readonly entries: readonly string[]
-}
-
-export interface SnippetsCatalog {
-  readonly presets: readonly {
-    readonly name: string
-    readonly slugs: readonly string[]
-  }[]
-  readonly categories: readonly CategoryCatalogEntry[]
-}
-
-/**
- * Builds the catalog both output modes read, so the human list and the `--json`
- * one cannot describe different corpora.
- */
-export function buildSnippetsCatalog(root: string): SnippetsCatalog {
-  return {
-    presets: loadPresets(root).map((preset) => ({
-      name: preset.name,
-      slugs: preset.slugs,
-    })),
-    categories: listCategories(root).map((name) => ({
-      name,
-      entries: listEntries(root, name),
-    })),
-  }
-}