LiveTemplate CLI Generator (lvt)
A Phoenix-inspired code generator for LiveTemplate applications with CRUD functionality and interactive TUI wizards.
Installation
go install github.com/livetemplate/lvt@latest
Or download pre-built binaries from the releases page.
Or build from source:
git clone https://github.com/livetemplate/lvt
cd lvt
go build -o lvt .
Version Synchronization
LVT follows the LiveTemplate core library's major.minor version:
- Core:
v0.1.5 β LVT: v0.1.x (any patch version)
- Core:
v0.2.0 β LVT: v0.2.0 (must match major.minor)
Contributing
See CONTRIBUTING.md for development guidelines.
All pull requests require passing CI checks including tests, linting, and code formatting.
Support
AI-Assisted Development
lvt provides AI assistance through multiple approaches, supporting all major AI assistants:
Quick Start
# List available AI agents
lvt install-agent --list
# Install agent for your AI assistant
lvt install-agent --llm <type> # claude, copilot, cursor, aider, generic
# Or start the MCP server (works with all MCP-compatible AIs)
lvt mcp-server
Supported AI Assistants
| AI Assistant |
Installation |
Best For |
| Claude Code |
lvt install-agent --llm claude |
Full workflows with 20+ skills |
| GitHub Copilot |
lvt install-agent --llm copilot |
In-editor suggestions |
| Cursor |
lvt install-agent --llm cursor |
Rule-based development |
| Aider |
lvt install-agent --llm aider |
CLI-driven development |
| Generic/Other |
lvt install-agent --llm generic |
Custom LLMs via MCP |
Claude Code (Recommended)
Full-featured agent with skills and workflows:
# Install
lvt install-agent --llm claude
# Upgrade
lvt install-agent --upgrade
# Start Claude Code
claude
Features:
- 20+ skills for lvt commands
- Project management agent
- Guided workflows
- Best practices enforcement
Try asking:
- "Add a posts resource with title and content"
- "Generate authentication system"
- "Create a quickstart blog app"
GitHub Copilot
Instructions-based integration:
# Install
lvt install-agent --llm copilot
# Open in VS Code - Copilot automatically understands LiveTemplate
Cursor
Rule-based development patterns:
# Install
lvt install-agent --llm cursor
# Open project in Cursor - rules apply to *.go files automatically
Aider
CLI configuration:
# Install
lvt install-agent --llm aider
# Start Aider - configuration loads automatically
aider
Upgrading Agents
# Upgrade any agent type
lvt install-agent --llm <type> --upgrade
This preserves your custom settings while updating the agent files.
Complete Setup Guide
For detailed setup instructions for each AI assistant, see:
Global AI Access via MCP Server
lvt also provides a Model Context Protocol (MCP) server that works with Claude Desktop, Claude Code, and other MCP-compatible AI applications. This gives you global access to lvt commands from anywhere.
Setup for Claude Desktop
-
Install lvt globally:
go install github.com/livetemplate/lvt@latest
-
Configure Claude Desktop by editing claude_desktop_config.json:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
Add:
{
"mcpServers": {
"lvt": {
"command": "lvt",
"args": ["mcp-server"]
}
}
}
-
Restart Claude Desktop
Once configured, Claude has access to these 16 tools:
Project & Resource Generation:
- lvt_new - Create new apps with kit/CSS/module options
- lvt_gen_resource - Generate CRUD resources with fields
- lvt_gen_view - Generate view-only handlers
- lvt_gen_auth - Generate authentication systems
- lvt_gen_schema - Generate database schema only
Database Migrations:
- lvt_migration_up - Run pending migrations
- lvt_migration_down - Rollback last migration
- lvt_migration_status - Check migration status
- lvt_migration_create - Create new migration files
Data & Inspection:
- lvt_seed - Generate test data for resources
- lvt_resource_list - List all available resources
- lvt_resource_describe - Show detailed schema for a resource
Validation & Configuration:
- lvt_validate_template - Validate and analyze template files
- lvt_env_generate - Generate .env.example with detected config
- lvt_kits_list - List available CSS framework kits
- lvt_kits_info - Show detailed kit information
Usage Example
In Claude Desktop, simply ask:
"Create a new LiveTemplate app called 'blog' with the multi kit"
Claude will use the MCP tools to create your app, even before you have a project directory!
MCP vs Embedded Agent
- MCP Server: Global access, works with Claude Desktop, great for project creation
- Embedded Agent: Project-specific, richer workflows, 20+ skills with detailed guidance
Use both for the best experience!
Quick Start
You can use lvt in two modes: Interactive (TUI wizards) or Direct (CLI arguments).
Important: Create apps outside of existing Go module directories. If you create an app inside another Go module (e.g., for testing), you'll need to use GOWORK=off when running commands:
GOWORK=off go run cmd/myapp/main.go
Interactive Mode (Recommended for New Users)
# Launch interactive app creator
lvt new
# Launch interactive resource builder
lvt gen
# Launch interactive view creator
lvt gen view
Direct Mode
1. Create a New App
lvt new myapp
cd myapp
This generates:
- Complete Go project structure
- Database layer with sqlc integration
- go.mod with Go 1.24+ tools directive
- README with next steps
2. Generate a CRUD Resource
# With explicit types
lvt gen users name:string email:string age:int
# With inferred types (NEW!)
lvt gen products name price quantity enabled created_at
# β Infers: name:string price:float quantity:int enabled:bool created_at:time
This generates:
app/users/users.go - Full CRUD handler
app/users/users.tmpl - Tailwind CSS UI
app/users/users_ws_test.go - WebSocket tests
app/users/users_test.go - Chromedp E2E tests
- Database schema and queries (appended)
3. Run Migrations
lvt migration up # Runs pending migrations and auto-generates database code
This automatically:
- Applies pending database migrations
- Runs
sqlc generate to create Go database code
- Updates your query interfaces
4. Wire Up Routes
Add to cmd/myapp/main.go:
import "myapp/app/users"
// In main():
http.Handle("/users", users.Handler(queries))
5. Run the App
go run cmd/myapp/main.go
Open http://localhost:8080/users
Tutorial: Building a Blog System
Let's build a complete blog system with posts, comments, and categories to demonstrate lvt's capabilities.
Step 1: Create the Blog App
lvt new myblog
cd myblog
This creates your project structure with database setup, main.go, and configuration. Dependencies are automatically installed via go get ./....
Step 2: Generate Resources
lvt gen posts title content:string published:bool
lvt gen categories name description
lvt gen comments post_id:references:posts author text
This generates for each resource:
- β
app/{resource}/{resource}.go - CRUD handler with LiveTemplate integration
- β
app/{resource}/{resource}.tmpl - Component-based template with Tailwind CSS
- β
app/{resource}/{resource}_test.go - E2E tests with chromedp
- β
Database migration file with unique timestamps
- β
SQL queries appended to
database/queries.sql
For the comments resource with post_id:references:posts:
- β
Creates
post_id field as TEXT (matching posts.id type)
- β
Adds foreign key constraint:
FOREIGN KEY (post_id) REFERENCES posts(id) ON DELETE CASCADE
- β
Creates index on
post_id for query performance
- β
No manual migration needed!
Step 3: Run Migrations
lvt migration up
This command:
- β
Runs all pending database migrations
- β
Automatically generates Go database code with sqlc
- β
Creates type-safe query interfaces
You'll see output like:
Running pending migrations...
OK 20240315120000_create_posts.sql
OK 20240315120001_create_categories.sql
OK 20240315120002_create_comments.sql
Generating database code with sqlc...
β
Database code generated successfully!
β
Migrations complete!
Step 4: Resolve Dependencies
go mod tidy
This resolves all internal package imports created by the generated code. Required before running the app.
Step 5: Wire Up Routes
The routes are auto-injected, but verify in cmd/myblog/main.go:
import (
"myblog/app/posts"
"myblog/app/categories"
"myblog/app/comments"
)
func main() {
// ... database setup ...
// Routes (auto-injected)
http.Handle("/posts", posts.Handler(queries))
http.Handle("/categories", categories.Handler(queries))
http.Handle("/comments", comments.Handler(queries))
// Start server
http.ListenAndServe(":8080", nil)
}
Step 6: Run the Blog
go run cmd/myblog/main.go
Visit:
Note: Visiting http://localhost:8080/ will show a 404 since no root handler exists. You can add a homepage next.
Step 7: Add a Custom View for the Homepage (Optional)
lvt gen view home
go mod tidy
go run cmd/myblog/main.go
This creates a view-only handler (no database operations). Edit app/home/home.tmpl to create your landing page, then visit http://localhost:8080/home.
Step 8: Test the Application
# Run all tests (E2E + WebSocket)
go test ./...
# Run specific resource tests
go test ./app/posts -v
Customization Ideas
1. Generate resources (CSS framework determined by kit):
# Resources use the CSS framework from your chosen kit
# Multi and single kits use Tailwind CSS
# Simple kit uses no CSS framework (semantic HTML)
lvt gen tags name
# To use a different CSS framework, create your app with a different kit
lvt new myapp --kit simple # Uses no CSS (semantic HTML)
cd myapp
lvt gen authors name bio # Will use semantic HTML
2. Use Type Inference:
# Field types are inferred from names
lvt gen articles title content published_at author email price
# Infers: title=string, content=string, published_at=time,
# author=string, email=string, price=float
3. Create Custom Templates:
# Copy templates to customize
lvt template copy all
# Edit templates in .lvt/templates/
# Your customizations apply to all new resources
4. Define Relationships with references:
# Basic reference (ON DELETE CASCADE - default)
lvt gen comments post_id:references:posts author text
# Custom ON DELETE behavior
lvt gen audit_logs user_id:references:users:set_null action:string
# Makes user_id nullable, sets NULL when user deleted
# Multiple references
lvt gen likes user_id:references:users post_id:references:posts
# Restrict deletion (prevent deleting parent if children exist)
lvt gen invoices customer_id:references:customers:restrict amount:float
5. Add More Features:
# Tags for posts
lvt gen tags name color:string
# Post-tag relationship (many-to-many with references)
lvt gen post_tags post_id:references:posts tag_id:references:tags
# User accounts
lvt gen users username email password_hash:string
# Post reactions with proper relationships
lvt gen reactions post_id:references:posts user_id:references:users type:string
Project Structure
After completing the tutorial, your project looks like:
myblog/
βββ cmd/myblog/main.go
βββ internal/
β βββ app/
β β βββ posts/
β β β βββ posts.go
β β β βββ posts.tmpl
β β β βββ posts_test.go
β β β βββ posts_ws_test.go
β β βββ categories/
β β βββ comments/
β β βββ home/
β βββ database/
β βββ db.go
β βββ migrations/
β β βββ 20240315120000_create_posts.sql
β β βββ 20240315120001_create_categories.sql
β β βββ ...
β βββ queries.sql
β βββ models/ # Generated by sqlc
β βββ db.go
β βββ models.go
β βββ queries.sql.go
βββ go.mod
Next Steps
- Add Authentication - Integrate session management
- Rich Text Editor - Add markdown or WYSIWYG editor to post content
- Image Uploads - Add image upload functionality
- Search - Implement full-text search across posts
- RSS Feed - Generate RSS feed from posts
- Admin Dashboard - Create
lvt gen view admin
- API Endpoints - Add JSON API alongside HTML views
Tips
- Start simple - Begin with core resources, add features incrementally
- Use migrations - Always use
lvt migration create for schema changes
- Test continuously - Run
go test ./... after each change
- Customize templates - Copy and modify templates to match your design
- Component mode - Use
--mode single for SPA-style applications
Commands
lvt new <app-name>
Creates a new LiveTemplate application with:
myapp/
βββ cmd/myapp/main.go # Application entry point
βββ go.mod # With //go:tool directive
βββ internal/
β βββ app/ # Handlers and templates
β βββ database/
β β βββ db.go # Connection & migrations
β β βββ schema.sql # Database schema
β β βββ queries.sql # SQL queries (sqlc)
β β βββ sqlc.yaml # sqlc configuration
β β βββ models/ # Generated code
β βββ shared/ # Shared utilities
βββ web/assets/ # Static assets
βββ README.md
lvt gen <resource> <field:type>...
Generates a full CRUD resource with database integration.
Example:
lvt gen posts title:string content:string published:bool views:int
Generated Files:
- Handler with State struct, Change() method, Init() method
- Bulma CSS template with:
- Create form with validation
- List view with search, sort, pagination
- Delete functionality
- Real-time WebSocket updates
- WebSocket unit tests
- Chromedp E2E tests
- Database schema and queries
Features:
- β
CRUD operations (Create, Read, Update, Delete)
- β
Search across string fields
- β
Sorting by fields
- β
Pagination
- β
Real-time updates via WebSocket
- β
Form validation
- β
Statistics/counts
- β
Bulma CSS styling
- β
Comprehensive tests
- β
Auto-injected routes - Automatically adds route and import to
main.go
lvt gen view <name>
Generates a view-only handler without database integration (like the counter example).
Example:
lvt gen view dashboard
Generates:
app/dashboard/dashboard.go - View handler with state management
app/dashboard/dashboard.tmpl - Bulma CSS template
app/dashboard/dashboard_ws_test.go - WebSocket tests
app/dashboard/dashboard_test.go - Chromedp E2E tests
Features:
- β
State management
- β
Real-time updates via WebSocket
- β
Bulma CSS styling
- β
Comprehensive tests
- β
No database dependencies
- β
Auto-injected routes - Automatically adds route and import to
main.go
lvt gen auth
Generates a complete authentication system similar to Phoenix's mix phx.gen.auth.
Example:
# Generate with default settings (password + magic-link auth)
lvt gen auth
# Generate with only password authentication
lvt gen auth --no-magic-link
# Generate with only magic-link authentication
lvt gen auth --no-password
# Disable email confirmation
lvt gen auth --no-email-confirm
# Disable CSRF protection
lvt gen auth --no-csrf
Flags:
--no-password - Disable password authentication
--no-magic-link - Disable magic-link authentication
--no-email-confirm - Disable email confirmation flow
--no-password-reset - Disable password reset functionality
--no-sessions-ui - Disable session management UI
--no-csrf - Disable CSRF protection middleware
Note: At least one authentication method (password or magic-link) must be enabled.
Generates:
shared/password/password.go - Password hashing utilities (bcrypt)
shared/email/email.go - Email sender interface with console logger
database/migrations/YYYYMMDDHHMMSS_create_auth_tables.sql - Auth tables migration
- Auth queries appended to
database/queries.sql
Features:
- β
Password authentication with bcrypt hashing
- β
Magic-link email authentication
- β
Email confirmation flow
- β
Password reset functionality
- β
Session management
- β
CSRF protection with gorilla/csrf
- β
Auto-updates
go.mod dependencies
- β
EmailSender interface (console logger + SMTP/Mailgun examples)
- β
Case-insensitive email matching
- β
Configurable features via flags
Database Tables:
users - User accounts with email and optional hashed password
user_tokens - Tokens for magic links, email confirmation, password reset
Next Steps After Generation:
# 1. Run migrations
lvt migration up
# 2. Generate sqlc code
sqlc generate
# 3. Update main.go to register auth handler
# (Implementation in Phase 2)
Router Auto-Update
When you generate a resource or view, lvt automatically:
-
Adds the import to your cmd/*/main.go:
import (
"yourapp/app/users" // β Auto-added
)
-
Injects the route after the TODO comment:
// TODO: Add routes here
http.Handle("/users", users.Handler(queries)) // β Auto-added
-
Maintains idempotency - Running the same command twice won't duplicate routes
This eliminates the manual step of wiring up routes, making the development workflow smoother. Routes are inserted in the order you generate them, right after the TODO marker.
Type Mappings
| CLI Type |
Go Type |
SQL Type |
| string |
string |
TEXT |
| int |
int64 |
INTEGER |
| bool |
bool |
BOOLEAN |
| float |
float64 |
REAL |
| time |
time.Time |
DATETIME |
Aliases:
str, text β string
integer β int
boolean β bool
float64, decimal β float
datetime, timestamp β time
Smart Type Inference (π Phase 1)
The CLI includes an intelligent type inference system that automatically suggests types based on field names:
How It Works
When using the type inference system, you can omit explicit types and let the system infer them:
// In ui.InferType("email") β returns "string"
// In ui.InferType("age") β returns "int"
// In ui.InferType("price") β returns "float"
// In ui.InferType("enabled") β returns "bool"
// In ui.InferType("created_at") β returns "time"
Inference Rules
String fields (default for unknown):
- Exact:
name, title, description, email, username, url, slug, address, etc.
- Contains:
*email*, *url*
Integer fields:
- Exact:
age, count, quantity, views, likes, score, rank, year
- Suffix:
*_count, *_number, *_index
Float fields:
- Exact:
price, amount, rating, latitude, longitude
- Suffix/Contains:
*_price, *_amount, *_rate, *price*, *amount*
Boolean fields:
- Exact:
enabled, active, published, verified, approved, deleted
- Prefix:
is_*, has_*, can_*
Time fields:
- Exact:
created_at, updated_at, deleted_at, published_at
- Suffix:
*_at, *_date, *_time
Usage
The inference system is available via the ui package:
import "github.com/livetemplate/lvt/internal/ui"
// Infer type from field name
fieldType := ui.InferType("email") // β "string"
// Parse field input (with or without type)
name, typ := ui.ParseFieldInput("email") // β "email", "string" (inferred)
name, typ := ui.ParseFieldInput("age:float") // β "age", "float" (explicit override)
Future Enhancement
In upcoming phases, this will power:
- Interactive field builders that suggest types as you type
- Direct mode support:
lvt gen users name email age (without explicit types)
- Smart defaults that reduce typing
Project Layout
The generated app follows idiomatic Go conventions:
cmd/ - Application entry points
app/ - Handlers and templates (co-located!)
database/ - Database layer with sqlc
shared/ - Shared utilities
web/assets/ - Static assets
Key Design Decision: Templates live next to their handlers for easy discovery.
Generated Handler Structure
package users
type State struct {
Queries *models.Queries
Users []User
SearchQuery string
SortBy string
CurrentPage int
PageSize int
TotalPages int
// ...
}
// Action methods - automatically dispatched based on action name
func (s *State) Add(ctx *livetemplate.ActionContext) error {
// Create user
return nil
}
func (s *State) Update(ctx *livetemplate.ActionContext) error {
// Update user
return nil
}
func (s *State) Delete(ctx *livetemplate.ActionContext) error {
// Delete user
return nil
}
func (s *State) Search(ctx *livetemplate.ActionContext) error {
// Search users
return nil
}
func (s *State) Init() error {
// Load initial data
return nil
}
func Handler(queries *models.Queries) http.Handler {
tmpl := livetemplate.New("users")
state := &State{Queries: queries, PageSize: 10}
return tmpl.Handle(state)
}
Testing
The project includes comprehensive testing infrastructure at multiple levels.
Make Targets (Recommended)
Use these convenient make targets for different testing workflows:
make test-fast # Unit tests only (~30s)
make test-commit # Before committing (~3-4min)
make test-all # Full suite (~5-6min)
make test-clean # Clean Docker resources
See Testing Guide for detailed documentation on test optimization and architecture.
Quick Start
# Run all tests (fast mode - skips deployment tests)
go test ./... -short
# Run all tests (including slower e2e tests)
go test ./...
# Run specific package tests
go test ./internal/generator -v
# Run tests with coverage
go test ./... -cover
Test Types
1. Unit Tests
Fast tests for individual packages and functions:
# Internal packages
go test ./internal/config ./internal/generator ./internal/parser -v
# Commands package
go test ./commands -v
Duration: <5 seconds
2. WebSocket Tests (*_ws_test.go)
Fast unit tests for WebSocket protocol and state changes in generated resources:
go test ./app/users -run WebSocket
Features:
- Test server startup with dynamic ports
- WebSocket connection testing
- CRUD action testing
- Server log capture for debugging
Duration: 2-5 seconds per resource
3. E2E Browser Tests (*_test.go)
Full browser testing with real user interactions for generated resources:
go test ./app/users -run E2E
Features:
- Docker Chrome container
- Real browser interactions (clicks, typing, forms)
- Visual verification
- Screenshot capture
- Console log access
Duration: 20-60 seconds per resource
4. Deployment Tests (Advanced)
Comprehensive deployment testing infrastructure for testing real deployments:
# Mock deployment tests (fast, no credentials needed)
go test ./e2e -run TestDeploymentInfrastructure_Mock -v
# Docker deployment tests (requires Docker)
RUN_DOCKER_DEPLOYMENT_TESTS=true go test ./e2e -run TestDockerDeployment -v
# Fly.io deployment tests (requires credentials)
export FLY_API_TOKEN="your_token"
RUN_FLY_DEPLOYMENT_TESTS=true go test ./e2e -run TestRealFlyDeployment -v
Features:
- Mock, Docker, and Fly.io deployment testing
- Automatic cleanup and resource management
- Smoke tests (HTTP, health, WebSocket, templates)
- Credential-based access control
Duration: 2 minutes (mock) to 15 minutes (real deployments)
Test Environment Variables
| Variable |
Purpose |
Default |
RUN_DOCKER_DEPLOYMENT_TESTS |
Enable Docker deployment tests |
false |
RUN_FLY_DEPLOYMENT_TESTS |
Enable Fly.io deployment tests |
false |
FLY_API_TOKEN |
Fly.io API token for real deployments |
- |
Continuous Integration
Tests run automatically on every pull request via GitHub Actions:
- β
Code formatting validation
- β
Unit tests (all internal packages)
- β
Commands tests
- β
E2E tests (short mode)
- β
Mock deployment tests
On-demand/scheduled deployment testing available via manual workflow dispatch or weekly schedule.
For detailed CI/CD documentation, see:
Skip Slow Tests
Use -short flag to skip slow tests (deployment tests, long-running e2e tests):
go test -short ./...
Test Documentation
For comprehensive testing documentation, see:
Generated go.mod includes:
//go:tool github.com/sqlc-dev/sqlc/cmd/sqlc
Run migrations (automatically runs sqlc):
lvt migration up
CSS Framework
All generated templates use Bulma CSS by default:
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/css/bulma.min.css">
Components used:
.section, .container - Layout
.box - Content containers
.table - Data tables
.button, .input, .select - Form controls
.pagination - Pagination controls
Development Workflow
- Create app:
lvt new myapp
- Generate resources:
lvt gen users name:string email:string
- Run migrations:
lvt migration up (auto-generates DB code)
- Wire routes in
main.go
- Run tests:
go test ./...
- Run app:
go run cmd/myapp/main.go
Examples
Blog App
lvt new myblog
cd myblog
# Generate posts resource
lvt gen posts title:string content:string published:bool
# Generate comments resource
lvt gen comments post_id:string author:string text:string
# Run migrations (auto-generates DB code)
lvt migration up
# Run
go run cmd/myblog/main.go
E-commerce
lvt new mystore
cd mystore
lvt gen products name:string price:float stock:int
lvt gen customers name:string email:string
lvt gen orders customer_id:string total:float
lvt migration up # Runs migrations and generates DB code
go run cmd/mystore/main.go
Architecture
Template System
The generator uses custom delimiters ([[, ]]) to avoid conflicts with Go template syntax:
- Generator templates:
[[.ResourceName]] - Replaced during generation
- Output templates:
{{.Title}} - Used at runtime by LiveTemplate
Embedded Templates
All templates are embedded using embed.FS for easy distribution.
Code Generation Strategy
- Parse field definitions (
name:type)
- Map types to Go and SQL types
- Render templates with resource data
- Generate handler, template, tests
- Append to database files
Testing the Generator
Run All Tests
go test ./cmd/lvt -v
Test Layers
-
Parser Tests (cmd/lvt/internal/parser/fields_test.go)
- Field parsing and validation
- Type mapping correctness
- 13 comprehensive tests
-
Golden File Tests (cmd/lvt/golden_test.go)
- Regression testing for generated code
- Validates handler and template output
- Update with:
UPDATE_GOLDEN=1 go test ./cmd/lvt -run Golden
-
Integration Tests (cmd/lvt/integration_test.go)
- Go syntax validation
- File structure validation
- Generation pipeline testing
-
Smoke Test (scripts/test_cli_smoke.sh)
- End-to-end CLI workflow
- App creation and resource generation
- File structure verification
Roadmap
-
lvt gen view - View-only handlers β
Complete
-
Router auto-update β
Complete
-
Bubbletea interactive UI β
Complete (Phase 1-3)
- Dependencies & infrastructure
- Smart type inference system (50+ patterns)
- UI styling framework (Lipgloss)
- Interactive app creation wizard
- Interactive resource builder
- Interactive view builder
- Mode detection (auto-switch based on args)
- Type inference in direct mode
-
Enhanced validation & help system (Phase 4) β
Complete
- Real-time Go identifier validation
- SQL reserved word warnings (25+ keywords)
- Help overlay with
? key in all wizards
- Color-coded feedback (βββ )
- All 3 wizards enhanced
-
Migration commands β
Complete
- Goose integration with minimal wrapper (~410 lines)
- Auto-generate migrations from
lvt gen resource
- Commands:
up, down, status, create <name>
- Timestamped migration files with Up/Down sections
- Schema versioning and rollback support
-
Custom template support β
Complete
- Cascading template lookup (project β user β embedded)
-
lvt template copy command for easy customization
- Project templates in
.lvt/templates/ (version-controlled)
- User-wide templates in
~/.config/lvt/templates/
- Selective override (only customize what you need)
- Zero breaking changes (~250 lines total)
-
Multiple CSS frameworks β
Complete
- Tailwind CSS v4 (default)
- Bulma 1.0.4
- Pico CSS v2
- None (pure HTML)
- CSS framework determined by kit (multi/single use Tailwind, simple uses Pico)
- 57 CSS helper functions for framework abstraction
- Conditional template rendering (single source of truth)
- Semantic HTML support for Pico CSS (, )
- Zero breaking changes (~550 lines total)
-
lvt gen auth - Authentication system β
Phase 1 Complete
- Password authentication (bcrypt)
- Magic-link email authentication
- Email confirmation flow
- Password reset functionality
- Session management tables
- CSRF protection (gorilla/csrf)
- Auto-dependency updates (go.mod)
- EmailSender interface with examples
- Configurable via flags
- Auth handlers (Phase 2)
- Custom authenticator (Phase 3)
- Middleware templates (Phase 4)
- GraphQL support
Contributing
See the main LiveTemplate CLAUDE.md for development guidelines.
License
Same as LiveTemplate project.