@erclx/aitk 3.25.2 → 3.26.1

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

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

package/governance/rules/claude/510-context.md

@@ -10,7 +10,6 @@ paths:
 
 - Before non-trivial work in a domain, read its `.claude/context/<domain>.md` entry. Use `.claude/context/index.md` to find it.
 - Leave the entry conforming when work in its domain changes what it describes.
-- Rewrite the decision a change supersedes rather than appending a second one narrating the transition.
 
 ## Narration pronouns
 

package/governance/rules/claude/520-wireframes.md

@@ -6,14 +6,6 @@ paths:
 
 # Wireframe standards
 
-## Layout and intent
-
-- Draw each surface as an ASCII block inside a `plaintext` fence, one fence per distinct layout.
-- Label a region with its role. Never label one with a class name, a token name, or a computed value.
-- Carry on-screen copy verbatim, and mark copy the surface templates.
-- State interaction intent, never the mechanism behind it. Send algorithms, handlers, and thresholds to a `.claude/context/` entry.
-- Update a surface's wireframe in the same pull request that changes its layout or its interaction.
-
 ## Authority
 
 - Follow the wireframes standard for layout and interaction intent: ASCII layout, region labels, variants, copy, and what moves to `.claude/context/`. It is the single source. Read it with `aitk standards wireframes`.

package/governance/rules/claude/530-requirements.md

@@ -6,14 +6,6 @@ paths:
 
 # Requirements standards
 
-## Scope and non-goals
-
-- State a goal as a user-facing outcome, never as the implementation delivering it.
-- Record explicit non-goals. Mark a deferred item `(deferred)`.
-- Leave the MVP list as written once its features ship. Do not renumber it, extend it, or annotate an entry with status.
-- Add later scope as a new section rather than as an extension of the MVP list.
-- Drop a section rather than pad it. Include `## Distribution` only when the project ships outside its own repository.
-
 ## Authority
 
 - Follow the requirements standard for what belongs in the problem, goals, non-goals, MVP features, tech stack, and constraints. It is the single source. Read it with `aitk standards requirements`.

package/governance/rules/claude/540-architecture.md

@@ -6,16 +6,6 @@ paths:
 
 # Architecture standards
 
-## Decisions
-
-- Give each decision its own H3 under `## Key technical decisions`, naming what it chose and the alternative it passed over.
-- Keep line-by-line function behavior and full type definitions out.
-
-## Verification anchors
-
-- Close a decision citing a measured number with `Measured at <short-sha> on <YYYY-MM-DD>.` Leave a decision citing none unanchored.
-- Refresh that anchor whenever the number is re-read, whether or not it moved.
-
 ## Authority
 
 - Follow the architecture standard for the overview, named decision entries, and risks. It is the single source. Read it with `aitk standards architecture`.

package/governance/rules/claude/550-design.md

@@ -6,14 +6,6 @@ paths:
 
 # Design standards
 
-## Tokens
-
-- Describe a token as intent rather than as a computed value.
-- Keep CSS classes, component filenames, and prop names out.
-- Carry a token system as a table, one row per token, and a component rule as a short bullet.
-- Keep the token table headers verbatim.
-- Record a non-obvious omission, such as no motion or no custom icons.
-
 ## Authority
 
 - Follow the design standard for visual intent, the token tables, and the render contract. It is the single source. Read it with `aitk standards design`.

package/governance/rules/claude/555-tasks.md

@@ -6,14 +6,6 @@ paths:
 
 # Tasks standards
 
-## What a task carries
-
-- Name where the task came from, through a `Plan:`, `Groundwork:`, `Intake:`, or `Issue:` line under the title.
-- Size the outcomes so one pull request closes all of them. Split the task before handing it off.
-- Use `## Outcomes` and `## Findings` and add no third heading. Note status inline on an outcome.
-- Keep class names, file paths, function names, and prop names out of every entry and title.
-- Never delete a task file. A shipped task moves to the archive under its own name.
-
 ## Authority
 
 - Follow the tasks standard for filenames, frontmatter, what belongs, and the task file format. It is the single source. Read it with `aitk standards tasks`.

package/governance/rules/claude/556-groundwork.md

@@ -6,15 +6,6 @@ paths:
 
 # Groundwork standards
 
-## Folder name
-
-- Name a new track `.claude/groundwork/<nn>-<slug>/`, a two-digit zero-padded ordinal followed by a kebab-case slug. Take the ordinal from the highest one already present across both `.claude/groundwork/` and `.claude/intake/`, incremented, or `01` when neither folder holds an entry. Never renumber an existing folder.
-
-## Measuring and closing
-
-- Never carry a figure from an earlier session without re-measuring it. Mark an inference as an inference.
-- Never close a track while an open question quietly fails an outcome. Resolve it, or record it as knowingly accepted.
-
 ## Authority
 
 - Follow the groundwork standard for reserved numbering, frontmatter and dating, what each required file holds, and the conventions a track keeps. It is the single source. Read it with `aitk standards groundwork`.

package/governance/rules/claude/557-intake.md

@@ -6,15 +6,6 @@ paths:
 
 # Intake standards
 
-## Folder name
-
-- Name a new dump `.claude/intake/<nn>-<slug>/`, a two-digit zero-padded ordinal followed by a kebab-case slug. Take the ordinal from the highest one already present across both `.claude/intake/` and `.claude/groundwork/`, incremented, or `01` when neither folder holds an entry. Never renumber an existing folder.
-
-## The answer contract
-
-- Never fill a `You:` slot and never infer a disposition from an empty one. Empty means unread, never agreement.
-- Report unread items by count on a resume pass. Do not decide one.
-
 ## Authority
 
 - Follow the intake standard for the folder layout, frontmatter and dating, the item format, and retrieval. It is the single source. Read it with `aitk standards intake`.

package/governance/rules/claude/559-memory.md

@@ -6,15 +6,6 @@ paths:
 
 # Memory standards
 
-## Routing
-
-- Write no memory entry for a fact a per-domain context entry already owns.
-
-## The pen
-
-- Never delete a memory entry. Retire one by moving it to an archive under its own name, since the folder is gitignored and a wrong call has no undo.
-- Never hand-edit `.claude/memory/index.md`. A hook regenerates it from sibling frontmatter.
-
 ## Authority
 
 - Follow the memory standard for the filename and type prefix, the frontmatter, the body shape per type, links between entries, and the lifecycle. It is the single source. Read it with `aitk standards memory`.

package/governance/rules/claude/560-diagrams.md

@@ -16,4 +16,3 @@ paths:
 
 - Write a new diagram to `.claude/diagrams/<kind>.md`, never to `.claude/DIAGRAMS.md`
 - Convert a `.claude/DIAGRAMS.md` left by an older install into per-kind entries before editing it
-- Refresh only the entries whose source signal moved. Do not rewrite the folder wholesale.

package/governance/rules/claude/561-teach.md

@@ -6,16 +6,8 @@ paths:
 
 # Teach standards
 
-## What a workspace keeps
-
-- Never renumber an existing folder, lesson, or record. A later reader cites it by the name it opened under.
-- Write every success line as a task the learner can be asked to perform, never as something they will understand.
-- Keep a reference page free of the learner. A page carrying second person or a quiz belongs under `lessons/`.
-- Record the wrong answer a learner gave, never a count of what they missed.
-- Date the workspace once, in the `MISSION.md` frontmatter. Never repeat the date in the body of any file.
-
 ## Authority
 
 - Follow the teach standard for the folder layout, ordinal naming, frontmatter, and the mission and learning-record formats. It is the single source. Read it with `aitk standards teach`.
-- Read `references/glossary.md` inside the `claude-teach` skill for the glossary every workspace carries at its root. It is the single source for the entry shape, the ordering, and which terms the file carries. Read it rather than invoking the skill, which resumes a workspace and runs lessons.
+- Read `references/glossary.md` inside the `aitk:claude-teach` skill for the glossary every workspace carries at its root. It is the single source for the entry shape, the ordering, and which terms the file carries. Read it rather than invoking the skill, which resumes a workspace and runs lessons.
 - Report it rather than proceeding silently when that file does not resolve. It ships with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have it.

package/governance/rules/claude/562-session.md

@@ -9,10 +9,6 @@ paths:
 ## What a handoff carries
 
 - Follow this rule rather than `555-tasks.md` for a `session-` file. A handoff is not a task and carries neither `## Outcomes` nor `## Findings`.
-- Never write into a file another session owns. Overwrite only the file the writing session already wrote.
-- Resolve the containing folder at the main worktree root, never inside a linked worktree.
-- Write only what a compaction destroys. Do not restate the board and do not summarize what shipped.
-- Cite a commit, a task, or a file and line for every claim, so a reader can tell a read from a recall.
 
 ## Authority
 

package/governance/rules/claude/570-skill.md

@@ -11,9 +11,8 @@ paths:
 
 ## Before editing
 
-- Read the skill's sibling `REQUIREMENT.md` when one exists. If the change closes no gap it states, change the requirement first or drop the change.
-- Confirm `create-skill`'s two creation-time questions are answered before a new `SKILL.md` lands, whether drafted by hand, by another skill, or by `create-skill` itself. Carry the third question into the sibling `REQUIREMENT.md`'s `Must not` section as a review criterion rather than a gate.
-- Report it rather than proceeding silently when `create-skill` does not resolve. It ships with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have it.
+- Confirm `aitk:create-skill`'s two creation-time questions are answered before a new `SKILL.md` lands, whether drafted by hand, by another skill, or by `aitk:create-skill` itself. Carry the third question into the sibling `REQUIREMENT.md`'s `Must not` section as a review criterion rather than a gate.
+- Report it rather than proceeding silently when `aitk:create-skill` does not resolve. It ships with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have it.
 
 ## After editing
 

package/governance/rules/claude/580-readme.md

@@ -6,14 +6,6 @@ paths:
 
 # README standards
 
-## Audience and voice
-
-- Write a repository-root README for someone deciding whether to commit to the project. A nested README keeps the reference voice.
-- Address the reader in second person.
-- Ground a claim in a command, a number, or a named constraint rather than an adjective.
-- Name what the project does not do.
-- Link out to full API documentation, license text, contribution guidelines, and troubleshooting rather than carrying them.
-
 ## Authority
 
 - Follow the readme standard for voice, structure, required and optional sections, heading hierarchy, badge classes, per-project-type content, and what to link out rather than inline. It is the single source. Read it with `aitk standards readme`.

package/governance/rules/claude/590-rule-authoring.md

@@ -6,19 +6,6 @@ paths:
 
 # Rule authoring standards
 
-## Numbering
-
-- Name a rule `.claude/rules/<subdirectory>/<n>-<slug>.md`. Give every rule a numeric prefix and keep the slug to one to three kebab words.
-- Treat `000-899` as reserved for a rule set that ships to targets, `000-599` across the shared subdirectories and `600-899` held for ones it has not added.
-- Number a rule the project authored itself in `900-999` and write it at `.claude/rules/project/<subdirectory>/<n>-<slug>.md`.
-- Do not take a reserved number for a project-authored rule because nothing installed holds it today. A later release can ship into it.
-
-## Body
-
-- State one directive per bullet in imperative voice. Do not explain the reasoning behind a rule.
-- Cut a rule that resists crisp one-line phrasing.
-- Do not restate a rule a sibling rule or `CLAUDE.md` already owns. Point once.
-
 ## Authority
 
 - Follow the rule-authoring standard for rule frontmatter, body shape, and voice. It is the single source. Read it with `aitk standards rule`.

package/governance/rules/claude/591-standard-authoring.md

@@ -7,14 +7,6 @@ paths:
 
 # Standard authoring standards
 
-## The scope statement
-
-- Govern one document type per standard, or one attribute across every document.
-- Open with a `## Scope` section naming what the standard governs and a `Does not govern:` list, placed above the shape rules.
-- Put the governed path in backticks in the first sentence, anchored deep enough to resolve from a project root. Keep an attribute standard's first sentence free of backticks and say in it that it governs an attribute.
-- Give each `Does not govern:` entry an excluded concern and the owner it goes to. Cut an entry naming no owner.
-- Declare a yield, an exemption, or a handoff from both sides of the boundary.
-
 ## Authority
 
 - Follow the standard-authoring standard for a standard's frontmatter, shape, scope, and success criterion. It is the single source. Read it with `aitk standards standard`.

package/governance/rules/core/045-memory.md

@@ -7,6 +7,6 @@ description: Keep memory writes scoped to .claude/memory/ and out of context-own
 ## Writing memory
 
 - Write all memory files to `.claude/memory/`, not `~/.claude/projects/`
-- A fact about a domain goes to that domain's `.claude/context/` entry, not to memory. `claude-memory-capture` routes it there and `claude-docs` folds it in. Memory keeps only what no context entry owns.
+- A fact about a domain goes to that domain's `.claude/context/` entry, not to memory. `aitk:claude-memory-capture` routes it there and `aitk:claude-docs` folds it in. Memory keeps only what no context entry owns. Report it rather than proceeding silently when either skill does not resolve. Both ship with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have them.
 - Never delete a memory entry. Retire one by moving it to `.claude/.tmp/memory-archive/`. A bulk retire runs through the shell, where no file edit fires a path-scoped rule, and the folder is gitignored with nothing to recover from.
-- Follow the memory standard, which your toolkit resolves by name, for the filename and type prefix, the frontmatter, the body shape each type carries, and the lifecycle. Check every entry in the pen against that standard and fix what breaks it, since nothing keeps the folder conforming on its own.
+- Follow the memory standard for the filename and type prefix, the frontmatter, the body shape each type carries, and the lifecycle. Read it with `aitk standards memory`. Check every entry in the pen against that standard and fix what breaks it, since nothing keeps the folder conforming on its own.

package/governance/rules/lang/120-bash.md

@@ -8,9 +8,10 @@ paths:
 
 ## Skill routing
 
-- Use `bash-script` for an interactive or human-facing script: prompts, a visual timeline UI, framed terminal output.
-- Use `cli-script` for a non-interactive script: automation, CI, cron, a pipeline helper, or anything run by an agent rather than watched by a person.
+- Use `aitk:bash-script` for an interactive or human-facing script: prompts, a visual timeline UI, framed terminal output.
+- Use `aitk:cli-script` for a non-interactive script: automation, CI, cron, a pipeline helper, or anything run by an agent rather than watched by a person.
 - Load the matched skill's own reference templates rather than hand-rolling interactivity or logging patterns outside them.
+- Report it rather than proceeding silently when the matched skill does not resolve. Both ship with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have them.
 
 ## Lint gate
 

package/package.json

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

package/standards/markdown.md

@@ -13,7 +13,7 @@ Governs what a check can decide about a markdown file: headings, paragraph and l
 
 The two frontmatter fields it reaches are `title` and `description`. They are named here rather than in the statement above, since a backticked token in a scope statement's first sentence is published as the standard's jurisdiction.
 
-The split with the voice guidance is what reads the rule rather than what the rule covers. Every ban below ships as data `aitk markdown audit` and the installed audit hook both read, so a violation is measured on every run. Cadence, rhythm, and information density are judgments a reader settles, and those travel in the `write-human` skill, which a markdown edit routes to.
+The split with the voice guidance is what reads the rule rather than what the rule covers. Every ban below ships as data `aitk markdown audit` and the installed audit hook both read, so a violation is measured on every run. Cadence, rhythm, and information density are judgments a reader settles, and those travel in the `aitk:write-human` skill, which a markdown edit routes to.
 
 Does not govern:
 

package/standards/teach.md

@@ -97,7 +97,7 @@ Record the wrong answer rather than the fact of an error. A wrong answer names t
 
 ## GLOSSARY.md
 
-Required in every workspace, holding one entry per term the subject defines. The glossary reference the `claude-teach` skill carries fixes what an entry looks like, how the file orders and groups them, and which terms it carries, so this standard states only that the file exists and sits at the workspace root. That reference ships with the plugin rather than installing here, because a promoted glossary keeps its shape wherever it lands and no project folder covers every destination. Say so and stop rather than working the shape from memory when the project has no plugin to read it from.
+Required in every workspace, holding one entry per term the subject defines. The glossary reference the `aitk:claude-teach` skill carries fixes what an entry looks like, how the file orders and groups them, and which terms it carries, so this standard states only that the file exists and sits at the workspace root. That reference ships with the plugin rather than installing here, because a promoted glossary keeps its shape wherever it lands and no project folder covers every destination. Say so and stop rather than working the shape from memory when the project has no plugin to read it from.
 
 Name the lesson or reference page a term first appears in as that reference requires. A workspace is the case it was written for, so a glossary here has a first appearance to name.
 

package/tooling/claude/seeds/CLAUDE.md

@@ -15,6 +15,7 @@
 
 ## Commands
 
+- These conventions came from a toolkit with its own CLI. A rule or standard naming a command is naming that CLI, present only where this project installed it.
 - Run `bun run check` before committing. Full script reference in the development entry under `.claude/context/`.
 
 ## Key paths