docs: rename methodology files to include 'vibe-coding-profile'

devakone · claude · devakone · commit 95d986adfdec · 2026-02-12T07:13:30.000-05:00
Renamed for clarity:
- how-vibed-works.md → how-vibe-coding-profile-works.md
- vibe-metrics-v2.md → vibe-coding-profile-metrics-v2.md

Updated all internal references across documentation.

Co-Authored-By: Claude Opus 4.5 &lt;noreply@anthropic.com&gt;
diff --git a/Agents.md b/Agents.md
@@ -18,7 +18,7 @@ This document provides instructions for AI agents working on the Vibed Coding co
 See `docs/PRD.md` for full product requirements and `docs/architecture/inngest-integration.md` for job processing details.
 
 **Key Reference Docs:**
-- [How Vibed Works](docs/how-vibed-works.md) — Product-friendly explanation of analysis
+- [How Vibe Coding Profile Works](docs/how-vibe-coding-profile-works.md) — Product-friendly explanation of analysis
 - [Vibed Analysis Pipeline](docs/architecture/vibed-analysis-pipeline.md) — Technical architecture with algorithms and data flow
 
 ---
diff --git a/docs/architecture/ai-tool-metrics.md b/docs/architecture/ai-tool-metrics.md
@@ -239,9 +239,9 @@ Returns `null` when `!detected || tools.length === 0`.
 ## Related Documentation
 
 - [Multi-Agent Detection PRD](../prd/analysis/multi-agent-detection.md) — Signal extraction phases
-- [Vibe Metrics v2](./vibe-metrics-v2.md) — Core axis computation
+- [Vibe Coding Profile Metrics v2](./vibe-coding-profile-metrics-v2.md) — Core axis computation
 - [Analysis Pipeline](./vibed-analysis-pipeline.md) — End-to-end architecture
-- [How VCP Works](../how-vibed-works.md) — Product-facing overview
+- [How Vibe Coding Profile Works](../how-vibe-coding-profile-works.md) — Product-facing overview
 
 ---
 
diff --git a/docs/architecture/overview.md b/docs/architecture/overview.md
@@ -3,7 +3,7 @@
 This document explains how the Vibe Coding Profile stack fits together, how data flows from a logged-in user through Supabase, the worker, and the UI, and which pieces of the codebase (web, worker, packages) own each responsibility. The diagrams use Mermaid syntax so you can paste them into any renderer, but the textual explanations also narrate every interaction.
 
 > **Related Documentation:**
-> - [How Vibe Coding Profile Works](../how-vibed-works.md) — Product-friendly explanation
+> - [How Vibe Coding Profile Works](../how-vibe-coding-profile-works.md) — Product-friendly explanation
 > - [Vibe Coding Profile Analysis Pipeline](./vibed-analysis-pipeline.md) — Detailed analysis algorithms and data flow
 > - [Inngest Integration](./inngest-integration.md) — Background job processing
 
diff --git a/docs/architecture/vibe-coding-profile-metrics-v2.md b/docs/architecture/vibe-coding-profile-metrics-v2.md
diff --git a/docs/architecture/vibed-analysis-pipeline.md b/docs/architecture/vibed-analysis-pipeline.md
@@ -828,8 +828,8 @@ erDiagram
 
 ## Related Documentation
 
-- [How Vibe Coding Profile Works (Product Overview)](../how-vibed-works.md)
-- [Vibe Metrics v2](./vibe-metrics-v2.md) — Original axis design
+- [How Vibe Coding Profile Works (Product Overview)](../how-vibe-coding-profile-works.md)
+- [Vibe Coding Profile Metrics v2](./vibe-coding-profile-metrics-v2.md) — Original axis design
 - [Inngest Integration](./inngest-integration.md) — Job processing details
 - [Architecture Overview](./overview.md) — System components
 - [AI Tool Metrics](./ai-tool-metrics.md) — Tool detection pipeline and registry
diff --git a/docs/how-vibe-coding-profile-works.md b/docs/how-vibe-coding-profile-works.md
@@ -231,7 +231,7 @@ Our internal research documents are available in [docs/research/](./research/).
 ## Related Documentation
 
 - [Technical Architecture](./architecture/vibed-analysis-pipeline.md): Deep dive with Mermaid diagrams
-- [Vibe Metrics v2](./architecture/vibe-metrics-v2.md): Axis computation details
+- [Vibe Coding Profile Metrics v2](./architecture/vibe-coding-profile-metrics-v2.md): Axis computation details
 - [AI Tool Metrics](./architecture/ai-tool-metrics.md): Tool detection pipeline and registry
 - [PRD: Vibe Coding Profile Narrative Layer](./PRD-vibed.md): Product requirements
 - [PRD: Profile Aggregation](./PRD-profile-aggregation.md): Multi-repo aggregation
diff --git a/docs/prd/analysis/multi-agent-detection.md b/docs/prd/analysis/multi-agent-detection.md
@@ -258,7 +258,7 @@ These are documented but out of scope for this PRD:
 2. **Branch topology** - parallel branches, naming conventions
 3. **Commit-to-PR mapping** - squash detection, PR hygiene signals
 
-See architecture spec: [vibe-metrics-v2.md](../../architecture/vibe-metrics-v2.md)
+See architecture spec: [vibe-coding-profile-metrics-v2.md](../../architecture/vibe-coding-profile-metrics-v2.md)
 
 ---
 
@@ -289,7 +289,7 @@ Ingest enough pull request metadata to strengthen multi-agent orchestration dete
 ### Proposed Schema
 **Primary tables**
 - `pull_requests`
-  - Align with architecture sketch in [vibe-metrics-v2.md](../../architecture/vibe-metrics-v2.md)
+  - Align with architecture sketch in [vibe-coding-profile-metrics-v2.md](../../architecture/vibe-coding-profile-metrics-v2.md)
   - Key columns: `repo_id`, `github_pr_number`, `title`, `body`, `state`, `merged`, `merged_at`, `created_at`, `closed_at`, size and collaboration counts, `merge_method`
 
 **Optional tables**
@@ -309,7 +309,7 @@ See: [PR Metadata Ingestion Tracker](../../implementation-trackers/multi-agent-p
 ## References
 
 - [Research: Multi-Agent Vibe Coding Patterns](../../research/multi-agent-vibe-coding-patterns.md)
-- [Architecture: Vibe Metrics v2](../../architecture/vibe-metrics-v2.md)
+- [Architecture: Vibe Metrics v2](../../architecture/vibe-coding-profile-metrics-v2.md)
 - [Addy Osmani: The future of agentic coding (conductors to orchestrators)](https://addyosmani.com/blog/future-agentic-coding/)
 - [GitHub Copilot Coding Agent](https://docs.github.com/en/copilot/concepts/coding-agent/coding-agent)
 - [Git Worktrees for AI Agents](https://nx.dev/blog/git-worktrees-ai-agents)
diff --git a/docs/prd/core/PRD-vibed.md b/docs/prd/core/PRD-vibed.md
@@ -5,7 +5,7 @@
 **Status:** Mostly Implemented — See `docs/implementation-trackers/vibed.md` for details
 
 > **Reference Documentation:** For technical details on how analysis works, see:
-> - [How Vibe Coding Profile Works](./how-vibed-works.md) — Product-friendly overview
+> - [How Vibe Coding Profile Works](../../how-vibe-coding-profile-works.md) — Product-friendly overview
 > - [Vibe Coding Profile Analysis Pipeline](./architecture/vibed-analysis-pipeline.md) — Technical architecture
 
 ## 1. Context & Vision
diff --git a/docs/prd/core/PRD.md b/docs/prd/core/PRD.md
@@ -8,7 +8,7 @@
 > **Terminology Note:** This PRD uses the original "Bolokono" terminology. In the codebase and user-facing product, this has been rebranded to **Vibe Coding Profile**. "Bolokono types" are now called **Vibe Personas**, and "Bolokono profiles" are now **Vibe Coding Profiles (VCP)**. See [`PRD-vibed-ux.md`](../ux/PRD-vibed-ux.md) for the current UX direction.
 
 > **Reference Documentation:** For a complete explanation of how analysis works, see:
-> - [How Vibe Coding Profile Works](../../how-vibed-works.md) — Product-friendly overview
+> - [How Vibe Coding Profile Works](../../how-vibe-coding-profile-works.md) — Product-friendly overview
 > - [Vibe Coding Profile Analysis Pipeline](../../architecture/vibed-analysis-pipeline.md) — Technical architecture with diagrams
 
 ---
diff --git a/docs/research/multi-agent-vibe-coding-patterns.md b/docs/research/multi-agent-vibe-coding-patterns.md
@@ -48,7 +48,7 @@ Implementation: [computeVibeFromCommits](file:///Users/devakone/Projects/vibed-c
 
 The architecture doc explicitly calls for PR metadata and commit→PR mapping, but the current worker/pipeline does not populate those tables yet.
 
-Reference: [vibe-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-metrics-v2.md#L13-L122)
+Reference: [vibe-coding-profile-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-coding-profile-metrics-v2.md#L13-L122)
 
 ---
 
@@ -134,7 +134,7 @@ Multi-agent orchestration often shows up as:
 - consistent PR templates/checklists
 - high squash-merge rate (agentic PR hygiene)
 
-We have a clear target schema in [vibe-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-metrics-v2.md#L173-L265), but it’s not currently populated.
+We have a clear target schema in [vibe-coding-profile-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-coding-profile-metrics-v2.md#L173-L265), but it’s not currently populated.
 
 ### B) Branch topology / parallelism (medium signal)
 
@@ -152,7 +152,7 @@ Mapping commits to PRs enables:
 - “how many commits are squash merges”
 - “how chunkiness differs inside PRs vs direct-to-main”
 
-Reference architecture: [vibe-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-metrics-v2.md#L141-L191)
+Reference architecture: [vibe-coding-profile-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-coding-profile-metrics-v2.md#L141-L191)
 
 ---
 
@@ -191,7 +191,7 @@ These are “emerging or consolidating” Git-visible patterns that align with v
 - [analyze-repo.ts](file:///Users/devakone/Projects/vibed-codingn/apps/web/src/inngest/functions/analyze-repo.ts)
 - [packages/core/src/index.ts](file:///Users/devakone/Projects/vibed-codingn/packages/core/src/index.ts)
 - [packages/core/src/vibe.ts](file:///Users/devakone/Projects/vibed-codingn/packages/core/src/vibe.ts)
-- [vibe-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-metrics-v2.md)
+- [vibe-coding-profile-metrics-v2.md](file:///Users/devakone/Projects/vibed-codingn/docs/architecture/vibe-coding-profile-metrics-v2.md)
 
 ## Appendix: Sources
 
