@erclx/aitk 0.84.0 → 0.85.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.84.0",
+  "version": "0.85.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

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

@@ -6,7 +6,15 @@ 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 `.claude/standards/wireframes.md` for layout and interaction intent: ASCII layout, region labels, variants, copy, and what moves to `.claude/context/`. It is the single source.
-- A wireframe carries layout and intent, not implementation. Read the standard before adding or revising a surface.
+- Read it before adding or revising a surface.

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

@@ -6,6 +6,14 @@ 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 `.claude/standards/requirements.md` for what belongs in the problem, goals, non-goals, MVP features, tech stack, and constraints. It is the single source.

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

@@ -6,6 +6,16 @@ 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 `.claude/standards/architecture.md` for the overview, named decision entries, and risks. It is the single source.

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

@@ -6,6 +6,14 @@ 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 `.claude/standards/design.md` for visual intent, the token tables, and the render contract. It is the single source.

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

@@ -6,6 +6,14 @@ 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 `.claude/standards/tasks.md` for filenames, frontmatter, what belongs, and the task file format. It is the single source.

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

@@ -6,6 +6,14 @@ 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 `.claude/standards/readme.md` 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.

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

@@ -6,6 +6,17 @@ paths:
 
 # Rule authoring standards
 
+## Numbering
+
+- Name a rule `.claude/rules/<subdirectory>/<n>-<slug>.md`, taking a number that collides with neither the project's rules nor any installed shared set.
+- Give every rule a numeric prefix and keep the slug to one to three kebab words.
+
+## 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 `.claude/standards/rule.md` for rule frontmatter, body shape, and voice. It is the single source.

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

@@ -7,6 +7,14 @@ 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 `.claude/standards/standard.md` for a standard's frontmatter, shape, scope, and success criterion. It is the single source.

package/package.json

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