luna-agents 2.0.1

package/commands/ll-persona.md

@@ -0,0 +1,280 @@
+---
+name: ll-persona
+displayName: Luna Persona
+description: Generate detailed user personas from your app's code, data model, and user flows — with AI avatars, journey maps, and behavioral profiles
+version: 1.0.0
+category: strategy
+agent: luna-requirements-analyzer
+parameters:
+  - name: action
+    type: string
+    description: "Action: generate (create personas), analyze (profile real users), journey (map user journeys), interview (simulate user interviews), segment (cluster users), empathy (empathy maps)"
+    required: true
+    prompt: true
+  - name: source
+    type: string
+    description: "Source: auto (from codebase), data (from analytics), manual (you describe), url (analyze competitor users)"
+    required: false
+    default: auto
+mcp_servers:
+  - sequential-thinking
+  - memory
+  - fetch
+  - playwright
+  - zai-mcp-server
+  - stability-ai
+  - git
+  - elevenlabs
+  - notebooklm
+---
+
+# /persona — Know Your Users Before They Know Themselves
+
+Generate rich, data-driven user personas from your actual codebase. Luna reads your routes, features, auth flows, billing tiers, and data model to create personas that are grounded in what your product actually does — not marketing fiction.
+
+## What Luna Analyzes
+
+```
+/persona generate
+         │
+         ▼
+   READ YOUR CODEBASE
+   ├── Auth system → who can sign up? (email, OAuth, SSO)
+   ├── Billing tiers → what plan levels exist?
+   ├── RBAC/permissions → what roles exist? (admin, member, viewer)
+   ├── Features per tier → what's gated behind paid plans?
+   ├── API scopes → what integrations exist?
+   ├── Onboarding flow → what's the first-run experience?
+   ├── Dashboard layout → what metrics do users see?
+   ├── Settings page → what can users customize?
+   ├── Mobile app → is there a mobile experience?
+   └── Data model → what entities do users create/manage?
+         │
+         ▼
+   GENERATE PERSONAS (3-5 primary)
+   ├── Each persona includes:
+   │   ├── Name, age, role, company size
+   │   ├── AI-generated avatar photo (Stability AI)
+   │   ├── Goals and motivations
+   │   ├── Pain points and frustrations
+   │   ├── Technical proficiency level
+   │   ├── Features they use most
+   │   ├── Billing tier they're on
+   │   ├── Devices and platforms
+   │   ├── Key workflows (mapped to your actual routes)
+   │   ├── Objections before purchasing
+   │   ├── What makes them churn
+   │   └── Quotes (in their voice)
+   │
+   └── Persona types derived from YOUR product:
+       ├── Free tier explorer
+       ├── Pro power user
+       ├── Team admin/manager
+       ├── Enterprise decision maker
+       ├── Developer/API consumer
+       ├── Non-technical end user
+       └── (custom based on your roles/tiers)
+```
+
+## Actions
+
+### /persona generate
+```
+Creates 3-5 detailed personas:
+
+┌──────────────────────────────────────────┐
+│  👤 PERSONA 1: "Alex Chen"               │
+│  Role: Senior Full-Stack Developer        │
+│  Company: Series A startup (25 people)    │
+│  Plan: Pro ($29/mo)                       │
+│  Tech: React, Node, AWS → migrating to CF│
+│                                           │
+│  GOALS                                    │
+│  • Deploy AI agents without infra hassle  │
+│  • Automate code review and testing       │
+│  • Ship faster with small team            │
+│                                           │
+│  PAIN POINTS                              │
+│  • Current CI/CD too slow                 │
+│  • Manual deployment process error-prone  │
+│  • Can't afford dedicated DevOps hire     │
+│                                           │
+│  KEY WORKFLOWS                            │
+│  • /dashboard → /agents → /agents/studio  │
+│  • /dashboard/chains → /chains/builder    │
+│  • /dashboard/api-keys (uses API daily)   │
+│                                           │
+│  CHURN RISK                               │
+│  • If agent execution is unreliable       │
+│  • If pricing increases without warning   │
+│  • If competitors offer better CLI        │
+│                                           │
+│  QUOTE                                    │
+│  "I need something that just works. I     │
+│   don't have time to debug my tools."     │
+└──────────────────────────────────────────┘
+```
+
+### /persona analyze
+```
+Profile real users from analytics/data:
+├── Cluster users by behavior patterns
+├── Identify power users vs casual users
+├── Map feature adoption by segment
+├── Detect churn signals per persona
+├── Revenue concentration by persona type
+├── Support ticket patterns by persona
+└── Recommends product changes per segment
+```
+
+### /persona journey
+```
+User Journey Map (per persona):
+├── AWARENESS: How they discover your product
+│   ├── Search terms they'd use
+│   ├── Communities they're in
+│   └── Content that would attract them
+│
+├── CONSIDERATION: What they evaluate
+│   ├── Features they compare
+│   ├── Competitors they check
+│   ├── Pricing sensitivity
+│   └── Questions they'd ask
+│
+├── ONBOARDING: First 10 minutes
+│   ├── Signup friction points
+│   ├── Time to first value
+│   ├── "Aha moment" trigger
+│   └── Drop-off risk points
+│
+├── ACTIVATION: First week
+│   ├── Key actions that predict retention
+│   ├── Features they try first
+│   ├── Support needs
+│   └── Upgrade triggers
+│
+├── RETENTION: Ongoing usage
+│   ├── Daily/weekly workflows
+│   ├── Feature depth over time
+│   ├── Team expansion triggers
+│   └── Advocacy signals
+│
+└── EXPANSION: Growth
+    ├── Upgrade triggers
+    ├── Team invite patterns
+    ├── API integration depth
+    └── Referral likelihood
+```
+
+### /persona interview
+```
+Simulate user interviews with AI:
+├── Luna role-plays AS each persona
+├── You ask questions, persona responds in character
+├── Grounded in your actual product features
+├── Tests messaging, pricing, feature ideas
+├── Voice mode available (ElevenLabs — each persona has unique voice)
+├── Transcript saved for reference
+└── Insights extracted and summarized
+```
+
+### /persona segment
+```
+User Segmentation Analysis:
+├── Behavioral clusters (usage patterns)
+├── Value-based segments (revenue tiers)
+├── Engagement segments (active/at-risk/churned)
+├── Feature adoption segments
+├── Platform segments (web/mobile/API/CLI)
+├── Growth potential scoring
+└── Actionable recommendations per segment
+```
+
+### /persona empathy
+```
+Empathy Map (per persona):
+┌────────────────┬────────────────┐
+│   THINKS       │    FEELS       │
+│ "Is this worth │ Excited about  │
+│  the price?"   │ AI automation  │
+│ "Can my team   │ Anxious about  │
+│  adopt this?"  │ vendor lock-in │
+├────────────────┼────────────────┤
+│   SAYS         │    DOES        │
+│ "We need to    │ Compares 3     │
+│  ship faster"  │ tools before   │
+│ "Show me ROI"  │ committing     │
+│                │ Trials free    │
+│                │ tier first     │
+└────────────────┴────────────────┘
+```
+
+## Usage
+
+```bash
+/persona generate                                          # Auto from codebase
+/persona generate --source url https://competitor.com      # Competitor's users
+/persona analyze                                           # Profile real users
+/persona journey "Alex Chen"                               # Journey map for persona
+/persona interview                                         # Simulate user interviews
+/persona segment                                           # Cluster users
+/persona empathy "Alex Chen"                               # Empathy map
+```
+
+## In Pipes
+
+```bash
+# Product development informed by personas
+/pipe persona generate >> idea "solve their biggest pain" >> plan >> go *5
+
+# Marketing targeted by persona
+/pipe persona generate >> ghost blog "content for each persona" >> publish all
+
+# Pricing validation
+/pipe persona generate >> money >> persona interview "test pricing reactions"
+
+# Full product strategy
+/pipe compete "competitor.com" >> persona generate >> persona journey >> present "product strategy"
+
+# Onboarding optimization
+/pipe persona journey >> e2e-flow >> browser-test >> fix >> persona interview "test new onboarding"
+
+# Voice of customer
+/pipe persona interview >> voice podcast "user insights" >> publish notion
+
+# Feature prioritization
+/pipe persona segment >> persona empathy >> present "feature priorities" >> share team
+```
+
+## Output
+
+```
+.luna/{project}/personas/
+  personas.md                    # All personas in detail
+  avatars/                       # AI-generated avatar images
+    persona-1.png
+    persona-2.png
+  journeys/                      # Journey maps per persona
+    alex-chen-journey.md
+    sarah-kim-journey.md
+  segments/                      # Segmentation analysis
+    segments.json
+    segment-recommendations.md
+  interviews/                    # Simulated interview transcripts
+    alex-chen-interview.md
+  empathy-maps/                  # Empathy maps
+    alex-chen-empathy.md
+  summary.md                     # Executive summary
+```
+
+## What Makes This Different
+
+| Traditional Personas | Luna Personas |
+|---------------------|---------------|
+| Made up in a workshop | Generated from your actual code |
+| Based on assumptions | Based on your data model, roles, tiers |
+| Static document | Living — updates as your product evolves |
+| Text-only | AI avatars, voice simulations, journey maps |
+| Generic demographics | Mapped to your specific routes and features |
+| Can't validate | Simulate interviews to test ideas |
+| One-time exercise | `/persona generate` anytime product changes |

package/commands/ll-pipe.md

@@ -0,0 +1,296 @@
+---
+name: ll-pipe
+displayName: Luna Pipeline Runner
+description: Luna's AI programming language — combine commands with operators, variables, conditions, loops, and workflows
+version: 2.0.0
+category: workflow
+agent: luna-task-executor
+parameters:
+  - name: pipeline
+    type: string
+    description: Pipeline expression or saved workflow name
+    required: true
+    prompt: true
+workflow:
+  - parse_pipeline_expression
+  - resolve_variables_and_imports
+  - validate_commands
+  - execute_pipeline
+  - collect_results
+  - generate_pipeline_report
+output:
+  - .luna/{current-project}/pipeline-report.md
+prerequisites: []
+---
+
+# Luna Pipe — AI Programming Language
+
+Compose Luna commands into powerful pipelines with variables, conditions, loops, workflows, and more.
+
+**Every command in a pipe is a Luna command.**
+
+---
+
+## Operators
+
+### Flow Control
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `>>` | Sequential | `req >> des >> plan` |
+| `~~` | Parallel | `rev ~~ test ~~ sec` |
+| `( )` | Group | `(rev ~~ test) >> ship` |
+| `?>>` | If success | `test ?>> ship` |
+| `!>>` | If failure | `test !>> fix` |
+
+### Loops
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `*N` | Loop N times | `go *5` |
+| `*N?` | Loop up to N, stop on success | `(fix >> test) *3?` |
+| `*N!` | Loop up to N, stop on failure | `go *10!` |
+| `*?` | Loop until success (max 10) | `(fix >> test) *?` |
+
+### Hooks
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `@before:CMD` | Run before each step | `@before:rules` |
+| `@after:CMD` | Run after each step | `@after:test` |
+| `@each:CMD` | Before + after each step | `@each:rev` |
+
+### Variables
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `$name = CMD` | Capture output into variable | `$report = rev` |
+| `$name` | Use variable as input to next step | `fix $report` |
+| `$CMD.field` | Access output field | `$test.coverage` |
+
+### Conditionals
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `if COND >> CMD` | Run if condition true | `if $test.coverage < 90 >> fix` |
+| `else >> CMD` | Run if condition false | `else >> ship` |
+| `match VAR` | Switch on value | `match $env >> staging: ... >> prod: ...` |
+
+### Error Handling
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `try (CMDS)` | Try block | `try (go >> test >> ship)` |
+| `catch (CMDS)` | Run on error | `catch (rollback >> fix)` |
+| `finally (CMDS)` | Always run | `finally (docs >> changelog)` |
+
+### Assertions
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `assert COND` | Fail pipeline if false | `assert $test.coverage >= 90` |
+| `assert files.max_lines <= 100` | Check file constraints | `assert files.max_lines <= 100` |
+
+### Approval Gates
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `approve "MSG"` | Pause for user confirmation | `approve "Ship to prod?"` |
+
+### Context Blocks
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `with scope:NAME` | Set scope for block | `with scope:billing (go *3 >> test)` |
+| `with model:NAME` | Set AI model for block | `with model:opus (nexa review)` |
+
+### Multi-Repo
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `in REPO (CMDS)` | Run in specific repo | `in lunaos-engine (test >> ship)` |
+
+### Map/Reduce
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `map [ITEMS] >> CMD` | Apply to each item | `map [auth, billing, teams] >> (go >> test)` |
+| `reduce CMD` | Merge results | `reduce pr` |
+
+### Watch & Events
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `watch PATH >> CMD` | Run on file change | `watch src/ >> test` |
+| `on EVENT >> CMD` | Run on event | `on git:push >> (rev ~~ test) ?>> ship` |
+
+### Timing
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `timeout Nm CMD` | Timeout after N minutes | `timeout 5m (nexa review)` |
+| `retry N CMD` | Retry N times on failure | `retry 3 test` |
+
+### Snapshots
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `snapshot` | Checkpoint current state | `snapshot >> go *5` |
+| `diff` | Show changes since snapshot | `diff >> rev >> pr` |
+
+### Named Workflows
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `def NAME = PIPE` | Define reusable workflow | `def qg = (rev ~~ test ~~ sec)` |
+| `run NAME` | Execute saved workflow | `run qg ?>> ship` |
+| `import NAME` | Load from .luna/pipelines/ | `import team-pipeline` |
+
+### Logging
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `log "MSG"` | Log message to report | `log "Starting deploy"` |
+
+---
+
+## Complete Examples
+
+### Standard Dev Workflow
+```
+/pipe req >> des >> plan >> go *5 >> rev >> test >> ship
+```
+
+### Full Workflow with All Safety Nets
+```
+/pipe try (
+  req >> des >> plan >>
+  @before:rules @after:test go *5 >>
+  (rev ~~ sec ~~ a11y) >>
+  assert $test.coverage >= 90 >>
+  assert files.max_lines <= 100 >>
+  approve "Ship to production?" >>
+  ship >> watch
+) catch (
+  rollback >> fix >> test
+) finally (
+  docs >> changelog
+)
+```
+
+### Quality Gate with Variables
+```
+/pipe $result = (rev ~~ test ~~ sec) >>
+  if $result.pass >> ship >> docs
+  else >> fix >> test >> ship
+```
+
+### Named Workflows
+```
+/pipe def quality = (rev ~~ test ~~ sec ~~ a11y)
+/pipe def safe-ship = quality ?>> approve "Ship?" >> ship !>> fix >> quality
+
+/pipe go *5 >> run safe-ship >> docs >> changelog
+```
+
+### Multi-Repo Deploy
+```
+/pipe in lunaos-engine (test >> ship) ~~
+      in lunaos-dashboard (test >> ship) ~~
+      in lunaos-studio (test >> ship) >>
+  log "All services deployed"
+```
+
+### Map Across Features
+```
+/pipe map [auth, billing, teams, workflows] >> (
+  with scope:$item (go >> test >> rev)
+) >> reduce pr
+```
+
+### AI Autopilot with Assertions
+```
+/pipe search "auth patterns" >>
+  nexa review >>
+  lam "improve auth security" >>
+  test >>
+  assert $test.pass >>
+  assert $test.coverage >= 90 >>
+  rev >> pr
+```
+
+### Watch Mode (Continuous)
+```
+/pipe watch src/**/*.ts >> test >> rev
+```
+
+### Event-Driven
+```
+/pipe on git:push >> (rev ~~ test ~~ sec) ?>> ship !>> fix >> test
+/pipe on schedule:daily >> deps >> sec >> perf
+```
+
+### Retry with Timeout
+```
+/pipe timeout 10m (nexa review) >> retry 3 (test) >> ship
+```
+
+### Snapshot + Diff for Safe Refactoring
+```
+/pipe snapshot >> refactor *3 >> diff >> test >> rev >> pr
+```
+
+### Feature with Auto-Fix Loop
+```
+/pipe @before:rules feature "add billing page" >>
+  (rev ~~ test ~~ sec) ?>> pr
+  !>> (fix >> test) *3? >> pr
+```
+
+### Brand Launch Pipeline
+```
+/pipe brand >> auth >> hig >> a11y >>
+  test >> approve "Launch?" >>
+  ship >> docs >> changelog >>
+  log "Launched!"
+```
+
+---
+
+## Available Luna Commands
+
+**Workflow**: `req`, `des`, `plan`, `go`, `rev`, `test`, `ship`, `watch`, `retro`
+**Autopilot**: `feature`, `parallel`, `fix`, `debug`, `refactor`, `pr`
+**Quality**: `rules`, `perf`, `a11y`, `deps`, `mock`, `storybook`
+**Code Gen**: `auth`, `brand`, `api-client`, `migrate`, `i18n`, `ci`, `changelog`
+**DevOps**: `env`, `rollback`, `dock`, `cf`, `sec`
+**AI**: `nexa`, `lam`, `oh`, `chain`, `vision`, `search`, `q`
+**Tools**: `hig`, `ui`, `docs`, `cfg`
+
+---
+
+## Execution Rules
+
+1. All commands in a pipe are Luna commands (shortcuts or full names)
+2. `>>` sequential — next starts after previous completes
+3. `~~` parallel — all start simultaneously
+4. `()` groups — treated as single unit
+5. `?>>` / `!>>` — branch on success/failure
+6. `*N` loops — repeat N times with variants `*N?`, `*N!`, `*?`
+7. `@before` / `@after` / `@each` — hooks run on every step
+8. `$var` — capture and pass output between steps
+9. `if/else/match` — branch on conditions or values
+10. `try/catch/finally` — structured error handling
+11. `assert` — fail pipeline if condition not met
+12. `approve` — pause for human confirmation
+13. `with` — set context (scope, model) for a block
+14. `in` — target specific repo
+15. `map/reduce` — apply pipeline to list, merge results
+16. `watch/on` — reactive and event-driven execution
+17. `timeout/retry` — timing controls
+18. `snapshot/diff` — track changes across pipeline
+19. `def/run/import` — named reusable workflows
+20. `log` — pipeline logging
+21. Scope inheritance — all steps share project context
+22. Fail-fast by default — use `?>>` / `!>>` / `try` for control
+23. Report generated at `.luna/{project}/pipeline-report.md`