@erclx/aitk 3.10.0 → 3.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (52) hide show
  1. package/claude/.claude-plugin/plugin.json +1 -1
  2. package/claude/skills/claude-markdown-propose/REQUIREMENT.md +48 -0
  3. package/claude/skills/claude-markdown-propose/SKILL.md +118 -0
  4. package/claude/skills/claude-markdown-propose/references/format.md +107 -0
  5. package/claude/skills/claude-pr-review/SKILL.md +1 -1
  6. package/claude/skills/claude-teach/SKILL.md +1 -1
  7. package/claude/skills/claude-worktree/SKILL.md +1 -1
  8. package/claude/skills/create-snippet/SKILL.md +1 -1
  9. package/claude/skills/git-branch/SKILL.md +1 -1
  10. package/claude/skills/git-commit/SKILL.md +1 -1
  11. package/claude/skills/git-issue/SKILL.md +2 -2
  12. package/claude/skills/git-pr/SKILL.md +5 -5
  13. package/claude/skills/git-split/SKILL.md +2 -2
  14. package/claude/skills/git-stage/SKILL.md +1 -1
  15. package/docs/agents/audits.md +2 -2
  16. package/docs/agents/records.md +1 -1
  17. package/docs/agents/teach.md +1 -1
  18. package/docs/ai-workflow.md +7 -6
  19. package/package.json +1 -1
  20. package/scripts/core/check-skill-paths.sh +1 -2
  21. package/scripts/core/verify.sh +0 -5
  22. package/src/audits/catalog.ts +20 -0
  23. package/src/claude/skills-audit.ts +7 -0
  24. package/src/commands/claude.ts +20 -6
  25. package/src/commands/comments.ts +6 -0
  26. package/src/commands/context.ts +32 -7
  27. package/src/commands/gov.ts +2 -2
  28. package/src/commands/markdown.ts +18 -2
  29. package/src/context/audit.ts +16 -0
  30. package/src/gov/test-order.ts +31 -7
  31. package/src/markdown/files.ts +10 -0
  32. package/src/records/backup.ts +1 -0
  33. package/src/records/validate.ts +1 -3
  34. package/{claude/skills/git-split/references → standards}/branch.md +0 -1
  35. package/{claude/skills/git-commit/references → standards}/commit.md +0 -1
  36. package/{claude/skills/claude-teach/references → standards}/glossary.md +0 -1
  37. package/standards/index.md +6 -0
  38. package/standards/{bundled/issue.md → issue.md} +0 -1
  39. package/standards/{bundled/pr.md → pr.md} +0 -1
  40. package/standards/{bundled/snippets.md → snippets.md} +0 -1
  41. package/claude/skills/claude-worktree/references/branch.md +0 -60
  42. package/claude/skills/create-snippet/references/snippets.md +0 -78
  43. package/claude/skills/git-branch/references/branch.md +0 -60
  44. package/claude/skills/git-issue/references/issue.md +0 -95
  45. package/claude/skills/git-pr/references/branch.md +0 -60
  46. package/claude/skills/git-pr/references/pr.md +0 -139
  47. package/claude/skills/git-split/references/pr.md +0 -139
  48. package/claude/skills/git-stage/references/commit.md +0 -73
  49. package/scripts/core/regen-skill-references.sh +0 -27
  50. package/standards/bundled/branch.md +0 -60
  51. package/standards/bundled/commit.md +0 -73
  52. package/standards/bundled/glossary.md +0 -76
@@ -1,76 +0,0 @@
1
- ---
2
- title: Glossary reference
3
- description: Frontmatter, entry shape, ordering, and the rules deciding which terms a glossary carries
4
- consumers: claude-teach
5
- ---
6
-
7
- # Glossary reference
8
-
9
- Applies to a glossary, the file holding one entry per term a body of material defines. It changes whenever the material names a concept a reader cannot look up yet, and it is revised in place rather than appended to.
10
-
11
- ## Scope
12
-
13
- Governs a glossary at `.claude/teach/<nn>-<topic>/GLOSSARY.md` and at whatever path a surface fixes for one it holds: its frontmatter, entry shape, ordering, grouping, and the rules deciding which terms it carries.
14
-
15
- Does not govern:
16
-
17
- - The folder a learning workspace lays out around its glossary, and the other files in it: `teach.md`
18
- - Which surface a glossary moves to once it leaves the material that produced it, which belongs to the surface driving that move
19
- - Voice, rhythm, and sentence construction: the `write-human` skill
20
- - Headings, punctuation, word choice, and file references: `markdown.md`
21
-
22
- ## What a working glossary looks like
23
-
24
- A glossary works when a reader who meets a term in the material settles it here without opening the page that introduced it:
25
-
26
- - Which word does this material use for the concept, and which words does it deliberately not use?
27
- - What does the term mean, stated without leaning on the term itself?
28
- - Where does the term appear, so a reader can see it used rather than only defined?
29
- - Does every entry carry a term the material actually uses?
30
-
31
- A glossary failing these is non-conforming even when it satisfies every shape rule below.
32
-
33
- ## Frontmatter
34
-
35
- - `title` (required): names the material the terms come from, in sentence case
36
- - `description` (required): one line naming what a reader gets from the entries
37
-
38
- ## Entries
39
-
40
- - Write one entry per term, as a single bullet.
41
- - Lead the bullet with the term as a bolded span, then the definition in one or two sentences.
42
- - Define the term without using it. A definition that spends the term explains nothing to the reader who arrived not knowing it.
43
- - Name where the term first appears, so a reader can reach one use of it in context.
44
- - Keep an entry to the meaning. Worked detail belongs on the page that teaches the term.
45
- - Sort entries alphabetically, so a reader who knows only the word finds it without reading the file.
46
-
47
- ## Which terms it carries
48
-
49
- - Add a term once the material has used it, never ahead of that. A glossary front-loaded with terms nothing has introduced is a syllabus rather than a reference.
50
- - Pick one word per concept and use that word everywhere. A glossary carrying two words for one thing hands the reader a choice it exists to remove.
51
- - List each rejected synonym as an alias to avoid inside the entry that won, so a reader arriving with the wrong word lands on the right one.
52
- - Use the glossary's own terms inside other definitions. A definition reaching for a synonym of a term defined two entries down teaches the reader a word the material does not use.
53
- - Revise an entry the material has moved under rather than adding a second one narrating the change.
54
-
55
- ## Grouping
56
-
57
- - Keep a short glossary as one alphabetical list under the title. Grouping a handful of entries costs a heading per category and saves no lookup.
58
- - Group a glossary long enough that one list stops helping under `##` headings by category, sorted alphabetically within each. Roughly two screens of entries is the signal.
59
- - Name each category so a reader picks it from the term alone. A category a reader cannot predict makes the grouping a second thing to search.
60
- - State a departure from any rule above in the file itself, naming what it departs from and why. A glossary serving no single body of material is the case that produces one, since a term drawn from everywhere has no first appearance to name.
61
-
62
- ## Template
63
-
64
- ```markdown
65
- ---
66
- title: <Material the terms come from>
67
- description: <one line naming what a reader gets from these entries>
68
- ---
69
-
70
- # <Material the terms come from>
71
-
72
- <One line on which material these terms come from and when the file changes.>
73
-
74
- - **<Term>**: <the meaning in one or two sentences, written without using the term>. Avoid <rejected synonym>. First appears in `<page or lesson>`.
75
- - **<Term>**: <the meaning in one or two sentences, written without using the term>. First appears in `<page or lesson>`.
76
- ```