@erclx/aitk - npm Package Compare versions

Comparing version

+19

governance/rules/claude/592-claude-md.md

		---
		description: Enforce the CLAUDE.md edit protocol and the test routing a fact into it rather than a rule
		paths:
		- 'CLAUDE.md'
		---

		# CLAUDE.md standards

		## Editing

		- Show the proposed change as a fenced `diff` block in chat first, then wait for approval before calling the file-editing tool.

		## Routing

		- Keep a rule here when it applies every session regardless of what is being edited.
		- Move a rule into `.claude/rules/` when it fires only on a specific path being edited and violating it ships silently.
		- Route a rule failing either half to a context entry or a skill body rather than here.
		- Name a rule's tier rather than a rule file. A path-scoped rule reaches the session on its own glob and needs no pointer from here.
		- Point at a skill by name where one applies. A skill loads only when invoked, so an unreferenced skill is one no session finds.

+1

-1

claude/.claude-plugin/plugin.json

		{
		"name": "aitk",
		"description": "Automated governance, versioning, and discovery tools for Claude Code.",
		"version": "3.2.0",
		"version": "3.3.0",
		"author": {
		@@ -6,0 +6,0 @@ "name": "Eric Le",

+1

-1

package.json

		{
		"name": "@erclx/aitk",
		"type": "module",
		"version": "3.2.0",
		"version": "3.3.0",
		"description": "Infrastructure and quality tooling for developer workflows",
		@@ -6,0 +6,0 @@ "license": "MIT",

+10

-0

standards/architecture.md

		@@ -46,2 +46,12 @@ ---

		## Length

		Every session pays for this file before any work starts, so it carries a budget. The budget counts decisions rather than lines, because a bare line total is satisfied by merging paragraph pairs and the merged paragraphs then fail the weight checkpoint in `markdown.md`. A file over budget is carrying too many decisions, not decisions written too long.

		- Budget six lines per decision entry, being the H3, two paragraphs, and the blank lines separating them.
		- Budget the frame outside `## Key technical decisions` separately, covering the H1, the overview, and the risks. State the number the project takes where it records the budget, since a frame carries no fixed structure to derive one from.
		- Read the ceiling as the frame plus six lines against the decision count, rather than as the total the two multiply out to.
		- Bring an over-budget file back by merging two decisions or retiring one, never by compressing a decision's prose.
		- Yield the budget to the paragraph weight checkpoint when the two disagree. A paragraph past the checkpoint is a defect no budget licenses.

		## Template
		@@ -48,0 +58,0 @@

+1

-0

tooling/claude/seeds/CLAUDE.md

		@@ -25,2 +25,3 @@ # Project
		- When planning an edit to `CLAUDE.md`, show the proposed change as a fenced `diff` block in chat first, then wait for approval before calling `Edit`
		- Keep a rule in `CLAUDE.md` when it applies every session regardless of what is being edited. Move one that fires only on a specific path being edited and ships silently when violated into `.claude/rules/`.
		- Edit an existing file with the file-editing tool, never a shell stream editor. An unescaped `&` in a `sed` replacement expands to the whole match, and `sed -i` exits zero when its pattern matches nothing, so both fail silently while reporting success. This governs edits you make, not stream editors written into a project's own scripts.
		@@ -27,0 +28,0 @@

New alerts