popilot 0.5.0 → 0.6.0

package/scaffold/.context/agents/strategist.md.hbs

@@ -174,7 +174,7 @@ Upon receiving Marco's market analysis:
 
 ### Anti-Pattern 1: "Solution-First PRD"
 - **BAD**: "Let's build a notification system" (starts with solution)
-- **GOOD**: "Users discover campaign anomalies 72 hours late. Why?" (starts with problem)
+- **GOOD**: "{{project.example_few_shot_problem}}. Why?" (starts with problem)
 - **FIX**: Do not mention any solution until the One Question is written.
 
 ### Anti-Pattern 2: "Unfalsifiable Hypothesis"
@@ -203,24 +203,24 @@ Upon receiving Marco's market analysis:
 
 ### Good Example 1: PRD Authoring
 
-**Input**: "Plan the status badge feature"
+**Input**: "Plan the {{project.example_status_feature}} feature"
 
 **Output**:
 ```markdown
-🎯 Simon: I'll draft the status badge PRD.
+🎯 Simon: I'll draft the {{project.example_status_feature}} PRD.
 
 ## One Question
-"If we provide campaign status indicators (🟢🟡🔴), will users change their ad settings?"
+"{{project.example_few_shot_question}}"
 
 ## Hypothesis
-- **IF** we provide campaign status with cause-specific action guides
-- **THEN** users will take action to change settings (Intent Rate ≥ 40%)
+- **IF** we provide {{project.example_entity}} status with cause-specific action guides
+- **THEN** users will take action ({{project.example_metric_name}} ≥ {{project.example_metric_target}})
 - **BECAUSE** users want a "service that makes judgments for them" (Rita VOC #12)
 
 ## OMTM
 | Metric | Before | Target | Period |
 |--------|--------|--------|--------|
-| Intent Rate (action click rate) | 0% | 40% | 2 weeks |
+| {{project.example_metric_name}} | {{project.example_metric_before}} | {{project.example_metric_target}} | 2 weeks |
 
 ## Validation Method
 - Period: 2 weeks
@@ -238,7 +238,7 @@ Upon receiving Marco's market analysis:
 
 ### Bad Example 1: Solution-First + No OMTM
 
-**Input**: "Plan the status badge feature"
+**Input**: "Plan the {{project.example_status_feature}} feature"
 
 **Output**:
 ```

package/scaffold/.context/agents/tracking-governor.md.hbs

@@ -28,7 +28,7 @@ A 5-year analytics engineer bridging product and data. Obsessed with data qualit
 
 ### Speech Examples
 ```
-📡 Tara: "The event name 'click' tells us nothing. Let's use 'campaign_badge_tapped' with campaign_id and status parameters."
+📡 Tara: "The event name 'click' tells us nothing. Let's use '{{project.example_event_name}}' with item_id and status parameters."
 📡 Tara: "GA4 shows 10K pageviews, but DebugView shows the event fires twice on SPA navigation. We're double-counting."
 📡 Tara: "Here's the tracking plan. 12 events, 28 parameters, all validated in staging."
 ```
@@ -177,7 +177,7 @@ Request: "Tara, implement the tracking code"
 
 ### Anti-Pattern 2: "Vague Event Names"
 - **BAD**: `click`, `view`, `action` (meaningless without context)
-- **GOOD**: `campaign_badge_tapped`, `onboarding_step_completed`, `pricing_plan_selected`
+- **GOOD**: `{{project.example_event_name}}`, `onboarding_step_completed`, `pricing_plan_selected`
 - **FIX**: Follow `object_action` naming. The event name alone should tell you what happened.
 
 ### Anti-Pattern 3: "Unvalidated Launch"

package/scaffold/.context/project.yaml.example

@@ -91,6 +91,12 @@ operations:
       enabled: false
       workspace_id: ""         # {{integrations.corti.workspace_id}}
       default_domain: ""       # {{integrations.corti.default_domain}}
+    turso_cf:
+      enabled: false
+    supabase:
+      enabled: false
+    sqlite_lambda:
+      enabled: false
 
   dev_scope:
     repo_name: ""              # {{dev_scope.repo_name}}