@theglitchking/hit-em-with-the-docs 2.7.1 → 2.8.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.
@@ -1,208 +0,0 @@
1
- # Documentation System Plugin (hit-em-with-the-docs)
2
-
3
- This project uses the hit-em-with-the-docs documentation system for hierarchical, self-managing documentation.
4
-
5
- ## Quick Reference
6
-
7
- ### Documentation Structure
8
-
9
- ```
10
- .documentation/
11
- ├── INDEX.md # Navigation hub
12
- ├── REGISTRY.md # Quick reference
13
- ├── security/ # Security, auth, Vault, Keycloak
14
- ├── devops/ # Deployment, CI/CD, Docker
15
- ├── database/ # Schema, migrations, RLS
16
- ├── api/ # API endpoints, routes
17
- ├── standards/ # Coding standards
18
- ├── testing/ # Test strategies
19
- ├── architecture/ # System design
20
- ├── features/ # Feature guides
21
- ├── quickstart/ # Setup guides
22
- ├── procedures/ # Operational procedures
23
- ├── workflows/ # Process documentation
24
- ├── agents/ # AI agent docs
25
- ├── backups/ # Backup guides
26
- ├── troubleshooting/ # Debug guides
27
- └── plans/ # Planning documents
28
- ```
29
-
30
- These 15 domains are built-in and always present. The set is **extensible** — register project-specific domains at runtime with `npx hit-em-with-the-docs domain add <id> -k <keywords>` (stored in `.claude/hit-em-with-the-docs.json` under `domains: []`, and scaffolded under `.documentation/<id>/`). Run `npx hit-em-with-the-docs domain list` to see the active set, and `domain remove <id>` to drop a custom one (never deletes docs).
31
-
32
- **Deprecated docs → `.documentation/archive/`.** To retire a doc without deleting it, use `npx hit-em-with-the-docs archive <file>` — it moves the doc under `archive/`, stamps lifecycle frontmatter (`archived_from` makes it reversible), and reindexes. A link guard refuses if active docs still link to it (`--force` overrides); `--dry-run` previews. `unarchive <file>` restores it where it came from, and `archive-candidates` lists docs that may warrant archiving (advisory, read-only — never moves anything). hewtd excludes the `archive/` folder from every scan (audit, link-check, metadata-sync, integrate, link graph, search), so archived docs are never validated or indexed. `archive` is reserved and cannot be a domain. A doc left at `status: deprecated` in an active folder is now surfaced by `audit` as an INFO nudge toward `archive`.
33
-
34
- ## Commands
35
-
36
- ### /docs
37
-
38
- Documentation commands for managing the hierarchical documentation system.
39
-
40
- #### /docs load <domain>
41
-
42
- Load documentation for a specific domain.
43
-
44
- Usage: `/docs load security`
45
-
46
- This loads:
47
- 1. Domain INDEX.md (complete listing)
48
- 2. Domain REGISTRY.md (quick reference)
49
- 3. Key documents summary
50
-
51
- #### /docs list
52
-
53
- List all documentation domains (the 15 built-in plus any custom domains) with descriptions.
54
-
55
- #### /docs search <query>
56
-
57
- Search across all documentation for a query term.
58
-
59
- Usage: `/docs search "authentication"`
60
-
61
- #### /docs stats
62
-
63
- Show documentation health statistics including:
64
- - Total documents per domain
65
- - Link health
66
- - Metadata compliance
67
- - Recent updates
68
-
69
- #### /docs maintain
70
-
71
- Run documentation maintenance:
72
- ```bash
73
- npx hit-em-with-the-docs maintain --quick
74
- ```
75
-
76
- #### /docs integrate <file>
77
-
78
- Integrate a document into the system:
79
- ```bash
80
- npx hit-em-with-the-docs integrate ./docs/new-guide.md
81
- ```
82
-
83
- ### /discover
84
-
85
- Pattern discovery commands for extracting patterns from the codebase.
86
-
87
- #### /discover patterns
88
-
89
- Discover coding patterns in the codebase:
90
- ```bash
91
- npx hit-em-with-the-docs discover patterns
92
- ```
93
-
94
- Detects: Service layer, Repository pattern, Factory pattern, Error handling, etc.
95
-
96
- #### /discover anti-patterns
97
-
98
- Detect anti-patterns and code smells:
99
- ```bash
100
- npx hit-em-with-the-docs discover anti-patterns
101
- ```
102
-
103
- Detects: Hardcoded credentials, SQL injection risks, console.log, any types, etc.
104
-
105
- #### /discover standards
106
-
107
- Extract implicit coding standards:
108
- ```bash
109
- npx hit-em-with-the-docs discover standards
110
- ```
111
-
112
- Extracts: Naming conventions, file organization, code style, documentation coverage.
113
-
114
- #### /discover dependencies
115
-
116
- Analyze project dependencies:
117
- ```bash
118
- npx hit-em-with-the-docs discover dependencies
119
- ```
120
-
121
- Analyzes: Package versions, circular dependencies, unused dependencies, security issues.
122
-
123
- ## Metadata Schema
124
-
125
- Every documentation file should have this YAML frontmatter:
126
-
127
- ```yaml
128
- ---
129
- # Required fields
130
- title: "Document Title"
131
- tier: guide|standard|example|reference|admin
132
- domains: [primary-domain]
133
- status: draft|active|deprecated|archived
134
- last_updated: 'YYYY-MM-DD'
135
- version: '1.0.0'
136
-
137
- # Optional fields
138
- audience: [all|developers|devops|admin]
139
- tags: [tag1, tag2]
140
- purpose: "One-sentence purpose"
141
- related_docs:
142
- - path/to/related.md
143
- author: "Name"
144
- ---
145
- ```
146
-
147
- ## Tiers
148
-
149
- | Tier | Description | Size |
150
- |------|-------------|------|
151
- | guide | Step-by-step how-to guides | 15-30 KB |
152
- | standard | Coding standards and conventions | 5-15 KB |
153
- | example | Code examples and templates | 3-10 KB |
154
- | reference | Comprehensive references | 30+ KB |
155
- | admin | Administrative/operational docs | 10-20 KB |
156
-
157
- ## Workflow Guidelines
158
-
159
- ### Adding New Documentation
160
-
161
- 1. Determine the appropriate domain
162
- 2. Create file with kebab-case naming: `topic-name-type.md`
163
- 3. Add required frontmatter
164
- 4. Write content following tier template
165
- 5. Run: `npx hit-em-with-the-docs integrate <file>`
166
-
167
- ### Weekly Maintenance
168
-
169
- Run every Friday:
170
- ```bash
171
- npx hit-em-with-the-docs maintain
172
- ```
173
-
174
- This syncs metadata, checks links, and audits compliance.
175
-
176
- ### Before Committing Documentation
177
-
178
- ```bash
179
- # Quick check
180
- npx hit-em-with-the-docs audit
181
-
182
- # Fix issues
183
- npx hit-em-with-the-docs metadata-sync --fix
184
- ```
185
-
186
- ## File Naming Convention
187
-
188
- - Use kebab-case: `api-design-standards.md`
189
- - Include type suffix when appropriate: `-guide.md`, `-standard.md`, `-procedure.md`
190
- - Be specific: `keycloak-integration-guide.md` not `auth.md`
191
-
192
- ## Related Commands
193
-
194
- ```bash
195
- # Initialize documentation structure
196
- npx hit-em-with-the-docs init
197
-
198
- # Generate reports
199
- npx hit-em-with-the-docs report health
200
- npx hit-em-with-the-docs report audit
201
- npx hit-em-with-the-docs report links
202
-
203
- # Check links
204
- npx hit-em-with-the-docs link-check
205
-
206
- # Discover patterns
207
- npx hit-em-with-the-docs discover patterns --language typescript
208
- ```