start-vibing 1.1.2 → 1.1.3

package/template/.claude/skills/docs-tracker/SKILL.md

@@ -1,239 +1,63 @@
----
-name: docs-tracker
-description: Automates documentation maintenance. Detects modified files via git diff, creates docs for new files, updates docs for modified files, generates changelog. Use after implementation to keep docs current.
-allowed-tools: Read, Glob, Grep, Bash
----
-
-# Docs Tracker - Automatic Documentation System
-
-## Purpose
-
-This skill automates documentation maintenance:
-
-- **Detects** modified files via git diff
-- **Compares** with existing documentation
-- **Creates** docs for new files
-- **Updates** docs for modified files
-- **Removes** docs for deleted files
-- **Generates** automatic changelog
-
----
-
-## Execution Flow
-
-```
-1. DETECT CHANGES → git diff --name-status
-        ↓
-2. CLASSIFY CHANGES → A=Added, M=Modified, D=Deleted
-        ↓
-3. CHECK EXISTING DOCS → docs/, codebase-knowledge/domains/
-        ↓
-4. EXECUTE ACTIONS → Create, update, or remove docs
-```
-
----
-
-## Detection Commands
-
-### Changes Since Last Commit
-
-```bash
-git diff --name-status HEAD~1
-```
-
-### Changes vs Main
-
-```bash
-git diff --name-status main..HEAD
-```
-
-### Added Files
-
-```bash
-git diff --name-status main..HEAD | grep "^A"
-```
-
-### Modified Files
-
-```bash
-git diff --name-status main..HEAD | grep "^M"
-```
-
-### Deleted Files
-
-```bash
-git diff --name-status main..HEAD | grep "^D"
-```
-
-### Detailed File Diff
-
-```bash
-git diff main..HEAD -- path/to/file.ts
-```
-
----
-
-## File → Doc Mapping
-
-| File Type             | Related Documentation                         |
-| --------------------- | --------------------------------------------- |
-| `server/routers/*.ts` | `codebase-knowledge/domains/[domain].md`      |
-| `server/models/*.ts`  | `codebase-knowledge/domains/[domain].md`      |
-| `app/**/page.tsx`     | `docs/flows/[feature].md`                     |
-| `components/**/*.tsx` | `docs/components/[component].md` (if complex) |
-| `lib/**/*.ts`         | `docs/utils/[lib].md` (if exported)           |
-
----
-
-## Update Rules
-
-### CREATE Doc When:
-
-- [ ] New file in `server/routers/` → Update domain
-- [ ] New file in `server/models/` → Update domain
-- [ ] New page in `app/` → Create flow doc if complex
-- [ ] New complex component → Consider doc
-
-### UPDATE Doc When:
-
-- [ ] tRPC procedure changed signature
-- [ ] Model changed schema
-- [ ] Page changed main flow
-- [ ] Connections between domains changed
-
-### REMOVE Doc When:
-
-- [ ] File was deleted
-- [ ] Feature was completely removed
-- [ ] Component was discontinued
-
----
-
-## Changelog Template
-
-```markdown
-## [Unreleased] - YYYY-MM-DD
-
-### Added
-
-- New feature X in `path/to/file.ts`
-- New component Y
-
-### Changed
-
-- Changed behavior of Z
-- Refactored module W
-
-### Fixed
-
-- Fixed bug in A
-- Resolved issue #123
-
-### Removed
-
-- Removed obsolete feature B
-
-### Docs Updated
-
-- Updated `codebase-knowledge/domains/[domain].md`
-- Created `docs/flows/[feature].md`
-```
-
----
-
-## Pre-Commit Checklist
-
-### 1. Detect Changes
-
-```bash
-git diff --name-status --cached
-```
-
-### 2. For Each Modified File
-
-- [ ] Which domain does it belong to?
-- [ ] Is domain updated in `codebase-knowledge/domains/`?
-- [ ] Has flow doc in `docs/flows/`? Needs update?
-- [ ] Commit hash will be added to domain?
-
-### 3. For Added Files
-
-- [ ] Which domain? Add to file list
-- [ ] Needs own doc or just update domain?
-- [ ] Connections with other domains?
-
-### 4. For Deleted Files
-
-- [ ] Remove from `codebase-knowledge/domains/`
-- [ ] Remove flow doc if exists
-- [ ] Update connections in related domains
-
----
-
-## Integration with Codebase-Knowledge
-
-### Update Domain After Change
-
-```markdown
-## Domain Update: [name]
-
-### Changes Detected
-
-| File         | Status   | Description    |
-| ------------ | -------- | -------------- |
-| path/file.ts | Modified | [what changed] |
-
-### Required Updates in domains/[domain].md
-
-- [ ] Update "Last Update" with date and commit
-- [ ] Add/remove files from list
-- [ ] Update "Recent Commits"
-- [ ] Check "Connections" if integration changed
-- [ ] Update "Attention Points" if applicable
-```
-
----
-
-## Output Format
-
-```markdown
-## DOCS TRACKER - Report
-
-### Changes Detected
-
-- **Added:** X files
-- **Modified:** Y files
-- **Deleted:** Z files
-
-### Docs That Need Update
-
-| Doc              | Type   | Action | Priority |
-| ---------------- | ------ | ------ | -------- |
-| domains/auth.md  | domain | update | HIGH     |
-| flows/feature.md | flow   | create | MEDIUM   |
-
-### Actions Executed
-
-- [x] Updated `domains/auth.md` with commit abc123
-- [x] Created `flows/new-feature.md`
-- [x] Removed `flows/obsolete.md`
-
-### Changelog Generated
-
-[changelog preview]
-```
-
----
-
-## Critical Rules
-
-1. **ALWAYS run before commit** - Outdated docs are technical debt
-2. **NEVER ignore new files** - Every file deserves documentation
-3. **KEEP changelog updated** - Facilitates releases
-4. **SYNC with codebase-knowledge** - It's the source of truth
-
----
-
-## Version
-
-- **v2.0.0** - Generic template
+---
+name: docs-tracker
+description: Tracks documentation that needs updating after code changes. Activates after code is written, after git commits, when files were modified, or when user says 'update docs', 'changelog', or 'document changes'.
+allowed-tools: Read, Glob, Grep, Bash
+---
+
+# Docs Tracker
+
+## When to Use
+
+- After implementation completes
+- Before committing changes
+- When user asks about documentation
+
+## Detection Commands
+
+```bash
+# Changes since last commit
+git diff --name-status HEAD~1
+
+# Changes vs main branch
+git diff --name-status main..HEAD
+
+# Staged changes
+git diff --name-status --cached
+```
+
+## File → Doc Mapping
+
+| File Type | Update This |
+|-----------|-------------|
+| `server/routers/*.ts` | `domains/[domain].md` |
+| `server/models/*.ts` | `domains/[domain].md` |
+| `app/**/page.tsx` | `docs/flows/[feature].md` |
+| `components/**/*.tsx` | Domain file or component doc |
+
+## Workflow
+
+1. **Detect** - `git diff --name-status`
+2. **Classify** - Added/Modified/Deleted
+3. **Update** - Relevant domain files
+4. **Changelog** - Add entry if significant
+
+## Changelog Format
+
+```markdown
+## [Unreleased]
+
+### Added
+- New feature X
+
+### Changed
+- Modified behavior of Y
+
+### Fixed
+- Bug in Z
+```
+
+## Rules
+
+1. **Run before commit** - outdated docs = tech debt
+2. **Update domains** - sync with codebase-knowledge
+3. **Keep changelog current** - facilitates releases

package/template/.claude/skills/final-check/SKILL.md

@@ -1,284 +1,72 @@
----
-name: final-check
-description: Final validation before task completion. Verifies all skills were consulted, documentation updated, tests pass. HAS VETO POWER - blocks incomplete tasks.
-allowed-tools: Read, Grep, Glob, Bash
----
-
-# Final Check - Final Validation System
-
-## VETO POWER
-
-> **WARNING:** This skill HAS VETO POWER.
-> If rule violated, MUST:
->
-> 1. STOP and list violations
-> 2. REQUIRE fix before approving
-> 3. Re-validate after fixes
-
----
-
-## Purpose
-
-This skill is the LAST check before task completion:
-
-- **Validates** all CLAUDE.md rules
-- **Verifies** all skills were consulted
-- **Confirms** documentation was updated
-- **Ensures** nothing was forgotten
-- **Blocks** incomplete tasks
-
----
-
-## Mega Validation Checklist
-
-### 1. CODEBASE-KNOWLEDGE
-
-- [ ] Affected domain consulted BEFORE implementing?
-- [ ] Domain file UPDATED after implementing?
-- [ ] Commit hash added?
-- [ ] Connections verified?
-
-### 2. DOCS-TRACKER
-
-- [ ] Changes detected via git diff?
-- [ ] New documentation created (if needed)?
-- [ ] Existing documentation updated?
-- [ ] Changelog updated?
-
-### 3. TEST-COVERAGE
-
-- [ ] New files have test or exemption?
-- [ ] New tRPC routes have unit test?
-- [ ] New pages have E2E spec?
-- [ ] E2E uses `auth.helper.ts` correctly?
-- [ ] No `.skip()` added?
-- [ ] All tests pass?
-
-### 4. UI-UX-AUDIT
-
-- [ ] Competitors researched (if UI)?
-- [ ] Accessibility validated?
-- [ ] Responsiveness tested?
-- [ ] Skeleton created (if new component)?
-- [ ] Zero horizontal overflow?
-
-### 5. SECURITY-SCAN
-
-- [ ] User ID always from session?
-- [ ] Sensitive data not sent to frontend?
-- [ ] Zod validation on all routes?
-- [ ] OWASP Top 10 verified?
-- [ ] No pending VETO?
-
-### 6. QUALITY-GATE
-
-- [ ] `bun run typecheck` passes?
-- [ ] `bun run lint` passes?
-- [ ] `bun run test` passes?
-- [ ] `bun run test:e2e` passes?
-- [ ] `bun run build` passes?
-
----
-
-## Checklist by Task Type
-
-### New Feature
-
-```markdown
-### Before Implementation
-
-- [ ] Consulted codebase-knowledge domain?
-- [ ] Researched competitors (if UI)?
-
-### During Implementation
-
-- [ ] Followed code patterns?
-- [ ] Created skeleton for components?
-- [ ] Validated inputs with Zod?
-- [ ] User ID always from session?
-
-### After Implementation
-
-- [ ] Created unit tests?
-- [ ] Created E2E tests?
-- [ ] Updated codebase-knowledge?
-- [ ] Updated docs/flows (if applicable)?
-- [ ] Ran full quality-gate?
-- [ ] Security-scan approved?
-```
-
-### Bug Fix
-
-```markdown
-### Before
-
-- [ ] Consulted affected domain?
-- [ ] Identified root cause?
-
-### During
-
-- [ ] Fix is minimal and focused?
-- [ ] Doesn't introduce regression?
-
-### After
-
-- [ ] Test covering the bug?
-- [ ] Updated domain with commit?
-- [ ] Quality-gate passes?
-```
-
-### Refactor
-
-```markdown
-### Before
-
-- [ ] Consulted affected domains?
-- [ ] Mapped all dependencies?
-
-### During
-
-- [ ] Maintained existing behavior?
-- [ ] Didn't break tests?
-
-### After
-
-- [ ] All tests pass?
-- [ ] Updated affected domains?
-- [ ] Quality-gate passes?
-```
-
----
-
-## Validation Flow
-
-```
-TASK COMPLETE? (developer thinks done)
-        ↓
-1. VERIFY CODEBASE-KNOWLEDGE → Consulted? Updated?
-        ↓
-2. VERIFY DOCS-TRACKER → Docs updated? Changelog?
-        ↓
-3. VERIFY TEST-COVERAGE → All files have tests? Pass?
-        ↓
-4. VERIFY UI-UX-AUDIT (if UI) → Research? Accessibility?
-        ↓
-5. VERIFY SECURITY-SCAN → No VETO? OWASP OK?
-        ↓
-6. VERIFY QUALITY-GATE → All checks pass?
-        ↓
-    ┌─────────┴─────────┐
-    ↓                   ↓
-VIOLATION           ALL OK
-→ VETO              → APPROVED
-→ LIST ISSUES       → CAN COMMIT
-```
-
----
-
-## Output Format
-
-### Approved
-
-```markdown
-## FINAL CHECK - APPROVED
-
-### Task Summary
-
-- **Type:** Feature
-- **Domain:** [domain]
-- **Files:** X modified
-
-### Verifications
-
-- [x] Codebase-Knowledge: Consulted and updated
-- [x] Docs-Tracker: Changelog updated
-- [x] Test-Coverage: Unit 3/3, E2E 2/2 pass
-- [x] UI-UX-Audit: Competitors researched, accessible
-- [x] Security-Scan: No vulnerabilities
-- [x] Quality-Gate: All checks pass
-
-**STATUS: APPROVED** - Ready to commit
-```
-
-### Vetoed
-
-```markdown
-## FINAL CHECK - VETOED
-
-### Task Summary
-
-- **Type:** Feature
-- **Domain:** [domain]
-
-### Violations Found
-
-#### ❌ Codebase-Knowledge
-
-- **Violation:** Domain NOT updated after implementation
-- **Action:** Update domain file with commit hash
-
-#### ❌ Test-Coverage
-
-- **Violation:** New file without test
-- **File:** `components/NewComponent.tsx`
-- **Action:** Create E2E spec
-
-**STATUS: VETOED** - 2 violations. Fix before commit.
-
-### Next Steps
-
-1. Update domain file
-2. Create test for new component
-3. Re-run final-check
-```
-
----
-
-## VETO Rules
-
-### IMMEDIATE VETO
-
-1. Security-scan found critical vulnerability
-2. Quality-gate doesn't pass
-3. Tests failing
-4. Codebase-knowledge not updated
-
-### VETO BEFORE MERGE
-
-1. Docs not updated
-2. Skeleton missing (if new component)
-3. Changelog not updated
-
-### WARNING (No veto)
-
-1. Coverage below ideal (but critical tests exist)
-2. Optional docs missing
-
----
-
-## Quick Command
-
-```bash
-# Run full validation
-bun run typecheck && bun run lint && bun run test && bun run test:e2e && bun run build
-
-# If all pass, manually verify:
-# - codebase-knowledge updated?
-# - docs updated?
-# - skeleton created?
-```
-
----
-
-## Critical Rules
-
-1. **HAS VETO POWER** - Last barrier before commit
-2. **VERIFIES EVERYTHING** - All skills, all rules
-3. **NO EXCUSES** - Rule is rule
-4. **DOCUMENTS VIOLATIONS** - For learning
-
----
-
-## Version
-
-- **v2.0.0** - Generic template
+---
+name: final-check
+description: Final validation before commits. HAS VETO POWER. Activates when user says 'commit', 'ready to commit', 'finalize', 'done', or when workflow is near completion. Blocks if any validation fails.
+allowed-tools: Read, Grep, Glob, Bash
+---
+
+# Final Check
+
+## VETO POWER
+
+This skill CAN and MUST block incomplete tasks.
+
+## When to Use
+
+- Before any commit
+- When user says task is "done"
+- After all other agents completed
+
+## Mega Checklist
+
+### 1. Codebase Knowledge
+- [ ] Domain consulted before implementing?
+- [ ] Domain updated after implementing?
+- [ ] Commit hash added?
+
+### 2. Docs Tracker
+- [ ] Documentation updated?
+- [ ] Changelog entry added?
+
+### 3. Test Coverage
+- [ ] New files have tests?
+- [ ] All tests pass?
+- [ ] No `.skip()` added?
+
+### 4. Security Scan
+- [ ] User ID from session?
+- [ ] No sensitive data to frontend?
+- [ ] Zod validation on routes?
+
+### 5. Quality Gate
+- [ ] `bun run typecheck` passes?
+- [ ] `bun run lint` passes?
+- [ ] `bun run test` passes?
+- [ ] `bun run build` passes?
+
+### 6. UI/UX (if applicable)
+- [ ] Competitors researched?
+- [ ] Accessibility validated?
+- [ ] All viewports tested?
+
+## Quick Validation
+
+```bash
+bun run typecheck && bun run lint && bun run test && bun run build
+```
+
+## Output
+
+**APPROVED:** All checks pass → ready to commit
+**VETOED:** Violations found → fix before commit
+
+## VETO Rules
+
+### Immediate VETO
+- Security vulnerability found
+- Tests failing
+- Build failing
+- Domain not updated
+
+### VETO Before Merge
+- Docs not updated
+- Changelog missing