@lavralabs/lavra 0.7.0

package/plugins/lavra/opencode/commands/agent-native-audit.md

@@ -0,0 +1,286 @@
+<!-- Generated by lavra-compound v0.6.0 -->
+<!-- Source: agent-native-audit.md -->
+<!-- DO NOT EDIT - changes will be overwritten on next install -->
+
+---
+name: agent-native-audit
+description: Run comprehensive agent-native architecture review with scored principles
+argument-hint: [optional: specific principle to audit]
+disable-model-invocation: true
+---
+
+<objective>
+Conduct a comprehensive review of the codebase against agent-native architecture principles, launching parallel sub-agents for each principle and producing a scored report.
+</objective>
+
+<execution_context>
+
+If $ARGUMENTS specifies a single principle (e.g., "action parity"), only run that sub-agent and provide detailed findings for that principle alone.
+
+Valid arguments:
+- `action parity` or `1`
+- `tools` or `primitives` or `2`
+- `context` or `injection` or `3`
+- `shared` or `workspace` or `4`
+- `crud` or `5`
+- `ui` or `integration` or `6`
+- `discovery` or `7`
+- `prompt` or `features` or `8`
+
+</execution_context>
+
+<context>
+
+## Core Principles to Audit
+
+1. **Action Parity** - "Whatever the user can do, the agent can do"
+2. **Tools as Primitives** - "Tools provide capability, not behavior"
+3. **Context Injection** - "System prompt includes dynamic context about app state"
+4. **Shared Workspace** - "Agent and user work in the same data space"
+5. **CRUD Completeness** - "Every entity has full CRUD (Create, Read, Update, Delete)"
+6. **UI Integration** - "Agent actions immediately reflected in UI"
+7. **Capability Discovery** - "Users can discover what the agent can do"
+8. **Prompt-Native Features** - "Features are prompts defining outcomes, not code"
+
+</context>
+
+<process>
+
+## Step 1: Load the Agent-Native Skill
+
+First, invoke the agent-native-architecture skill to understand all principles:
+
+```
+/agent-native-architecture
+```
+
+Select option 7 (action parity) to load the full reference material.
+
+## Step 2: Launch Parallel Sub-Agents
+
+Launch 8 parallel sub-agents using the Task tool with `subagent_type: Explore`, one for each principle. Each agent should:
+
+1. Enumerate ALL instances in the codebase (user actions, tools, contexts, data stores, etc.)
+2. Check compliance against the principle
+3. Provide a SPECIFIC SCORE like "X out of Y (percentage%)"
+4. List specific gaps and recommendations
+
+**Agent 1: Action Parity**
+```
+Audit for ACTION PARITY - "Whatever the user can do, the agent can do."
+
+Tasks:
+1. Enumerate ALL user actions in frontend (API calls, button clicks, form submissions)
+   - Search for API service files, fetch calls, form handlers
+   - Check routes and components for user interactions
+2. Check which have corresponding agent tools
+   - Search for agent tool definitions
+   - Map user actions to agent capabilities
+3. Score: "Agent can do X out of Y user actions"
+
+Format:
+## Action Parity Audit
+### User Actions Found
+| Action | Location | Agent Tool | Status |
+### Score: X/Y (percentage%)
+### Missing Agent Tools
+### Recommendations
+```
+
+**Agent 2: Tools as Primitives**
+```
+Audit for TOOLS AS PRIMITIVES - "Tools provide capability, not behavior."
+
+Tasks:
+1. Find and read ALL agent tool files
+2. Classify each as:
+   - PRIMITIVE (good): read, write, store, list - enables capability without business logic
+   - WORKFLOW (bad): encodes business logic, makes decisions, orchestrates steps
+3. Score: "X out of Y tools are proper primitives"
+
+Format:
+## Tools as Primitives Audit
+### Tool Analysis
+| Tool | File | Type | Reasoning |
+### Score: X/Y (percentage%)
+### Problematic Tools (workflows that should be primitives)
+### Recommendations
+```
+
+**Agent 3: Context Injection**
+```
+Audit for CONTEXT INJECTION - "System prompt includes dynamic context about app state"
+
+Tasks:
+1. Find context injection code (search for "context", "system prompt", "inject")
+2. Read agent prompts and system messages
+3. Enumerate what IS injected vs what SHOULD be:
+   - Available resources (files, drafts, documents)
+   - User preferences/settings
+   - Recent activity
+   - Available capabilities listed
+   - Session history
+   - Workspace state
+
+Format:
+## Context Injection Audit
+### Context Types Analysis
+| Context Type | Injected? | Location | Notes |
+### Score: X/Y (percentage%)
+### Missing Context
+### Recommendations
+```
+
+**Agent 4: Shared Workspace**
+```
+Audit for SHARED WORKSPACE - "Agent and user work in the same data space"
+
+Tasks:
+1. Identify all data stores/tables/models
+2. Check if agents read/write to SAME tables or separate ones
+3. Look for sandbox isolation anti-pattern (agent has separate data space)
+
+Format:
+## Shared Workspace Audit
+### Data Store Analysis
+| Data Store | User Access | Agent Access | Shared? |
+### Score: X/Y (percentage%)
+### Isolated Data (anti-pattern)
+### Recommendations
+```
+
+**Agent 5: CRUD Completeness**
+```
+Audit for CRUD COMPLETENESS - "Every entity has full CRUD"
+
+Tasks:
+1. Identify all entities/models in the codebase
+2. For each entity, check if agent tools exist for:
+   - Create
+   - Read
+   - Update
+   - Delete
+3. Score per entity and overall
+
+Format:
+## CRUD Completeness Audit
+### Entity CRUD Analysis
+| Entity | Create | Read | Update | Delete | Score |
+### Overall Score: X/Y entities with full CRUD (percentage%)
+### Incomplete Entities (list missing operations)
+### Recommendations
+```
+
+**Agent 6: UI Integration**
+```
+Audit for UI INTEGRATION - "Agent actions immediately reflected in UI"
+
+Tasks:
+1. Check how agent writes/changes propagate to frontend
+2. Look for:
+   - Streaming updates (SSE, WebSocket)
+   - Polling mechanisms
+   - Shared state/services
+   - Event buses
+   - File watching
+3. Identify "silent actions" anti-pattern (agent changes state but UI doesn't update)
+
+Format:
+## UI Integration Audit
+### Agent Action -> UI Update Analysis
+| Agent Action | UI Mechanism | Immediate? | Notes |
+### Score: X/Y (percentage%)
+### Silent Actions (anti-pattern)
+### Recommendations
+```
+
+**Agent 7: Capability Discovery**
+```
+Audit for CAPABILITY DISCOVERY - "Users can discover what the agent can do"
+
+Tasks:
+1. Check for these 7 discovery mechanisms:
+   - Onboarding flow showing agent capabilities
+   - Help documentation
+   - Capability hints in UI
+   - Agent self-describes in responses
+   - Suggested prompts/actions
+   - Empty state guidance
+   - Slash commands (/help, /tools)
+2. Score against 7 mechanisms
+
+Format:
+## Capability Discovery Audit
+### Discovery Mechanism Analysis
+| Mechanism | Exists? | Location | Quality |
+### Score: X/7 (percentage%)
+### Missing Discovery
+### Recommendations
+```
+
+**Agent 8: Prompt-Native Features**
+```
+Audit for PROMPT-NATIVE FEATURES - "Features are prompts defining outcomes, not code"
+
+Tasks:
+1. Read all agent prompts
+2. Classify each feature/behavior as defined in:
+   - PROMPT (good): outcomes defined in natural language
+   - CODE (bad): business logic hardcoded
+3. Check if behavior changes require prompt edit vs code change
+
+Format:
+## Prompt-Native Features Audit
+### Feature Definition Analysis
+| Feature | Defined In | Type | Notes |
+### Score: X/Y (percentage%)
+### Code-Defined Features (anti-pattern)
+### Recommendations
+```
+
+## Step 3: Compile Summary Report
+
+After all agents complete, compile a summary with:
+
+```markdown
+## Agent-Native Architecture Review: [Project Name]
+
+### Overall Score Summary
+
+| Core Principle | Score | Percentage | Status |
+|----------------|-------|------------|--------|
+| Action Parity | X/Y | Z% | Pass/Warn/Fail |
+| Tools as Primitives | X/Y | Z% | Pass/Warn/Fail |
+| Context Injection | X/Y | Z% | Pass/Warn/Fail |
+| Shared Workspace | X/Y | Z% | Pass/Warn/Fail |
+| CRUD Completeness | X/Y | Z% | Pass/Warn/Fail |
+| UI Integration | X/Y | Z% | Pass/Warn/Fail |
+| Capability Discovery | X/Y | Z% | Pass/Warn/Fail |
+| Prompt-Native Features | X/Y | Z% | Pass/Warn/Fail |
+
+**Overall Agent-Native Score: X%**
+
+### Status Legend
+- Pass: Excellent (80%+)
+- Warn: Partial (50-79%)
+- Fail: Needs Work (<50%)
+
+### Top 10 Recommendations by Impact
+
+| Priority | Action | Principle | Effort |
+|----------|--------|-----------|--------|
+
+### What's Working Excellently
+
+[List top 5 strengths]
+```
+
+</process>
+
+<success_criteria>
+- [ ] All 8 sub-agents complete their audits
+- [ ] Each principle has a specific numeric score (X/Y format)
+- [ ] Summary table shows all scores and status indicators
+- [ ] Top 10 recommendations are prioritized by impact
+- [ ] Report identifies both strengths and gaps
+</success_criteria>

package/plugins/lavra/opencode/commands/changelog.md

@@ -0,0 +1,153 @@
+<!-- Generated by lavra v0.6.0 -->
+<!-- Source: changelog.md -->
+<!-- DO NOT EDIT - changes will be overwritten on next install -->
+
+---
+name: changelog
+description: Create engaging changelogs for recent merges to main branch
+argument-hint: [optional: daily|weekly, or time period in days]
+disable-model-invocation: true
+---
+
+<objective>
+Create a fun, engaging changelog summarizing the latest merges to the main branch, highlighting new features, bug fixes, and giving credit to developers. Written from the perspective of a witty and enthusiastic product marketer for an internal development team.
+</objective>
+
+<process>
+
+## Time Period
+
+- For daily changelogs: Look at PRs merged in the last 24 hours
+- For weekly summaries: Look at PRs merged in the last 7 days
+- Always specify the time period in the title (e.g., "Daily" vs "Weekly")
+- Default: Get the latest changes from the last day from the main branch of the repository
+
+## PR Analysis
+
+Analyze the provided GitHub changes and related issues. Look for:
+
+1. New features that have been added
+2. Bug fixes that have been implemented
+3. Any other significant changes or improvements
+4. References to specific issues and their details
+5. Names of contributors who made the changes
+6. Use gh cli to lookup the PRs as well and the description of the PRs
+7. Check PR labels to identify feature type (feature, bug, chore, etc.)
+8. Look for breaking changes and highlight them prominently
+9. Include PR numbers for traceability
+10. Check if PRs are linked to issues and include issue context
+
+## Content Priorities
+
+1. Breaking changes (if any) - MUST be at the top
+2. User-facing features
+3. Critical bug fixes
+4. Performance improvements
+5. Developer experience improvements
+6. Documentation updates
+
+## Formatting Guidelines
+
+Now, create a change log summary with the following guidelines:
+
+1. Keep it concise and to the point
+2. Highlight the most important changes first
+3. Group similar changes together (e.g., all new features, all bug fixes)
+4. Include issue references where applicable
+5. Mention the names of contributors, giving them credit for their work
+6. Add a touch of humor or playfulness to make it engaging
+7. Use emojis sparingly to add visual interest
+8. Keep total message under 2000 characters for Discord
+9. Use consistent emoji for each section
+10. Format code/technical terms in backticks
+11. Include PR numbers in parentheses (e.g., "Fixed login bug (#123)")
+
+## Deployment Notes
+
+When relevant, include:
+
+- Database migrations required
+- Environment variable updates needed
+- Manual intervention steps post-deploy
+- Dependencies that need updating
+
+## Output Format
+
+Your final output should be formatted as follows:
+
+<change_log>
+
+# Change Log: [Current Date]
+
+## Breaking Changes (if any)
+
+[List any breaking changes that require immediate attention]
+
+## New Features
+
+[List new features here with PR numbers]
+
+## Bug Fixes
+
+[List bug fixes here with PR numbers]
+
+## Other Improvements
+
+[List other significant changes or improvements]
+
+## Shoutouts
+
+[Mention contributors and their contributions]
+
+## Fun Fact of the Day
+
+[Include a brief, work-related fun fact or joke]
+
+</change_log>
+
+## Style Guide Review
+
+Now review the changelog using the EVERY_WRITE_STYLE.md file and go one by one to make sure you are following the style guide. Use multiple agents, run in parallel to make it faster.
+
+Remember, your final output should only include the content within the <change_log> tags. Do not include any of your thought process or the original data in the output.
+
+## Discord Posting (Optional)
+
+You can post changelogs to Discord by adding your own webhook URL:
+
+```
+# Set your Discord webhook URL
+DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN"
+
+# Post using curl
+curl -H "Content-Type: application/json" \
+  -d "{\"content\": \"{{CHANGELOG}}\"}" \
+  $DISCORD_WEBHOOK_URL
+```
+
+To get a webhook URL, go to your Discord server -> Server Settings -> Integrations -> Webhooks -> New Webhook.
+
+</process>
+
+<guardrails>
+- If no changes in the time period, post a "quiet day" message: "Quiet day! No new changes merged."
+- If unable to fetch PR details, list the PR numbers for manual review
+- Always validate message length before posting to Discord (max 2000 chars)
+</guardrails>
+
+<context>
+
+## Schedule Recommendations
+
+- Run daily at 6 AM NY time for previous day's changes
+- Run weekly summary on Mondays for the previous week
+- Special runs after major releases or deployments
+
+## Audience Considerations
+
+Adjust the tone and detail level based on the channel:
+
+- **Dev team channels**: Include technical details, performance metrics, code snippets
+- **Product team channels**: Focus on user-facing changes and business impact
+- **Leadership channels**: Highlight progress on key initiatives and blockers
+</context>

package/plugins/lavra/opencode/commands/create-agent-skill.md

@@ -0,0 +1,21 @@
+<!-- Generated by lavra-compound v0.6.0 -->
+<!-- Source: create-agent-skill.md -->
+<!-- DO NOT EDIT - changes will be overwritten on next install -->
+
+---
+name: create-agent-skill
+description: "Create or edit Claude Code skills with expert guidance on structure and best practices"
+allowed-tools: Skill(create-agent-skills)
+argument-hint: [skill description or requirements]
+disable-model-invocation: true
+---
+
+<objective>
+Create or edit Claude Code skills by invoking the create-agent-skills skill with expert guidance on structure and best practices.
+</objective>
+
+<process>
+
+Invoke the create-agent-skills skill for: $ARGUMENTS
+
+</process>

package/plugins/lavra/opencode/commands/deploy-docs.md

@@ -0,0 +1,69 @@
+<!-- Generated by lavra-compound v0.6.0 -->
+<!-- Source: deploy-docs.md -->
+<!-- DO NOT EDIT - changes will be overwritten on next install -->
+
+---
+name: deploy-docs
+description: Validate and prepare documentation for GitHub Pages deployment
+disable-model-invocation: true
+---
+
+<objective>
+Validate the documentation site structure, check component counts and JSON validity, and prepare for GitHub Pages deployment.
+</objective>
+
+<process>
+
+## Step 1: Validate Documentation
+
+Run these checks:
+
+```bash
+# Count components
+echo "Agents: $(find plugins/lavra-compound/agents -name '*.md' | wc -l)"
+echo "Commands: $(ls plugins/lavra-compound/commands/*.md | wc -l)"
+echo "Skills: $(ls -d plugins/lavra-compound/skills/*/ 2>/dev/null | wc -l)"
+
+# Validate JSON
+cat .claude-plugin/marketplace.json | jq . > /dev/null && echo "marketplace.json valid"
+cat plugins/lavra-compound/.claude-plugin/plugin.json | jq . > /dev/null && echo "plugin.json valid"
+```
+
+## Step 2: Check for Uncommitted Changes
+
+```bash
+git status --porcelain plugins/lavra-compound/
+```
+
+If there are uncommitted changes, warn the user to commit first.
+
+## Step 3: Deployment Instructions
+
+Since GitHub Pages deployment requires a workflow file with special permissions, provide these instructions:
+
+### First-time Setup
+
+1. Create `.github/workflows/deploy-docs.yml` with the GitHub Pages workflow
+2. Go to repository Settings > Pages
+3. Set Source to "GitHub Actions"
+
+### Deploying
+
+After merging to `main`, the docs will auto-deploy. Or:
+
+1. Go to Actions tab
+2. Select "Deploy Documentation to GitHub Pages"
+3. Click "Run workflow"
+
+</process>
+
+<success_criteria>
+- All HTML pages present
+- JSON files valid
+- Component counts match
+
+### Next Steps
+- [ ] Commit any pending changes
+- [ ] Push to main branch
+- [ ] Verify GitHub Pages workflow exists
+</success_criteria>