luna-agents 2.0.1

package/commands/ll-curb.md

@@ -0,0 +1,164 @@
+---
+name: ll-curb
+displayName: Luna Curb Writer
+description: Transform marketing copy into Curb Your Enthusiasm-style content — awkward, honest, slightly aggressive developer humor
+version: 1.0.0
+category: content
+agent: luna-documentation
+parameters:
+  - name: target
+    type: string
+    description: "What to rewrite: landing, pricing, readme, social, pitch, email, changelog, or a file path"
+    required: false
+    prompt: true
+  - name: tone
+    type: string
+    description: "Intensity: mild (witty), medium (sarcastic), hot (Larry David at his worst)"
+    required: false
+    default: medium
+mcp_servers:
+  - git
+  - fetch
+  - memory
+---
+
+# /curb — Curb Your Marketing
+
+Transform your product marketing into Curb Your Enthusiasm-style developer content. Awkward. Honest. Slightly aggressive. Surprisingly convincing.
+
+## Usage
+
+```bash
+/curb                          # Rewrite entire landing page
+/curb landing                  # Landing page copy
+/curb pricing                  # Pricing section
+/curb social                   # Generate 20 tweet-sized one-liners
+/curb readme                   # README with personality
+/curb pitch                    # Product Hunt / investor pitch
+/curb email "welcome series"   # Onboarding emails with tone
+/curb changelog                # Changelog that people actually read
+/curb src/components/Hero.tsx  # Rewrite a specific file's copy
+```
+
+## The Curb Voice Rules
+
+When generating content, follow these rules exactly:
+
+### Tone
+- **Petty frustration** about absurd industry norms (paying per minute, writing YAML to run tests, vendor lock-in)
+- **Escalating indignation** — start calm, build to "what are we DOING here?"
+- **Conversational rants** — talk directly at the reader like complaining to a friend at dinner
+- **Deadpan disbelief** — "So you're telling me..." / "Let me get this straight..."
+- **Awkward social moments** — the coworker stare, the DevOps guy going quiet
+
+### Format Rules
+- Never use hashtags or corporate speak
+- Keep tweets under 280 characters
+- The humor comes from the TRUTH — real developer pain, real pricing absurdity
+- End landing pages with passive-aggressive CTAs
+- Always contrast the absurd status quo with the obvious alternative
+
+### Structure for Landing Pages
+
+```
+HERO: Bold complaint disguised as a headline
+SUBHERO: The relatable rant (2-3 sentences, conversational)
+
+PROBLEM ("Let me ask you something..."):
+  - 3 rant cards (setup + punchline)
+  - 4 one-liner punches as border-left quotes
+  - The "invoice moment" — emotional turning point
+
+SOLUTION: State what it does in the most understated way possible
+  "PushCI.dev — run CI locally. That's it."
+
+COMPARISON: Honest table with uncomfortable truths
+  - Include "Emotional damage" as a real row
+  - Cloud CI column: sarcastic quotes
+  - Your product column: deadpan honesty
+
+SOCIAL PROOF (kind of):
+  - Fake-real testimonials that sound like therapy
+  - "I stopped paying for CI and nothing bad happened. That worried me."
+
+PRICING: One word. "Free."
+  - Then the passive-aggressive footnote
+
+CTA: "Or keep paying. That's fine. Totally fine."
+```
+
+### One-Liner Bank Template
+
+Generate 20 lines in these categories:
+
+**Existential (why does this exist):**
+- Pattern: "[absurd thing] + [deadpan reaction]"
+- Example: "I'm pushing code... why is there a meter running? What is this, a taxi?"
+
+**Comparative (us vs them):**
+- Pattern: "[their problem] vs [our non-problem]"
+- Example: "I had two problems: slow pipelines and expensive pipelines. Now I just have slow pipelines."
+
+**Observational (industry truths):**
+- Pattern: "The cloud is great... until [uncomfortable truth]"
+- Example: "You know what's scalable? Costs. Costs scale beautifully."
+
+**Self-deprecating (honest about our own product):**
+- Pattern: "[honest admission] + [but still better]"
+- Example: "PushCI.dev — it's not better... it's just not charging you. Which somehow makes it better."
+
+**Short punches (tweet-sized):**
+- Pattern: [4-8 words, no fluff]
+- "Stop renting your own CI."
+- "Run builds. Not up a bill."
+- "CI without invoices hits different."
+
+## Workflow
+
+### Step 1: Analyze the Project
+
+Read these files to understand the product:
+- `package.json`, `README.md`, `CLAUDE.md` — what it does
+- Landing page components — existing copy
+- Pricing data — what's free vs paid
+- Competitor comparison data — what to roast
+
+Extract:
+- Product name and what it replaces
+- Key value proposition (what's absurdly better)
+- Competitor pain points (what to make fun of)
+- Pricing advantage (the free angle)
+
+### Step 2: Generate Curb Content
+
+Based on the target, generate:
+
+**Landing page**: Full page rewrite with all sections above
+**Social**: 20 one-liners across all 5 categories
+**Pricing**: Curb-style pricing section with passive-aggressive CTAs
+**README**: Technical README but every section header is a complaint
+**Pitch**: Product Hunt description in "Larry David pitching a startup" voice
+**Email**: Onboarding sequence where each email gets progressively more honest
+**Changelog**: Version notes that read like therapy sessions
+
+### Step 3: Implement
+
+- Write the actual component code (React/TSX)
+- Maintain existing styling and framework
+- Keep the Curb tone in JSX string literals
+- Add a rotating quote ticker if applicable
+- Ensure all CTAs point to real URLs
+
+## Examples of Good Lines
+
+From the PushCI landing page (the original implementation):
+
+```
+"Build minutes? What is this, a gym membership?"
+"CI used to be a tool. Now it's a subscription. For what? For waiting?"
+"The cloud is great... until it starts acting like a landlord."
+"You know what's scalable? Costs. Costs scale beautifully."
+"I stopped paying for CI and nothing bad happened. That worried me."
+"You can keep paying for CI. I'm not judging. I am judging a little."
+"Emotional damage: High vs Still high, but free"
+```

package/commands/ll-debug.md

@@ -0,0 +1,76 @@
+---
+name: ll-debug
+displayName: Luna Debugger
+description: Systematic debugging — reproduce, hypothesize, instrument, test, narrow down with persistent state
+version: 1.0.0
+category: debugging
+agent: luna-code-review
+parameters:
+  - name: issue
+    type: string
+    description: Bug description, error message, or unexpected behavior
+    required: true
+    prompt: true
+  - name: scope
+    type: string
+    description: Project or feature scope
+    required: true
+    prompt: true
+workflow:
+  - reproduce_issue
+  - form_hypotheses
+  - instrument_code
+  - test_hypotheses
+  - narrow_root_cause
+  - persist_debug_state
+  - generate_debug_report
+output:
+  - .luna/{current-project}/debug-session.md
+prerequisites: []
+---
+
+# Luna Debugger
+
+Scientific debugging method with persistent state across context resets.
+
+## What This Command Does
+
+1. **Reproduce** — confirm the issue and document exact steps
+2. **Hypothesize** — list 3-5 possible root causes ranked by likelihood
+3. **Instrument** — add targeted logging/breakpoints to test hypotheses
+4. **Test** — run specific scenarios to confirm or eliminate each hypothesis
+5. **Narrow** — binary search through code flow to pinpoint root cause
+6. **Persist** — save debug state so you can resume after context resets
+7. **Report** — document findings, root cause, and suggested fix
+
+## Debug Protocol
+
+```
+Observe → Hypothesize → Predict → Test → Repeat
+    ↓
+Each iteration:
+  - Record what you tested
+  - Record what you learned
+  - Update hypothesis rankings
+  - Save state to debug-session.md
+```
+
+## Usage
+
+```
+/debug "API returns 500 on workflow creation with > 10 nodes"
+/debug "Dashboard shows stale data after team member removal"
+/debug "Playwright test flakes on CI but passes locally"
+```
+
+## State Persistence
+
+Debug state is saved to `.luna/{project}/debug-session.md` so you can:
+- Resume debugging after context window resets
+- Hand off to another developer with full context
+- Review the debugging process for learning
+
+## Differs from /fix
+
+- `/fix` — knows the bug, writes test, fixes it
+- `/debug` — doesn't know root cause, investigates systematically

package/commands/ll-deploy.md

@@ -0,0 +1,101 @@
+---
+name: ll-deploy
+displayName: Luna Deployment
+description: Deploy application to staging and production environments
+version: 1.0.0
+category: deployment
+agent: luna-deployment
+parameters:
+  - name: scope
+    type: string
+    description: Project or feature scope for deployment
+    required: true
+    prompt: true
+workflow:
+  - verify_deployment_readiness
+  - configure_infrastructure
+  - deploy_to_staging
+  - run_smoke_tests
+  - deploy_to_production
+  - generate_deployment_report
+output:
+  - .luna/{current-project}/deployment-report.md (project-level)
+  - .luna/{current-project}/{feature}/deployment-report.md (feature-level)
+prerequisites:
+  - .luna/{current-project}/implementation-plan.md
+  - .luna/{current-project}/code-review-report.md
+  - .luna/{current-project}/test-validation-report.md
+  - .luna/{current-project}/design.md
+  - all_tests_passing
+---
+
+# Luna Deployment
+
+Deploys your application to staging and production environments with comprehensive validation and reporting.
+
+## What This Command Does
+
+This command verifies deployment readiness, configures infrastructure, deploys to staging, runs smoke tests, deploys to production, and generates a detailed deployment report with all necessary information.
+
+## Prerequisites
+
+Requires in your current project:
+- `.luna/{current-project}/implementation-plan.md`
+- `.luna/{current-project}/code-review-report.md`
+- `.luna/{current-project}/test-validation-report.md`
+- `.luna/{current-project}/design.md`
+- All tests passing (from test validation report)
+
+If you're missing any prerequisites, complete the workflow:
+```bash
+/luna-requirements
+/luna-design
+/luna-plan
+/luna-execute  # Until all tasks complete
+/luna-review
+/luna-test
+```
+
+## Usage Instructions
+
+When you run this command, you'll be prompted for the scope:
+- Press **ENTER** for project-level deployment
+- Type **feature-name** to match your implementation scope
+
+## Execution Steps
+
+1. **Readiness Verification**: Verifies all prerequisites and deployment readiness
+2. **Infrastructure Configuration**: Sets up and configures deployment infrastructure
+3. **Staging Deployment**: Deploys application to staging environment
+4. **Smoke Testing**: Runs smoke tests to validate staging deployment
+5. **Production Deployment**: Deploys application to production environment
+6. **Report Generation**: Generates comprehensive deployment-report.md
+
+## Output Files
+
+Creates in your current project:
+- `.luna/{current-project}/deployment-report.md` for project-level deployment
+- `.luna/{current-project}/{feature}/deployment-report.md` for feature-level deployment
+
+The deployment report includes:
+- Deployment timeline with key milestones
+- Environment configuration details
+- Health check results for all deployed services
+- Performance validation metrics
+- Rollback plan and procedures
+- Access credentials and endpoints
+- Post-deployment verification results
+
+## Next Steps in Workflow
+
+After successful deployment, create documentation:
+```
+/luna-docs
+```
+
+## Tips
+
+- Ensure all tests pass before attempting deployment
+- Review the staging deployment results before production deployment
+- Keep the deployment report for future reference and audits
+- The rollback plan in the report helps you quickly recover from issues

package/commands/ll-deps.md

@@ -0,0 +1,70 @@
+---
+name: ll-deps
+displayName: Luna Dependency Audit
+description: Audit dependencies — outdated packages, vulnerabilities, unused deps, license check, upgrade plan
+version: 1.0.0
+category: quality
+agent: luna-code-review
+parameters:
+  - name: action
+    type: string
+    description: Action (audit, update, cleanup, licenses, all)
+    required: false
+    prompt: true
+  - name: scope
+    type: string
+    description: Project or feature scope
+    required: true
+    prompt: true
+workflow:
+  - scan_dependencies
+  - check_vulnerabilities
+  - find_unused_deps
+  - check_outdated
+  - audit_licenses
+  - generate_upgrade_plan
+  - generate_deps_report
+output:
+  - .luna/{current-project}/deps-report.md
+prerequisites: []
+---
+
+# Luna Dependency Audit
+
+Keep dependencies secure, current, and minimal.
+
+## What This Command Does
+
+1. **Scan** — reads package.json, lock files, and import statements
+2. **Vulnerabilities** — checks for known CVEs (npm audit + Snyk DB)
+3. **Unused** — finds installed packages not imported anywhere
+4. **Outdated** — lists packages with available updates
+5. **Licenses** — checks for incompatible licenses (GPL in MIT project)
+6. **Upgrade Plan** — prioritized list of safe upgrades with breaking change notes
+7. **Report** — full dependency health scorecard
+
+## Actions
+
+| Action | What It Does |
+|--------|-------------|
+| `audit` | Vulnerability scan |
+| `update` | Show available updates with risk level |
+| `cleanup` | Find and remove unused dependencies |
+| `licenses` | License compatibility check |
+| `all` | Everything above |
+
+## Usage
+
+```
+/deps                   # Full audit
+/deps audit             # Vulnerabilities only
+/deps cleanup           # Remove unused
+/deps licenses          # License check
+```
+
+## Risk Levels
+
+- **Safe** — patch update, no breaking changes
+- **Low** — minor update, new features only
+- **Medium** — major update, has migration guide
+- **High** — major update, significant breaking changes

package/commands/ll-design.md

@@ -0,0 +1,86 @@
+---
+name: ll-design
+displayName: Luna Design Architecture
+description: Transform requirements into comprehensive technical design specification
+version: 1.0.0
+category: design
+agent: luna-design-architect
+parameters:
+  - name: scope
+    type: string
+    description: Project or feature scope for design
+    required: true
+    prompt: true
+workflow:
+  - read_requirements_document
+  - design_system_architecture
+  - create_component_specifications
+  - define_data_models_api_endpoints
+  - generate_design_document
+output:
+  - .luna/{current-project}/design.md (project-level)
+  - .luna/{current-project}/{feature}/design.md (feature-level)
+prerequisites:
+  - .luna/{current-project}/requirements.md
+---
+
+# Luna Design Architecture
+
+Transforms your requirements into comprehensive technical design specifications with implementation guidelines.
+
+## What This Command Does
+
+This command reads your requirements document and creates a detailed technical design including system architecture, component specifications, data models, API endpoints, and implementation guidelines.
+
+## Prerequisites
+
+Requires in your current project:
+- `.luna/{current-project}/requirements.md`
+
+If you don't have requirements yet, run:
+```
+/luna-requirements
+```
+
+## Usage Instructions
+
+When you run this command, you'll be prompted for the scope:
+- Press **ENTER** for project-level design
+- Type **feature-name** to match your requirements scope
+
+## Execution Steps
+
+1. **Requirements Analysis**: Reads and analyzes the requirements.md from your project
+2. **Architecture Design**: Designs comprehensive system architecture
+3. **Component Specification**: Creates detailed component specifications
+4. **Data Modeling**: Defines data models and API endpoints
+5. **Design Generation**: Generates design.md with implementation guidelines
+
+## Output Files
+
+Creates in your current project:
+- `.luna/{current-project}/design.md` for project-level design
+- `.luna/{current-project}/{feature}/design.md` for feature-level design
+
+The design document includes:
+- System architecture diagrams
+- Component specifications and responsibilities
+- Data models and relationships
+- API endpoint specifications
+- Technology stack recommendations
+- Implementation guidelines and best practices
+
+## Next Steps in Workflow
+
+After design is complete, proceed with:
+```
+/luna-plan
+```
+
+This will break down your design into ordered, actionable implementation tasks.
+
+## Tips
+
+- Ensure your requirements document is complete before running this command
+- Review the generated architecture for scalability and maintainability
+- Consider your team's technical expertise when reviewing technology choices

package/commands/ll-devto-publish.md

@@ -0,0 +1,172 @@
+---
+name: ll-devto-publish
+displayName: Luna Dev.to Publisher
+description: Write and publish Dev.to articles about any project — with comedy styles (Curb, Seinfeld, The Office, Silicon Valley) or straight technical. Auto-publishes via API.
+version: 1.0.0
+category: deployment
+agent: luna-seo
+parameters:
+  - name: product_name
+    type: string
+    description: "Product name"
+    required: true
+    prompt: true
+  - name: domain
+    type: string
+    description: "Product URL"
+    required: true
+    prompt: true
+  - name: style
+    type: string
+    description: "Style: curb (Curb Your Enthusiasm), seinfeld (observational), office (Michael Scott), silicon-valley (tech satire), straight (no comedy), absurd (surreal humor)"
+    required: false
+    default: curb
+  - name: topic
+    type: string
+    description: "What the article is about (e.g., 'why our tool is better than GitHub Actions')"
+    required: true
+    prompt: true
+  - name: publish
+    type: boolean
+    description: "Auto-publish to Dev.to (requires DEV_TO_API_KEY in .env)"
+    required: false
+    default: true
+workflow:
+  - analyze_project
+  - generate_article_in_style
+  - review_and_refine
+  - publish_to_devto
+  - generate_social_snippets
+output:
+  - docs/launch/DEVTO_{topic}.md
+  - .luna/{current-project}/devto-publish-report.md
+mcp_servers:
+  - git
+  - fetch
+---
+
+# /devto-publish — Write & Ship Dev.to Articles
+
+Write technical articles with personality. Auto-publish to Dev.to via API.
+
+## Comedy Styles
+
+### Curb Your Enthusiasm (`--style curb`)
+Petty frustration about absurd industry norms. Escalating indignation. Deadpan disbelief.
+
+> "So I'm looking at our GitHub Actions bill and I go — wait. We're paying... to LINT? We're paying someone to run eslint? I could run eslint. My toaster could run eslint."
+
+> "Let me get this straight. You WROTE a config file. To TELL a computer. To run a TEST. That YOUR computer could run. For FREE."
+
+**Tone rules:**
+- Start calm, build to "what are we DOING here?"
+- Talk directly at the reader like complaining at dinner
+- "So you're telling me..." / "Let me get this straight..."
+- The awkward silence moment when the DevOps guy realizes
+- Always end with the product URL, never hashtags
+
+### Seinfeld (`--style seinfeld`)
+Observational comedy about everyday developer absurdity. "What's the deal with..."
+
+> "What's the DEAL with YAML? It's not markup. It's not code. It's this weird in-between thing where one wrong space and your entire pipeline explodes. It's like the metric system of configuration."
+
+> "You ever notice how setting up CI/CD takes longer than writing the actual code? That's like spending more time building the mailbox than writing the letter."
+
+**Tone rules:**
+- "What's the deal with [industry norm]?"
+- Observational comparisons to everyday life
+- Pop-out bits — "Not that there's anything wrong with Jenkins..."
+- Jerry's incredulous tone when describing the obvious
+
+### The Office (`--style office`)
+Michael Scott energy. Confident ignorance. Cringe comedy.
+
+> "Would I rather have working CI/CD or a pizza party? Trick question. PushCI gives you both because you save so much money on your CI bill you can afford a pizza party every day. — Michael Scott"
+
+> "I'm not superstitious. But I am a little stitious. About YAML. Every time I write a YAML file, something bad happens. That's just science."
+
+**Tone rules:**
+- Michael Scott quotes (real or fabricated)
+- "That's what she said" energy (keep it clean)
+- Dwight-level obsession with the technical details
+- Jim's deadpan camera look when something absurd happens
+- Conference room meeting vibes
+
+### Silicon Valley (`--style silicon-valley`)
+Tech startup satire. Disruption theater. VC-speak.
+
+> "We're not building CI/CD. We're building an AI-native infrastructure consciousness layer that democratizes developer velocity across the entire compute spectrum. Also it runs npm test. For free."
+
+> "Our TAM is literally every developer who has ever written a YAML file and felt their soul leave their body. That's a $14 billion market."
+
+**Tone rules:**
+- Buzzword overload that circles back to something simple
+- "We're making the world a better place" but for CI/CD
+- Erlich Bachman confidence with Richard Hendricks reality
+- Jian-Yang energy: "It's like GitHub Actions... but for your machine"
+
+### Straight Technical (`--style straight`)
+No comedy. Clean, authoritative technical writing.
+
+**Tone rules:**
+- Problem → Solution → Comparison → How to try
+- Feature tables, code examples, benchmarks
+- Professional but not boring
+
+### Absurd (`--style absurd`)
+Surreal humor. Monty Python meets tech.
+
+> "In a world where developers spend more time configuring CI/CD than actual development, one tool dared to ask: what if we just... didn't? What if the computer figured it out itself? Critics called it 'lazy.' We call it 'AI.'"
+
+**Tone rules:**
+- Dramatic movie trailer narration for mundane things
+- Personifying config files and pipelines
+- Unexpected philosophical tangents
+- "Brought to you by the letters Y, A, M, and L"
+
+## Auto-Publish
+
+Set `DEV_TO_API_KEY` in your `.env` file. Get one at https://dev.to/settings/extensions
+
+The skill will:
+1. Generate the article in your chosen style
+2. Publish it to Dev.to via API
+3. Return the published URL
+4. Generate social media snippets for Twitter/LinkedIn
+
+## Examples
+
+```bash
+# Curb style about your CI/CD tool
+/devto-publish --product_name PushCI --domain pushci.dev \
+  --style curb --topic "why YAML is dead"
+
+# Seinfeld style about your database tool
+/devto-publish --product_name MyDB --domain mydb.io \
+  --style seinfeld --topic "what's the deal with database migrations"
+
+# The Office style product launch
+/devto-publish --product_name TeamApp --domain teamapp.com \
+  --style office --topic "we built a project management tool"
+
+# Silicon Valley VC pitch energy
+/devto-publish --product_name CloudThing --domain cloudthing.io \
+  --style silicon-valley --topic "disrupting the monitoring space"
+
+# Straight technical comparison
+/devto-publish --product_name MyTool --domain mytool.dev \
+  --style straight --topic "comparing MyTool vs Datadog"
+
+# Just generate, don't publish
+/devto-publish --product_name MyApp --domain myapp.com \
+  --style curb --topic "why our tool exists" --publish false
+```
+
+## Vibe-Coding Era Energy
+
+All comedy styles lean into the vibe-coding reality:
+- Nobody writes code anymore, AI does
+- But we're still writing YAML configs by hand??
+- The cognitive dissonance of 2026 dev workflows
+- Claude builds your app but you manually configure CI
+- "The AI writes your code. YOU write the YAML that tests it."