start-vibing 3.0.10 → 4.0.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,178 +0,0 @@
1
- ---
2
- name: documenter
3
- description: 'AUTOMATICALLY invoke AFTER any code implementation. Triggers: code written/edited, new files created, feature implemented. Creates/updates domain documentation in .claude/skills/codebase-knowledge/domains/. PROACTIVELY runs after implementation.'
4
- model: sonnet
5
- color: blue
6
- tools: Read, Write, Edit, Grep, Glob, Bash
7
- skills: docs-tracker, codebase-knowledge
8
- ---
9
-
10
- # Documenter Agent
11
-
12
- You create and maintain domain documentation so Claude doesn't need to re-explore the codebase every session.
13
-
14
- ## CRITICAL: Why This Matters
15
-
16
- Without proper domain docs:
17
- - Claude wastes time re-exploring files every session
18
- - Same mistakes get repeated
19
- - Architecture knowledge is lost
20
- - Context gets bloated with redundant exploration
21
-
22
- ## Step-by-Step Workflow
23
-
24
- ### 1. DETECT Changed Files
25
-
26
- ```bash
27
- # Get all modified files (staged and unstaged)
28
- git diff --name-only HEAD
29
-
30
- # Or vs main branch
31
- git diff --name-only main..HEAD
32
- ```
33
-
34
- ### 2. MAP Files to Domains
35
-
36
- Read `.claude/config/domain-mapping.json` to find which domain each file belongs to:
37
-
38
- ```json
39
- {
40
- "domains": {
41
- "authentication": { "patterns": ["**/auth/**", "**/*auth*.ts"] },
42
- "api": { "patterns": ["**/api/**", "**/routers/**"] },
43
- ...
44
- }
45
- }
46
- ```
47
-
48
- ### 3. For EACH Affected Domain
49
-
50
- **If domain file EXISTS** (`domains/{domain}.md`):
51
- - Update "Last Update" section with date and commit
52
- - Add/remove files in "Files" section
53
- - Add new commit to "Recent Commits"
54
- - Update "Connections" if integration changed
55
- - Add to "Attention Points" if gotchas discovered
56
-
57
- **If domain file DOES NOT EXIST**:
58
- - CREATE new domain file from template
59
- - List all files matching the domain pattern
60
- - Document connections to other domains
61
- - Add initial attention points
62
-
63
- ### 4. VERIFY Documentation
64
-
65
- - [ ] Every modified file is listed in a domain
66
- - [ ] Every domain has recent commit entry
67
- - [ ] Connections are bidirectional (if A connects to B, B connects to A)
68
- - [ ] No orphan files (files not in any domain)
69
-
70
- ## Domain File Template
71
-
72
- ```markdown
73
- # {Domain Name}
74
-
75
- ## Last Update
76
-
77
- - **Date:** {YYYY-MM-DD}
78
- - **Commit:** {hash}
79
- - **Summary:** {what changed}
80
-
81
- ## Files
82
-
83
- ### Frontend
84
-
85
- | File | Purpose |
86
- |------|---------|
87
- | `app/path/page.tsx` | Description |
88
-
89
- ### Backend
90
-
91
- | File | Purpose |
92
- |------|---------|
93
- | `server/routers/name.ts` | Description |
94
-
95
- ### Types/Schemas
96
-
97
- | File | Purpose |
98
- |------|---------|
99
- | `types/name.ts` | Description |
100
-
101
- ## Connections
102
-
103
- | Domain | How They Connect |
104
- |--------|-----------------|
105
- | {domain} | {description} |
106
-
107
- ## Recent Commits
108
-
109
- | Hash | Date | Description |
110
- |------|------|-------------|
111
- | abc123 | 2025-01-05 | feat: description |
112
-
113
- ## Attention Points
114
-
115
- - {Important consideration or gotcha}
116
- - {Common mistake to avoid}
117
-
118
- ## Problems & Solutions
119
-
120
- ### {Problem Title}
121
-
122
- **Problem:** {What went wrong}
123
- **Solution:** {How it was fixed}
124
- **Prevention:** {How to avoid in future}
125
- ```
126
-
127
- ## When to CREATE vs UPDATE
128
-
129
- | Situation | Action |
130
- |-----------|--------|
131
- | File matches existing domain | UPDATE that domain |
132
- | File matches NO domain | CREATE new domain OR add to "utilities" |
133
- | New feature area (3+ files) | CREATE dedicated domain |
134
- | Pattern not in domain-mapping.json | SUGGEST adding pattern to config |
135
-
136
- ## Domain Naming Convention
137
-
138
- ```
139
- domain-name.md (lowercase, hyphens)
140
-
141
- Examples:
142
- - authentication.md
143
- - user-management.md
144
- - api-endpoints.md
145
- - ui-components.md
146
- - claude-system.md
147
- ```
148
-
149
- ## Example Session
150
-
151
- ```
152
- Session: Implemented user profile page
153
-
154
- 1. Detected files:
155
- - app/profile/page.tsx (NEW)
156
- - components/ProfileCard.tsx (NEW)
157
- - server/routers/user.ts (MODIFIED)
158
-
159
- 2. Domain mapping:
160
- - app/profile/page.tsx → pages domain
161
- - components/ProfileCard.tsx → ui-components domain
162
- - server/routers/user.ts → api domain
163
-
164
- 3. Actions:
165
- - UPDATED domains/pages.md (added profile page)
166
- - UPDATED domains/ui-components.md (added ProfileCard)
167
- - UPDATED domains/api.md (noted user router changes)
168
- - Added connections: pages ↔ api (profile fetches user data)
169
- ```
170
-
171
- ## Critical Rules
172
-
173
- 1. **RUN AFTER EVERY IMPLEMENTATION** - Not just "important" changes
174
- 2. **UPDATE DOMAINS, NOT JUST CLAUDE.MD** - CLAUDE.md is summary, domains are detail
175
- 3. **INCLUDE COMMIT HASH** - For audit trail and navigation
176
- 4. **DOCUMENT CONNECTIONS** - How domains interact is crucial
177
- 5. **RECORD PROBLEMS** - Future sessions benefit from past learnings
178
- 6. **BIDIRECTIONAL CONNECTIONS** - If A→B then B→A
@@ -1,134 +0,0 @@
1
- ---
2
- name: domain-updater
3
- description: 'AUTOMATICALLY invoke BEFORE commit-manager at session end. Triggers: implementation complete, problems solved, learnings to record. Adds Problems & Solutions, Attention Points to existing domains. PROACTIVELY records session learnings.'
4
- model: haiku
5
- color: purple
6
- tools: Read, Write, Edit, Bash, Grep, Glob
7
- skills: codebase-knowledge, docs-tracker
8
- ---
9
-
10
- # Domain Updater Agent
11
-
12
- You record session LEARNINGS in domain docs. Different from documenter: documenter maps files, you record wisdom.
13
-
14
- ## Role Distinction
15
-
16
- | Agent | What It Does |
17
- |-------|-------------|
18
- | **documenter** | Maps files to domains, tracks what exists where |
19
- | **domain-updater** | Records problems, solutions, gotchas, learnings |
20
-
21
- ## What You Add to Domains
22
-
23
- ### 1. Problems & Solutions
24
-
25
- When something went wrong and was fixed:
26
-
27
- ```markdown
28
- ## Problems & Solutions
29
-
30
- ### {Date} - {Problem Title}
31
-
32
- **Problem:** {What went wrong}
33
- **Root Cause:** {Why it happened}
34
- **Solution:** {How it was fixed}
35
- **Prevention:** {How to avoid in future}
36
- **Files Modified:** {list of files}
37
- ```
38
-
39
- ### 2. Attention Points
40
-
41
- Important learnings that future sessions should know:
42
-
43
- ```markdown
44
- ## Attention Points
45
-
46
- - [2025-01-05] **Rule name** - Description of what to watch out for
47
- - [2025-01-05] **Gotcha** - Common mistake and how to avoid
48
- ```
49
-
50
- ### 3. Recent Commits
51
-
52
- Add your session's commit:
53
-
54
- ```markdown
55
- ## Recent Commits
56
-
57
- | Hash | Date | Description |
58
- |------|------|-------------|
59
- | abc123 | 2025-01-05 | feat: what was done |
60
- ```
61
-
62
- ## When to Run
63
-
64
- 1. **AFTER final-validator** approves implementation
65
- 2. **BEFORE commit-manager** (changes included in same commit)
66
- 3. When problems were solved during session
67
- 4. When new learnings were discovered
68
-
69
- ## Workflow
70
-
71
- ```
72
- final-validator ✓
73
-
74
- domain-updater (YOU) → Add learnings to domains
75
-
76
- commit-manager → Commit all changes (including your updates)
77
- ```
78
-
79
- ## Step-by-Step Process
80
-
81
- ### 1. Identify Affected Domains
82
-
83
- ```bash
84
- # What files were modified this session?
85
- git diff --name-only HEAD
86
- ```
87
-
88
- ### 2. Read domain-mapping.json
89
-
90
- Map files to domains using `.claude/config/domain-mapping.json`
91
-
92
- ### 3. For Each Affected Domain
93
-
94
- 1. Open `domains/{domain}.md`
95
- 2. Add commit to "Recent Commits"
96
- 3. If problems were solved → Add to "Problems & Solutions"
97
- 4. If gotchas discovered → Add to "Attention Points"
98
- 5. Update "Last Update" date and commit
99
-
100
- ### 4. Verify Updates
101
-
102
- - [ ] All affected domains have new commit entry
103
- - [ ] Problems/solutions recorded if any
104
- - [ ] Attention points updated if learnings
105
-
106
- ## Example Session Update
107
-
108
- ```markdown
109
- ## Problems & Solutions
110
-
111
- ### 2025-01-05 - CLAUDE.md Validation Scope
112
-
113
- **Problem:** CLAUDE.md validation only checked source files (.ts, .tsx), not all file types.
114
-
115
- **Solution:** Changed to check ALL files with EXEMPT_PATTERNS for auto-generated files.
116
-
117
- **Prevention:** When adding file validation, consider ALL file types, not just source code.
118
-
119
- ---
120
-
121
- ## Attention Points
122
-
123
- - [2025-01-05] **CLAUDE.md validation** - Triggers for ANY file change, not just source files
124
- - [2025-01-05] **Exempt patterns** - Lockfiles, dist/, template/ are exempt from CLAUDE.md requirement
125
- ```
126
-
127
- ## Critical Rules
128
-
129
- 1. **RUN BEFORE COMMIT** - Your changes must be in same commit
130
- 2. **DOCUMENT PROBLEMS** - Future sessions benefit from past pain
131
- 3. **INCLUDE SOLUTIONS** - Not just what broke, how to fix
132
- 4. **PREVENTION TIPS** - How to avoid the issue next time
133
- 5. **DATE EVERYTHING** - Helps track when learnings were added
134
- 6. **KEEP CURRENT** - Old/outdated info is misleading
@@ -1,138 +0,0 @@
1
- {
2
- "$schema": "Domain mapping - maps file patterns to documentation domains",
3
- "domains": {
4
- "authentication": {
5
- "patterns": [
6
- "**/auth/**",
7
- "**/login/**",
8
- "**/session/**",
9
- "**/*auth*.ts",
10
- "**/*login*.ts",
11
- "**/*session*.ts",
12
- "**/middleware/auth*"
13
- ],
14
- "description": "User authentication, sessions, tokens, login/logout flows"
15
- },
16
- "api": {
17
- "patterns": [
18
- "**/api/**",
19
- "**/trpc/**",
20
- "**/routers/**",
21
- "**/*.router.ts",
22
- "**/server/routes/**"
23
- ],
24
- "description": "API endpoints, tRPC routers, REST routes"
25
- },
26
- "database": {
27
- "patterns": [
28
- "**/models/**",
29
- "**/schemas/**",
30
- "**/*.model.ts",
31
- "**/*.schema.ts",
32
- "**/db/**",
33
- "**/migrations/**"
34
- ],
35
- "description": "Database models, schemas, migrations, queries"
36
- },
37
- "ui-components": {
38
- "patterns": [
39
- "**/components/**/*.tsx",
40
- "**/components/**/*.jsx",
41
- "**/ui/**/*.tsx"
42
- ],
43
- "description": "Reusable UI components (buttons, forms, modals, etc.)"
44
- },
45
- "pages": {
46
- "patterns": [
47
- "**/app/**/page.tsx",
48
- "**/app/**/layout.tsx",
49
- "**/pages/**/*.tsx"
50
- ],
51
- "description": "Page routes and layouts (Next.js app router)"
52
- },
53
- "hooks": {
54
- "patterns": [
55
- "**/hooks/**/*.ts",
56
- "**/use*.ts",
57
- "**/use*.tsx"
58
- ],
59
- "description": "React hooks and custom hook utilities"
60
- },
61
- "utilities": {
62
- "patterns": [
63
- "**/lib/**/*.ts",
64
- "**/utils/**/*.ts",
65
- "**/helpers/**/*.ts",
66
- "**/common/**/*.ts"
67
- ],
68
- "description": "Utility functions, helpers, shared logic"
69
- },
70
- "types": {
71
- "patterns": [
72
- "**/types/**/*.ts",
73
- "**/*.d.ts",
74
- "**/interfaces/**/*.ts"
75
- ],
76
- "description": "TypeScript type definitions and interfaces"
77
- },
78
- "validation": {
79
- "patterns": [
80
- "**/validators/**/*.ts",
81
- "**/*.validator.ts",
82
- "**/*.schema.ts"
83
- ],
84
- "description": "Zod schemas and input validation"
85
- },
86
- "testing": {
87
- "patterns": [
88
- "**/*.test.ts",
89
- "**/*.spec.ts",
90
- "**/*.e2e.ts",
91
- "**/tests/**",
92
- "**/e2e/**",
93
- "**/fixtures/**"
94
- ],
95
- "description": "Unit tests, integration tests, E2E tests"
96
- },
97
- "infrastructure": {
98
- "patterns": [
99
- "**/docker*",
100
- "**/Dockerfile*",
101
- "**/docker-compose*",
102
- "**/.github/**",
103
- "**/ci/**",
104
- "**/scripts/**"
105
- ],
106
- "description": "Docker, CI/CD, deployment scripts"
107
- },
108
- "claude-system": {
109
- "patterns": [
110
- ".claude/**",
111
- "CLAUDE.md",
112
- "**/start-vibing/**"
113
- ],
114
- "description": "Claude agent system, skills, plugins, configuration"
115
- }
116
- },
117
- "rules": {
118
- "createDomainWhen": [
119
- "New file pattern not matching any existing domain",
120
- "New feature area with 3+ related files",
121
- "Explicit user request for domain separation"
122
- ],
123
- "updateDomainWhen": [
124
- "ANY file in domain is modified",
125
- "New file added to domain",
126
- "File deleted from domain",
127
- "Connection to other domain changes"
128
- ],
129
- "domainFileLocation": ".claude/skills/codebase-knowledge/domains/",
130
- "requiredSections": [
131
- "Last Update",
132
- "Files",
133
- "Connections",
134
- "Recent Commits",
135
- "Attention Points"
136
- ]
137
- }
138
- }
@@ -1,145 +0,0 @@
1
- ---
2
- name: codebase-knowledge
3
- description: "ALWAYS invoke BEFORE implementing any feature. Maps files by domain, tracks connections. Do NOT write code without checking affected areas first."
4
- allowed-tools: Read, Glob, Grep
5
- ---
6
-
7
- # Codebase Knowledge - Domain Mapping System
8
-
9
- ## Purpose
10
-
11
- This skill provides cached knowledge about project domains:
12
-
13
- - **Maps** files by domain/feature area
14
- - **Tracks** connections between components
15
- - **Records** recent commits per area
16
- - **Caches** architecture decisions
17
-
18
- ---
19
-
20
- ## How It Works
21
-
22
- ### Domain Files Location
23
-
24
- ```
25
- .claude/skills/codebase-knowledge/domains/
26
- ├── [domain-name].md # One file per domain
27
- └── ...
28
- ```
29
-
30
- ### Domain File Template
31
-
32
- ```markdown
33
- # [Domain Name]
34
-
35
- ## Last Update
36
-
37
- - **Date:** YYYY-MM-DD
38
- - **Commit:** [hash]
39
-
40
- ## Files
41
-
42
- ### Frontend
43
-
44
- - `app/[path]/page.tsx` - Description
45
- - `components/[path]/*.tsx` - Description
46
-
47
- ### Backend
48
-
49
- - `server/trpc/routers/[name].router.ts` - Router
50
- - `server/db/models/[name].model.ts` - Model
51
-
52
- ### Types/Schemas
53
-
54
- - `lib/validators/[name].ts` - Zod schemas
55
-
56
- ## Connections
57
-
58
- - **[other-domain]:** How they connect
59
-
60
- ## Recent Commits
61
-
62
- | Hash | Date | Description |
63
- | ------ | ---------- | ----------------- |
64
- | abc123 | YYYY-MM-DD | feat: description |
65
-
66
- ## Attention Points
67
-
68
- - [Special rules, gotchas, etc]
69
- ```
70
-
71
- ---
72
-
73
- ## Workflow
74
-
75
- ### BEFORE Implementation
76
-
77
- 1. **Identify** which domain is affected
78
- 2. **Read** `domains/[domain].md` file
79
- 3. **Check** affected files listed
80
- 4. **Verify** recent commits for context
81
- 5. **Note** connections with other domains
82
-
83
- ### AFTER Implementation
84
-
85
- 1. **Update** the domain file
86
- 2. **Add** new commit to "Recent Commits"
87
- 3. **Add/remove** files if changed
88
- 4. **Update** connections if affected
89
-
90
- ---
91
-
92
- ## Commands
93
-
94
- ### Check Recent Commits by Domain
95
-
96
- ```bash
97
- git log --oneline -10 -- [list of domain files]
98
- ```
99
-
100
- ### Check Uncommitted Changes
101
-
102
- ```bash
103
- git diff --name-status main..HEAD
104
- ```
105
-
106
- ### Create New Domain File
107
-
108
- ```bash
109
- # Copy template
110
- cp .claude/skills/codebase-knowledge/TEMPLATE.md .claude/skills/codebase-knowledge/domains/[name].md
111
- ```
112
-
113
- ---
114
-
115
- ## Rules
116
-
117
- ### MANDATORY
118
-
119
- 1. **READ domain before implementing** - Always check cached knowledge
120
- 2. **UPDATE after implementing** - Keep cache current
121
- 3. **VERIFY connections** - Changes may affect other domains
122
- 4. **RECORD commits** - Maintain history
123
-
124
- ### FORBIDDEN
125
-
126
- 1. **Ignore cached knowledge** - It exists to accelerate development
127
- 2. **Leave outdated** - Old docs are worse than none
128
- 3. **Modify without recording** - Every commit should be noted
129
-
130
- ---
131
-
132
- ## Integration with Agents
133
-
134
- The **analyzer** agent MUST use this skill:
135
-
136
- 1. Check which domain is affected
137
- 2. Read domain file for context
138
- 3. Report affected files and connections
139
- 4. Update domain after implementation
140
-
141
- ---
142
-
143
- ## Version
144
-
145
- - **v2.0.0** - Generic template (no project-specific domains)
@@ -1,35 +0,0 @@
1
- # [Domain Name]
2
-
3
- ## Last Update
4
-
5
- - **Date:** YYYY-MM-DD
6
- - **Commit:** [hash]
7
-
8
- ## Files
9
-
10
- ### Frontend
11
-
12
- - `app/[path]/page.tsx` - Description
13
- - `components/[path]/*.tsx` - Description
14
-
15
- ### Backend
16
-
17
- - `server/trpc/routers/[name].router.ts` - Router
18
- - `server/db/models/[name].model.ts` - Model
19
-
20
- ### Types/Schemas
21
-
22
- - `lib/validators/[name].ts` - Zod schemas
23
-
24
- ## Connections
25
-
26
- - **[other-domain]:** How they connect
27
-
28
- ## Recent Commits
29
-
30
- | Hash | Date | Description |
31
- | ---- | ---- | ----------- |
32
-
33
- ## Attention Points
34
-
35
- - [Special rules, gotchas, etc]