vibe-me 2.0.0 → 3.0.0

package/templates/metrics.md

@@ -0,0 +1,35 @@
+# Metrics
+
+<!-- 
+  INSTRUCTIONS FOR AI AGENT:
+  What numbers matter for this project? Not vanity metrics — the numbers 
+  that actually drive decisions.
+  
+  If this is not a product/business (it's a library or open-source tool), 
+  the relevant metrics might be: downloads, GitHub stars, open issues, 
+  contributor count, test coverage, build time. Adapt accordingly.
+  Delete these instruction comments when done.
+-->
+
+## North Star Metric
+
+<!-- The ONE number that best captures whether this project is succeeding. -->
+<!-- Example: "Weekly active users who complete at least one document" -->
+
+## Key Metrics
+
+| Metric | Current | Target | Why It Matters |
+|---|---|---|---|
+| | | | |
+
+## What We Track
+
+<!-- Where is data collected? Analytics tools, dashboards, manual tracking? -->
+
+- 
+
+## What We Don't Track (But Should)
+
+<!-- Gaps in measurement. Things we wish we knew but don't. -->
+
+- 

package/templates/product.md

@@ -0,0 +1,54 @@
+# Product
+
+<!-- 
+  INSTRUCTIONS FOR AI AGENT:
+  This captures the PRODUCT layer — not what the code does, but what 
+  the product is, why people use it, and what drives retention.
+  
+  If this is NOT a product (it's a library, CLI tool, internal infrastructure, 
+  or open-source utility), write:
+  "N/A — This is a [library/tool/etc], not a user-facing product."
+  Then briefly describe who integrates with it and why, and move on.
+  Do NOT delete this file — its absence vs presence signals project type.
+  Delete these instruction comments when done.
+-->
+
+## Product Vision
+
+<!-- One paragraph. What does the world look like if this product succeeds? -->
+
+## Value Proposition
+
+<!-- Why would someone choose THIS over alternatives? What's the unfair advantage? -->
+
+## What Drives Signups
+
+<!-- Why do new users show up? What pain brought them here? -->
+
+- 
+
+## What Drives Retention
+
+<!-- Why do users stay? What becomes indispensable? -->
+
+- 
+
+## What Nobody Uses
+
+<!-- Features that exist but get ignored. Candidates for removal or redesign. -->
+
+- 
+
+## Where Users Get Confused
+
+<!-- Friction points. Where do users drop off, get stuck, or contact support? -->
+
+- 
+
+## Feature Priorities
+
+<!-- What should be built next, and WHY (tied to a user problem, not a feature wish) -->
+
+| Priority | Feature | User Problem It Solves |
+|---|---|---|
+| | | |

package/templates/risks.md

@@ -0,0 +1,44 @@
+# Risks
+
+<!-- 
+  INSTRUCTIONS FOR AI AGENT:
+  Every project has risks. Technical, legal, market, operational.
+  Be honest. This file is for internal awareness, not external marketing.
+  
+  If this is a low-stakes side project, the risks might just be:
+  "Risk of abandonment — no external users depend on this."
+  That's fine. Still document it.
+  Delete these instruction comments when done.
+-->
+
+## Technical Risks
+
+<!-- What could break in ways that are hard to fix? -->
+
+| Risk | Likelihood | Impact | Mitigation |
+|---|---|---|---|
+| | | | |
+
+## Legal / Compliance Risks
+
+<!-- Licensing issues, data privacy, regulatory requirements -->
+
+- 
+
+## Market Risks
+
+<!-- Competition, timing, platform dependency -->
+
+- 
+
+## Operational Risks
+
+<!-- Bus factor, key dependencies on one person, vendor lock-in -->
+
+- 
+
+## Security Risks
+
+<!-- Known attack vectors, unpatched vulnerabilities, data exposure -->
+
+- 

package/templates/users.md

@@ -0,0 +1,47 @@
+# Users
+
+<!-- 
+  INSTRUCTIONS FOR AI AGENT:
+  This captures the EMOTIONAL REALITY of users — not just what they do,
+  but how they feel, what scares them, what confuses them, what they want.
+  
+  If this project has no end users (it's a library or internal tool), write:
+  "N/A — This is a [library/tool]. Consumers are developers integrating via API/package."
+  Then describe the developer persona instead.
+  Delete these instruction comments when done.
+-->
+
+## Personas
+
+<!-- Who are the real humans using this? Be specific. Not "users" — who? -->
+
+### [Persona Name]
+- **Who:** [Role, experience level, context]
+- **Goal:** [What they're trying to accomplish]
+- **Frustration:** [What makes their current situation painful]
+- **Fear:** [What are they worried might go wrong]
+- **Technical Comfort:** [How tech-savvy are they]
+
+---
+
+<!-- Copy for each persona. Most products have 2-4. -->
+
+## Emotional Reality
+
+<!-- How do users FEEL when they use this? What emotional states drive their behavior? -->
+<!-- Example: "Users are scared. They don't trust AI with legal documents." -->
+<!-- Example: "Users are in a hurry. They need results in under 30 seconds." -->
+
+- 
+
+## Common Objections
+
+<!-- What stops someone from signing up, paying, or trusting the product? -->
+
+- 
+
+## What Users Say (Verbatim)
+
+<!-- Real quotes from users, support tickets, reviews. The raw voice of the customer. -->
+
+-