Customization

# Generate from template
lv artifact create instructions my-domain

# With specific scope
lv artifact create instructions payments --applyTo "**/payments/**"

---
applyTo: "**/payments/**,**/billing/**"
---

# Payment Domain Instructions

## Security Requirements
- All payment amounts must use decimal types, never floats
- PCI DSS compliance is mandatory for card data
- Log transaction IDs, never card numbers

## API Patterns
- Use idempotency keys for all mutations
- Implement retry with exponential backoff
- Return structured error responses

## Testing
- Mock all external payment provider calls
- Test edge cases: zero amounts, refunds, partial payments
- Include timezone edge cases for billing cycles

lv artifact create prompt migration

---
mode: agent
tools:
  - filesystem
  - git
  - postgres
description: Create database migration for schema changes
---

# Database Migration

You are creating a database migration.

## Context
- **Schema**: #file:prisma/schema.prisma
- **Current Selection**: #selection

## Instructions
Follow #file:.github/instructions/prisma.instructions.md

## Task
Create a migration for:

```
#selection
```

## Requirements
1. Use Prisma migrate format
2. Include rollback steps
3. Add data migration if needed
4. Update seed data

## Output
- Migration file in prisma/migrations/
- Updated schema.prisma if needed
- Migration documentation

# In VS Code Copilot Chat
#prompt:migration

# Or via CLI
lv prompt run migration --selection "Add email verification field"

# New toolset from scratch
lv artifact create toolset readonly

# Extend existing toolset
lv artifact create toolset deploy --extends default

{
  "name": "deploy",
  "description": "Toolset for production deployments",
  "extends": "default",
  
  "tools": {
    "filesystem": {
      "enabled": true,
      "config": {
        "allowedPaths": ["src/**", "dist/**"],
        "blockedPaths": ["*.env*", "*.key", "secrets/**"]
      }
    },
    "git": {
      "enabled": true,
      "config": {
        "allowCommit": true,
        "allowPush": true,
        "allowedBranches": ["main", "release/*"]
      }
    },
    "github": {
      "enabled": true,
      "config": {
        "allowPR": false,
        "allowRelease": true,
        "requireApproval": true
      }
    }
  },
  
  "securityPolicy": {
    "requireApproval": ["all"],
    "auditAll": true,
    "blockPatterns": ["DROP", "DELETE", "TRUNCATE"]
  }
}

{
  "devcycles": {
    "custom": [
      {
        "id": "onboard",
        "name": "Developer Onboarding",
        "description": "Set up new developer environment",
        "instruction": ".github/instructions/onboard.instructions.md",
        "prompt": ".github/prompts/onboard.prompt.md",
        "toolset": ".github/toolsets/default.toolset.jsonc",
        "phases": ["analyze", "implement", "validate"],
        "checkpoints": {
          "required": ["validate"],
          "autoCreate": true
        }
      }
    ]
  }
}

# Create instruction file
lv artifact create instructions onboard

# Create prompt file  
lv artifact create prompt onboard

lv devcycle run onboard --wizard

---
name: Security Reviewer
description: Reviews code for security vulnerabilities
tools:
  - filesystem
  - git
instructions:
  - .github/copilot-instructions.md
  - .github/instructions/security.instructions.md
---

# Security Reviewer Agent

You are a security-focused code reviewer. Your job is to identify
potential vulnerabilities and suggest fixes.

## Focus Areas
- Authentication and authorization flaws
- Input validation gaps
- SQL injection possibilities
- XSS vulnerabilities
- Sensitive data exposure
- Cryptographic weaknesses

## Review Process
1. Scan for common vulnerability patterns
2. Check authentication flows
3. Verify input sanitization
4. Review data handling
5. Assess cryptographic usage

## Output Format
For each issue found:
- Severity: Critical/High/Medium/Low
- Location: File and line number
- Description: What's wrong
- Recommendation: How to fix
- Reference: CWE or OWASP ID

# Project-Specific Additions

## Custom Conventions
In addition to framework defaults, this project follows:

- Use snake_case for database columns
- Prefix private methods with underscore
- Include JSDoc for all exported functions

## Domain Context
This is an e-commerce platform. Key concepts:
- Products have variants and SKUs
- Orders go through fulfillment states
- Payments are handled by Stripe

## Team Preferences
- Prefer explicit over implicit
- Favor composition over inheritance
- Write tests before implementation

lv upgrade --strategy merge

# Preview changes first
lv upgrade --strategy merge --dry-run

# Export customizations
lv artifact export --output customizations.tar.gz

# Import after fresh install
lv artifact import customizations.tar.gz

# Validate all artifacts
lv artifact validate

# Check for conflicts with framework
lv doctor --verbose

# Test custom DevCycle
lv devcycle run my-custom-cycle --dry-run