@su-record/vibe 3.2.62 → 4.0.0

package/skills/vibe.docs/SKILL.md

@@ -1,121 +0,0 @@
----
-name: vibe.docs
-description: Use when README, guides, architecture, release notes, agent instructions, diagrams, or codemaps must be generated or synchronized with the actual codebase.
-argument-hint: "readme, guide, arch, release, agent, diagram, or codemaps"
-user-invocable: true
----
-
-# /vibe.docs
-
-Generate or update project documentation by analyzing the actual codebase.
-
-## Usage
-
-```
-/vibe.docs readme     # README.md 생성/갱신
-/vibe.docs guide      # 사용자 가이드 (docs/GUIDE.md)
-/vibe.docs arch       # 아키텍처 문서 + Mermaid 다이어그램 (docs/ARCHITECTURE.md)
-/vibe.docs release    # 릴리즈 노트 (git history 기반)
-/vibe.docs agent      # CLAUDE.md / AGENTS.md 생성·동기화 (agents-md 검증 필수)
-/vibe.docs diagram    # Mermaid 다이어그램 (architecture/ER/flow/seq) → .vibe/diagrams/
-/vibe.docs codemaps   # 코드베이스 구조 자동 문서화 → docs/CODEMAPS/
-```
-
-## Pipeline Position
-
-```
-/vibe.spec    → Design (what to build)
-/vibe.run     → Implement (build it)
-/vibe.trace   → Verify (prove it works)
-/vibe.docs    → Document (explain it)
-```
-
----
-
-Execute the bundled implementation below — subcommand에 따라 해당 섹션 실행
-
-ARGUMENTS: $ARGUMENTS
-
-## Bundled implementation
-
-
-# vibe.docs — Project Documentation Generator
-
-Generate or update project documentation by analyzing the actual codebase.
-
-## Subcommands
-
-## Subcommands (선택된 하나만 로드)
-
-한 번의 호출은 서브커맨드 **하나만** 실행한다. 해당 reference 하나만 읽고 나머지 6개는 읽지 않는다.
-
-| 서브커맨드 | 산출물 | 본문 |
-|---|---|---|
-| `readme` | README.md | `references/readme.md` |
-| `guide` | 사용자 가이드 | `references/guide.md` |
-| `arch` | 아키텍처 문서 | `references/arch.md` |
-| `agent` | CLAUDE.md / AGENTS.md | `references/agent.md` |
-| `release` | 릴리스 노트 / CHANGELOG | `references/release.md` |
-| `diagram` | 다이어그램 | `references/diagram.md` |
-| `codemaps` | 코드맵 | `references/codemaps.md` |
-
-서브커맨드 없이 호출되면 무엇을 생성할지 사용자에게 묻는다 — 전부 생성하지 않는다.
-
-## Pipeline Integration
-
-`/vibe.docs` completes the development pipeline:
-
-```
-/vibe.spec    → Design (what to build)
-/vibe.run     → Implement (build it)
-/vibe.trace   → Verify (prove it works)
-/vibe.docs    → Document (explain it)
-```
-
-### Auto-trigger after `/vibe.trace`
-
-When `/vibe.trace` completes with all scenarios passing, suggest:
-> "All scenarios verified. Run `/vibe.docs readme` to update documentation?"
-
-## Guidelines
-
-### DO
-- Read the actual codebase before generating — never guess
-- Preserve existing documentation that's still accurate
-- Include concrete code examples from the actual project
-- Keep language consistent with project (Korean/English based on CLAUDE.md)
-- For `/vibe.docs release` (changelog mode), follow `references/api-docs-changelog.md` natively — no dedicated agent
-- For API-heavy projects (api-docs mode), follow `references/api-docs-changelog.md` natively
-- For `/vibe.docs arch` and `/vibe.docs diagram` Mermaid generation, follow `references/diagram-spec.md` natively
-- Use the `agents-md` skill for `/vibe.docs agent` — applies equally to CLAUDE.md and AGENTS.md
-
-### DON'T
-- Don't generate placeholder text ("Lorem ipsum", "TODO: fill in")
-- Don't document internal implementation details in user-facing docs
-- Don't create files without reading existing ones first
-- Don't assume features — verify by reading code
-
-## Quality Checklist
-
-Before finalizing any document:
-
-- [ ] All code examples are runnable (copy-paste ready)
-- [ ] Installation steps tested against package.json
-- [ ] Links and paths are valid
-- [ ] No placeholder text remaining
-- [ ] Consistent with project language (Korean/English)
-
-## Done Criteria
-
-- [ ] The requested document exists at its specified path.
-- [ ] Example commands, paths, and identifiers match the repository.
-- [ ] No placeholder or unverified feature claim remains.
-- [ ] Internal links and file paths resolve to real targets.
-- [ ] The document preserves the project's existing language.
-
-## 체인 의존 (reference 안에서 호출되는 스킬)
-
-reference 로 내려간 절차가 다른 스킬을 체인 호출한다. **설치 무결성 검사가 추적할 수 있도록 여기에 선언한다** —
-선언이 없으면 그 스킬이 미설치여도 아무도 잡지 못한다.
-
-- Load skill `vibe.agents-md` — `references/agent.md` 단계에서 호출

package/skills/vibe.docs/references/agent.md

@@ -1,59 +0,0 @@
-# /vibe.docs agent — Agent Instruction Files (CLAUDE.md / AGENTS.md)
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`agent` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs agent` — Agent Instruction Files (CLAUDE.md / AGENTS.md)
-
-**CLI ↔ file mapping:**
-
-| CLI | File | Support |
-|---|---|---|
-| Claude Code | `CLAUDE.md` | 100% (Primary) |
-| Codex | `AGENTS.md` | 100% (Primary) |
-| Antigravity CLI | `GEMINI.md` | 100% |
-
-Cursor is not supported — do not generate or check Cursor-specific context files.
-
-**Source of truth:**
-- **`CLAUDE.md` is the content SSOT.** Always edit it first; `AGENTS.md` is a regenerated derivative.
-- Behavioral block: `skills/vibe.docs/templates/behavioral-principles.md` (4 Karpathy principles, wrapped in `<!-- VIBE-BEHAVIORAL:START/END -->` markers).
-- **번역 규칙이 파일로 존재하면 그 파일이 SSOT다.** 프로젝트 루트에 `scripts/agents-md-rules.json` 이 있으면
-  아래 4·5번 손 치환 목록을 쓰지 않고 `npm run gen:agents-md` 로 생성한다 — 규칙을 두 곳에 적으면
-  그 순간 두 벌이 되고, 어느 쪽이 맞는지 판정할 수단이 사라진다. 검증은 `npm run gen:agents-md:check`.
-  (vibe 저장소 자신이 이 경로다. 규칙 파일이 없는 프로젝트는 4·5번을 그대로 적용한다.)
-
-**Procedure (applies to both creation and modification):**
-
-1. **Detect state** — check which of `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` exist in project root. **`CLAUDE.md` is always the SSOT**; if missing, create it first (never derive from AGENTS.md).
-2. **For `AGENTS.md`**:
-   - **If missing** → create by cloning `CLAUDE.md` + applying CLI substitution (below).
-   - **If exists** → regenerate from current `CLAUDE.md` + substitution, preserving user-specific additions outside the VIBE block.
-3. **For `GEMINI.md`**:
-   - **If missing** → create by cloning `CLAUDE.md` + applying Antigravity substitution.
-   - **If exists** → regenerate from current `CLAUDE.md` + substitution, preserving user-specific additions outside the VIBE block.
-4. **CLI substitution for `AGENTS.md`** (Codex): `Claude Code` → `Codex` · `~/.claude/` → `~/.codex/` · `.claude/` → `.codex/` · `CLAUDE.md` → `AGENTS.md`. `CLAUDE.md` itself gets no substitution.
-5. **CLI substitution for `GEMINI.md`** (Antigravity): `Claude Code` → `Antigravity CLI` · `~/.claude/` → `~/.gemini/` · `.claude/` → `.gemini/` · `CLAUDE.md` → `GEMINI.md`.
-6. **Validate every touched file (whether newly created or modified)** via the `agents-md` skill — see validation block below. **Never write or save without running this step.**
-7. Report per file: created / updated / skipped / validation warnings.
-
-**Idempotent:** Re-running re-syncs the behavioral block and re-applies substitutions without duplication.
-
-**Mandatory validation (every create & every update) — Load skill `vibe.agents-md`:**
-
-- Size target 60–150 lines (Optimal). Warn at 200+, force split/trim at 300+.
-- 4-question check per line (outside `VIBE-BEHAVIORAL` block):
-  - Would the agent make a mistake without this? (No → delete)
-  - Needed every session? (No → move to SPEC/plan)
-  - Can a linter/hook replace it? (Yes → move)
-  - Discoverable from code? (Yes → delete)
-- Lost-in-the-Middle: critical rules at top, frequently-violated rules at bottom.
-- Addy Osmani test: "Can the agent discover this by reading the code?" → Yes = delete.
-- Strip tech-stack name-drops already stated in `package.json`.
-
-Report line ranges to trim per file. Do not auto-delete; surface findings for user approval before finalizing.
-
-**When to run:**
-- After `vibe init` / `vibe update` if `CLAUDE.md` or `AGENTS.md` is missing or out of sync.
-- After upgrading `@su-record/vibe` when the behavioral template changes.
-- Whenever the SSOT file is edited — re-sync `AGENTS.md`.
-- User explicitly asks to refresh agent instructions.

package/skills/vibe.docs/references/api-docs-changelog.md

@@ -1,34 +0,0 @@
-# docs — API Docs & Changelog Spec
-
-> Loaded by docs SKILL.md for `/vibe.docs release` (changelog mode) and API-heavy projects (api-docs mode) — documentation rules for the two artifacts that go stale fastest: API docs and changelogs.
-
-## API Mode
-
-Walk the route handlers/controllers in the given scope and document each
-endpoint: method + path, auth requirement, parameters (path/query/body with
-types, required vs optional, enum values), success and error responses (all
-status codes actually returned), and a runnable example (curl or fetch). List
-endpoints that exist in code but lack documentation — the gap list is as
-valuable as the docs.
-
-## Changelog Mode
-
-From `git diff` and `git log`, classify changes as breaking / added /
-changed / fixed / performance / internal / dependencies. Recommend the
-semantic version bump with a one-line reason. Every breaking change gets
-migration steps; every fix states old vs new behavior.
-
-## Constraints
-
-Return documentation as text output only — never create or write files; the
-calling command decides where content lands. Descriptions are user-facing:
-what changed for the consumer, not which internal function was refactored
-(pure refactors go under Internal, briefly). Document what the code actually
-does, not what comments claim — when they disagree, flag the discrepancy
-rather than picking one silently.
-
-## Done
-
-- API mode: every endpoint in scope documented or explicitly listed as an undocumented gap
-- Changelog mode: all changes classified, version bump recommended with reason, breaking changes have migration steps
-- Output is paste-ready text; zero files created

package/skills/vibe.docs/references/arch.md

@@ -1,28 +0,0 @@
-# /vibe.docs arch — Architecture Documentation
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`arch` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs arch` — Architecture Documentation
-
-Generate architecture overview with diagrams:
-
-1. **Module map**: Directory structure → responsibility mapping
-2. **Dependency graph**: Import analysis → Mermaid diagram
-3. **Data flow**: Entry points → processing → output
-4. **Key decisions**: Extract from CLAUDE.md and code comments
-
-Output: `docs/ARCHITECTURE.md`
-
-**Mermaid diagram generation:**
-```
-File-pattern search: src/**/ → module list
-Text search: pattern="^import .+ from" → dependency edges
-Full-file reading: CLAUDE.md → architecture notes
-
-Generate:
-graph TD
-    CLI[CLI Commands] --> Core[Core Logic]
-    Core --> Infra[Infrastructure]
-    Infra --> DB[(Database)]
-    Infra --> API[External APIs]
-```

package/skills/vibe.docs/references/codemaps-output.md

@@ -1,23 +0,0 @@
-# docs — Codemaps: Generated Files & Contents
-
-> Loaded by docs SKILL.md `codemaps` mode — full generated-files tree, per-file contents, and tools used.
-
-**Generated Files:**
-```
-docs/CODEMAPS/
-├── INDEX.md          # Overview of all areas
-├── frontend.md       # Frontend structure
-├── backend.md        # API/backend structure
-├── database.md       # Schema documentation
-└── integrations.md   # External services
-```
-
-**Each file contains:**
-- Module table (name, path, description)
-- Data flow diagram (Mermaid)
-- Dependencies list
-- Related areas
-
-**Tools Used:**
-- ts-morph (TypeScript AST)
-- madge (dependency graph)

package/skills/vibe.docs/references/codemaps.md

@@ -1,17 +0,0 @@
-# /vibe.docs codemaps — Codemaps Generation
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`codemaps` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs codemaps` — Codemaps Generation
-
-Generate auto-documentation from codebase structure directly (native
-capability — no dedicated agent).
-
-**Output Location:** `docs/CODEMAPS/`
-
-> Read `references/codemaps-output.md` for the full generated-files tree, per-file contents, and tools used.
-
-**Example:**
-```
-/vibe.docs codemaps
-```

package/skills/vibe.docs/references/diagram-spec.md

@@ -1,34 +0,0 @@
-# docs — Diagram Generation Spec
-
-> Loaded by docs SKILL.md `diagram` mode — Mermaid diagram generation rules (architecture, ERD, flowcharts, sequence).
-
-Produce a Mermaid diagram that reflects the actual code, not a generic
-picture. Ground it in sources first: folder structure and imports for
-architecture; `models/`, `migrations/`, `schema.*`, ORM definitions for ERDs;
-the real branch/return structure of the code for flowcharts.
-
-## Output Conventions
-
-- Architecture → `graph TB` with layers top-to-bottom (client → API → data);
-  label edges with the interaction (`HTTP`, `Query`, `Cache`)
-- ERD → `erDiagram` with cardinality (`||--o{`), PK/FK/UK markers, and the
-  fields that matter for understanding relationships (not every column)
-- Flows → `flowchart TD` with decision diamonds carrying their conditions on
-  the edge labels
-- One diagram per concern — split rather than cram; keep each diagram readable
-  at ~20 nodes or fewer
-- Save to `.vibe/diagrams/{type}-{YYYY-MM-DD}.md` and note render options
-  (GitHub/GitLab render Mermaid natively; otherwise https://mermaid.live/)
-
-## Constraints
-
-Accuracy over completeness: omit elements you couldn't verify in the code
-rather than inventing plausible boxes; if a relationship is inferred rather
-than read, mark it. Valid Mermaid syntax is non-negotiable — quote labels
-containing special characters.
-
-## Done
-
-- Diagram matches verifiable code structure (each node traceable to a file/table/function)
-- Mermaid syntax is valid and renders
-- Saved to `.vibe/diagrams/` with a one-paragraph summary of what it shows

package/skills/vibe.docs/references/diagram.md

@@ -1,24 +0,0 @@
-# /vibe.docs diagram — Diagram Generation
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`diagram` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs diagram` — Diagram Generation
-
-Generate Mermaid diagrams for architecture, ERD, flowchart, or sequence
-visualization directly (native capability — no dedicated agent). Ground the
-diagram in sources first: folder structure and imports for architecture;
-`models/`, `migrations/`, `schema.*`, ORM definitions for ERDs; the real
-branch/return structure of the code for flowcharts.
-
-**Options:**
-- `/vibe.docs diagram` (default): Architecture overview
-- `/vibe.docs diagram --er`: Entity-Relationship Diagram
-- `/vibe.docs diagram --flow`: Flowchart
-- `/vibe.docs diagram --seq`: Sequence Diagram
-
-> Read `references/diagram-spec.md` for the full output conventions (Mermaid syntax per diagram type, save location, accuracy constraints).
-
-**Example:**
-```
-/vibe.docs diagram --er
-```

package/skills/vibe.docs/references/guide.md

@@ -1,23 +0,0 @@
-# /vibe.docs guide — User Guide
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`guide` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs guide` — User Guide
-
-Generate a step-by-step user guide:
-
-1. **Installation**: Detect package manager, prerequisites
-2. **Configuration**: Find all config files, document each option
-3. **Usage**: Extract CLI commands or API usage patterns
-4. **FAQ**: Common issues from error handling patterns
-5. **Troubleshooting**: Known edge cases from test files
-
-Output: `docs/GUIDE.md`
-
-**Analysis approach:**
-```
-Full-file reading: package.json → bin, scripts, peerDependencies
-File-pattern search: src/cli/commands/*.ts → CLI command list
-Text search: pattern="throw new|Error\(" → common error scenarios
-Text search: pattern="(process\.env|config)\.\w+" → configuration options
-```

package/skills/vibe.docs/references/readme.md

@@ -1,45 +0,0 @@
-# /vibe.docs readme — README Generation
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`readme` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs readme` — README Generation
-
-Analyze the codebase and generate a complete README.md:
-
-1. **Detect project nature**: Read package.json, CLAUDE.md, existing README
-2. **Extract key info**: Tech stack, installation, usage, API surface
-3. **Generate sections**:
-
-```markdown
-# Project Name
-> One-line description from package.json
-
-## What is this?
-[2-3 sentences explaining the problem and solution]
-
-## Quick Start
-[Installation + minimal usage example]
-
-## Features
-[Auto-detected from codebase — exported functions, CLI commands, API endpoints]
-
-## Architecture
-[High-level module diagram if 5+ source directories]
-
-## Configuration
-[Detected config files and their purposes]
-
-## Development
-[Build, test, lint commands from package.json scripts]
-
-## License
-```
-
-**Analysis approach:**
-```
-Full-file reading: package.json → name, description, scripts, dependencies
-File-pattern search: src/**/*.ts → module structure
-Text search: pattern="export (function|class|const)" → public API surface
-Text search: pattern="(app|router)\.(get|post|put|delete)" → API endpoints
-Full-file reading: CLAUDE.md → project conventions
-```

package/skills/vibe.docs/references/release.md

@@ -1,31 +0,0 @@
-# /vibe.docs release — Release Notes
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`release` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs release` — Release Notes
-
-Generate release notes from git history:
-
-1. **Collect**: `git log` since last tag
-2. **Classify**: feat/fix/refactor/docs/chore from commit messages
-3. **Group**: By category with breaking changes highlighted
-4. **Format**: Semantic versioning suggestion
-
-Output: `RELEASE_NOTES.md` or append to `CHANGELOG.md`
-
-**Output format:**
-```markdown
-## [x.y.z] - YYYY-MM-DD
-
-### Breaking Changes
-- ...
-
-### Features
-- feat: description (#PR)
-
-### Bug Fixes
-- fix: description (#PR)
-
-### Other
-- refactor/docs/chore items
-```

package/skills/vibe.docs/templates/architecture.md

@@ -1,80 +0,0 @@
-# Architecture: {{PROJECT_NAME}}
-
-> Version: {{VERSION}} | Updated: {{DATE}}
-
-## Overview
-
-{{2-3 SENTENCES: WHAT THIS SYSTEM DOES AND ITS PRIMARY ARCHITECTURAL APPROACH.}}
-
-## System Diagram
-
-```mermaid
-graph TD
-    {{ENTRY_POINT}}[{{ENTRY_LABEL}}] --> {{MODULE_A}}[{{MODULE_A_LABEL}}]
-    {{MODULE_A}} --> {{MODULE_B}}[{{MODULE_B_LABEL}}]
-    {{MODULE_A}} --> {{MODULE_C}}[{{MODULE_C_LABEL}}]
-    {{MODULE_B}} --> {{STORE}}[({{STORE_LABEL}})]
-    {{MODULE_C}} --> {{EXTERNAL}}[{{EXTERNAL_SERVICE_LABEL}}]
-```
-
-> Replace nodes above based on actual `import` analysis. Run:
-> `grep -r "^import .* from" src/ | sed 's/.*from //' | sort | uniq` to get dependency edges.
-
-## Module Responsibilities
-
-| Module / Directory | Responsibility | Key Files |
-|--------------------|---------------|-----------|
-| `{{MODULE_1}}/` | {{RESPONSIBILITY}} | `{{KEY_FILE}}` |
-| `{{MODULE_2}}/` | {{RESPONSIBILITY}} | `{{KEY_FILE}}` |
-| `{{MODULE_3}}/` | {{RESPONSIBILITY}} | `{{KEY_FILE}}` |
-
-## Data Flow
-
-```
-{{INPUT_SOURCE}}
-  ↓ {{STEP_1_DESCRIPTION}}
-{{PROCESSING_MODULE}}
-  ↓ {{STEP_2_DESCRIPTION}}
-{{OUTPUT_TARGET}}
-```
-
-### Key Data Entities
-
-| Entity | Where Defined | Storage |
-|--------|--------------|---------|
-| `{{ENTITY_1}}` | `{{FILE_PATH}}` | {{DB / FILE / MEMORY}} |
-| `{{ENTITY_2}}` | `{{FILE_PATH}}` | {{DB / FILE / MEMORY}} |
-
-## External Dependencies
-
-| Service | Purpose | Auth Method |
-|---------|---------|-------------|
-| `{{SERVICE_1}}` | {{PURPOSE}} | {{API_KEY / OAUTH / NONE}} |
-| `{{SERVICE_2}}` | {{PURPOSE}} | {{AUTH_METHOD}} |
-
-## Key Decisions
-
-| Decision | Chosen Approach | Alternatives Considered | Rationale |
-|----------|----------------|------------------------|-----------|
-| {{DECISION_1}} | {{CHOICE}} | {{ALTERNATIVES}} | {{WHY}} |
-| {{DECISION_2}} | {{CHOICE}} | {{ALTERNATIVES}} | {{WHY}} |
-
-## Constraints & Non-Goals
-
-**Constraints:**
-- {{CONSTRAINT_1}} (e.g., "Must work offline")
-- {{CONSTRAINT_2}}
-
-**Non-goals (out of scope):**
-- {{NON_GOAL_1}}
-- {{NON_GOAL_2}}
-
-## Local Development Setup
-
-```bash
-{{SETUP_COMMANDS}}
-```
-
-## Further Reading
-
-- {{INTERNAL_LINK_OR_DOC}}

package/skills/vibe.docs/templates/behavioral-principles.md

@@ -1,47 +0,0 @@
-<!-- VIBE-BEHAVIORAL:START -->
-## Behavioral Principles (Karpathy-Inspired)
-
-Derived from Andrej Karpathy's observations on LLM coding pitfalls.
-Source: https://github.com/forrestchang/andrej-karpathy-skills
-
-### Think Before Coding
-
-**Don't assume. Don't hide confusion. Surface tradeoffs.**
-
-- State assumptions explicitly. If uncertain, ask rather than guess.
-- Present multiple interpretations — don't pick silently when ambiguity exists.
-- Push back when a simpler approach exists.
-- Stop when confused. Name what's unclear. Ask.
-
-### Simplicity First
-
-**Minimum code that solves the problem. Nothing speculative.**
-
-- No features beyond what was asked.
-- No abstractions for single-use code.
-- No flexibility or configurability that wasn't requested.
-- No error handling for impossible scenarios.
-- If 200 lines could be 50, rewrite it.
-
-### Surgical Changes
-
-**Touch only what you must. Clean up only your own mess.**
-
-- Don't improve adjacent code, comments, or formatting.
-- Don't refactor things that aren't broken.
-- Match existing style, even if you'd do it differently.
-- Remove orphans YOUR changes created — leave pre-existing dead code alone.
-- Every changed line should trace to the user's request.
-
-### Goal-Driven Execution
-
-**Define success criteria. Loop until verified.**
-
-| Instead of | Transform to |
-|------------|--------------|
-| "Add validation" | "Write tests for invalid inputs, then make them pass" |
-| "Fix the bug" | "Write a test that reproduces it, then make it pass" |
-| "Refactor X" | "Ensure tests pass before and after" |
-
-Strong success criteria enable independent looping. Weak criteria ("make it work") require constant clarification.
-<!-- VIBE-BEHAVIORAL:END -->

package/skills/vibe.docs/templates/readme.md

@@ -1,84 +0,0 @@
-# {{PROJECT_NAME}}
-
-> {{ONE_LINE_DESCRIPTION_FROM_PACKAGE_JSON}}
-
-## What is this?
-
-{{2-3 SENTENCES: THE PROBLEM THIS PROJECT SOLVES AND HOW IT SOLVES IT.}}
-
-## Quick Start
-
-```bash
-# Install
-{{PACKAGE_MANAGER}} install {{PACKAGE_NAME}}
-
-# Minimal usage example
-{{USAGE_EXAMPLE}}
-```
-
-## Features
-
-- **{{FEATURE_1}}** — {{BRIEF_DESCRIPTION}}
-- **{{FEATURE_2}}** — {{BRIEF_DESCRIPTION}}
-- **{{FEATURE_3}}** — {{BRIEF_DESCRIPTION}}
-
-## Architecture
-
-> Include this section if the project has 5+ source directories.
-
-```
-{{PROJECT_NAME}}/
-├── {{DIR_1}}/      # {{RESPONSIBILITY_1}}
-├── {{DIR_2}}/      # {{RESPONSIBILITY_2}}
-└── {{DIR_3}}/      # {{RESPONSIBILITY_3}}
-```
-
-## Configuration
-
-| File | Purpose |
-|------|---------|
-| `{{CONFIG_FILE_1}}` | {{PURPOSE}} |
-| `{{CONFIG_FILE_2}}` | {{PURPOSE}} |
-
-**Key environment variables:**
-
-| Variable | Required | Default | Description |
-|----------|----------|---------|-------------|
-| `{{ENV_VAR_1}}` | Yes / No | `{{DEFAULT}}` | {{DESCRIPTION}} |
-
-## Development
-
-```bash
-# Install dependencies
-{{INSTALL_COMMAND}}
-
-# Build
-{{BUILD_COMMAND}}
-
-# Test
-{{TEST_COMMAND}}
-
-# Lint
-{{LINT_COMMAND}}
-```
-
-## API Reference
-
-> Include if the project exposes a public API.
-
-### `{{FUNCTION_OR_CLASS_NAME}}`
-
-```typescript
-{{FUNCTION_SIGNATURE}}
-```
-
-{{DESCRIPTION}}
-
-**Parameters:**
-- `{{PARAM_1}}` — {{TYPE}}: {{DESCRIPTION}}
-
-**Returns:** `{{RETURN_TYPE}}` — {{DESCRIPTION}}
-
-## License
-
-{{LICENSE}} — see [LICENSE](./LICENSE)