quiver-cli 1.3.0 → 2.0.0

package/template/.agents/skills/data/prisma-cli/references/migrate-dev.md

@@ -1,145 +0,0 @@
-# prisma migrate dev
-
-Creates and applies migrations during development. Requires a shadow database.
-
-## Command
-
-```bash
-prisma migrate dev [options]
-```
-
-## What It Does
-
-1. Runs existing migrations in shadow database to detect drift
-2. Applies any pending migrations
-3. Generates new migration from schema changes
-4. Applies new migration to development database
-5. Updates `_prisma_migrations` table
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--name` / `-n` | Name the migration |
-| `--create-only` | Create a new migration but do not apply it |
-| `--schema` | Custom path to your Prisma schema |
-| `--config` | Custom path to your Prisma config file |
-| `--url` | Override the datasource URL from the Prisma config file |
-
-### Follow-up Commands
-
-- Run `prisma generate` explicitly when you need refreshed client output
-- Run `prisma db seed` explicitly when you need seed data
-
-Note: Prisma CLI help for `7.6.0` still says `migrate dev` "trigger[s] generators", but local verification in a temp Prisma 7.6.0 project did not emit generated client files. Treat `prisma generate` as an explicit follow-up step when you need generated artifacts on disk.
-
-## Examples
-
-### Create and apply migration
-
-```bash
-prisma migrate dev
-```
-
-Prompts for migration name if schema changed.
-
-### Named migration
-
-```bash
-prisma migrate dev --name add_users_table
-```
-
-### Create without applying
-
-```bash
-prisma migrate dev --create-only
-```
-
-Useful for reviewing migration SQL before applying.
-
-### Full workflow
-
-```bash
-prisma migrate dev --name my_migration
-prisma generate
-prisma db seed
-```
-
-## Migration Files
-
-Created in `prisma/migrations/`:
-
-```
-prisma/migrations/
-├── 20240115120000_add_users_table/
-│   └── migration.sql
-├── 20240116090000_add_posts/
-│   └── migration.sql
-└── migration_lock.toml
-```
-
-## Schema Drift Detection
-
-If `migrate dev` detects drift (manual database changes or edited migrations), it prompts to reset:
-
-```
-Drift detected: Your database schema is not in sync.
-
-Do you want to reset your database? All data will be lost.
-```
-
-## When to Use
-
-- Local development
-- Adding new models/fields
-- Changing relations
-- Creating indexes
-
-## When NOT to Use
-
-- Production deployments (use `migrate deploy`)
-- CI/CD pipelines (use `migrate deploy`)
-- MongoDB (use `db push` instead)
-
-## Common Patterns
-
-### After schema changes
-
-```prisma
-// schema.prisma - Add new field
-model User {
-  id        Int      @id @default(autoincrement())
-  email     String   @unique
-  name      String?
-  createdAt DateTime @default(now())  // New field
-}
-```
-
-```bash
-prisma migrate dev --name add_created_at
-```
-
-### Handling data loss warnings
-
-When a migration would cause data loss:
-
-```bash
-prisma migrate dev --name remove_field
-# Warning: You are about to delete data...
-# Accept with: --accept-data-loss
-```
-
-## Shadow Database
-
-`migrate dev` requires a shadow database for drift detection. Configure in `prisma.config.ts`:
-
-```typescript
-export default defineConfig({
-  datasource: {
-    url: env('DATABASE_URL'),
-    shadowDatabaseUrl: env('SHADOW_DATABASE_URL'),
-  },
-})
-```
-
-For local Prisma Postgres (`prisma dev`), shadow database is handled automatically.

package/template/.agents/skills/data/prisma-cli/references/migrate-diff.md

@@ -1,89 +0,0 @@
-# prisma migrate diff
-
-Compares database schemas and generates diffs (SQL or summary).
-
-## Command
-
-```bash
-prisma migrate diff [options]
-```
-
-## What It Does
-
-- Compares two sources (`--from-...` and `--to-...`)
-- Sources can be:
-    - Empty (`empty`)
-    - Schema file (`schema`)
-    - Migrations directory (`migrations`)
-    - Database URL (`url`) or Configured Datasource (`config-datasource`)
-- Outputs the difference:
-    - Human-readable summary (default)
-    - SQL script (`--script`)
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--script` | Render SQL script to stdout |
-| `--exit-code` | Exit 2 if changes detected, 0 if empty, 1 if error |
-| `--config` | Custom path to your Prisma config file |
-
-### Sources (Must provide one `from` and one `to`)
-
-- `--from-empty`, `--to-empty`
-- `--from-schema <path>`, `--to-schema <path>`
-- `--from-migrations <path>`, `--to-migrations <path>`
-- `--from-url <url>`, `--to-url <url>`
-- `--from-config-datasource`, `--to-config-datasource` (uses `prisma.config.ts`)
-
-## Examples
-
-### Generate SQL for a schema change
-
-Compare current production DB to your local schema:
-
-```bash
-prisma migrate diff \
-  --from-url "$PROD_DB_URL" \
-  --to-schema ./prisma/schema.prisma \
-  --script
-```
-
-### Review pending migrations
-
-Compare database state to migrations directory:
-
-```bash
-prisma migrate diff \
-  --from-config-datasource \
-  --to-migrations ./prisma/migrations
-```
-
-### Create baseline migration
-
-Compare empty state to current schema:
-
-```bash
-prisma migrate diff \
-  --from-empty \
-  --to-schema ./prisma/schema.prisma \
-  --script > prisma/migrations/0_init/migration.sql
-```
-
-### Check for drift (CI)
-
-Check if database matches schema:
-
-```bash
-prisma migrate diff \
-  --from-config-datasource \
-  --to-schema ./prisma/schema.prisma \
-  --exit-code
-```
-
-## Use Cases
-
-- **Forward-generating migrations**: Creating SQL without `migrate dev`.
-- **Drift detection**: Checking if DB is in sync.
-- **Baselining**: Creating initial migration from existing DB.
-- **Debugging**: Understanding what `migrate dev` would do.

package/template/.agents/skills/data/prisma-cli/references/migrate-reset.md

@@ -1,78 +0,0 @@
-# prisma migrate reset
-
-Resets your database and re-applies all migrations.
-
-## Command
-
-```bash
-prisma migrate reset [options]
-```
-
-## What It Does
-
-1. **Drops** the database (if possible) or deletes all data/tables
-2. **Re-creates** the database
-3. **Applies** all migrations from `prisma/migrations/`
-4. Stops there - run seed and generate explicitly if needed
-
-**Warning: All data will be lost.**
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--force` / `-f` | Skip confirmation prompt |
-| `--schema` | Path to schema file |
-| `--config` | Custom path to your Prisma config file |
-
-## Examples
-
-### Basic reset
-
-```bash
-prisma migrate reset
-```
-
-Prompts for confirmation in interactive terminals.
-
-### Force reset (CI/Automation)
-
-```bash
-prisma migrate reset --force
-```
-
-### With custom schema
-
-```bash
-prisma migrate reset --schema=./custom/schema.prisma
-```
-
-## When to Use
-
-- **Development**: When you want a fresh start
-- **Testing**: Resetting test database before suites
-- **Drift Recovery**: When the database is out of sync and you can't migrate
-
-## Follow-up Steps
-
-Run `prisma generate` and `prisma db seed` explicitly when you need refreshed client output or seed data after a reset.
-
-## Configuration
-
-Configure the seed script in `prisma.config.ts`, then run it explicitly after reset:
-
-```typescript
-export default defineConfig({
-  migrations: {
-    seed: 'tsx prisma/seed.ts',
-  },
-})
-```
-
-Typical workflow:
-
-```bash
-prisma migrate reset --force
-prisma generate
-prisma db seed
-```

package/template/.agents/skills/data/prisma-cli/references/migrate-resolve.md

@@ -1,57 +0,0 @@
-# prisma migrate resolve
-
-Resolves issues with database migrations, such as failed migrations or baselining.
-
-## Command
-
-```bash
-prisma migrate resolve [options]
-```
-
-## What It Does
-
-Updates the `_prisma_migrations` table to manually change the state of a migration. This is a recovery tool.
-
-## Options
-
-You must provide exactly one of `--applied` or `--rolled-back`.
-
-| Option | Description |
-|--------|-------------|
-| `--applied <name>` | Mark a migration as **applied** (success) |
-| `--rolled-back <name>` | Mark a migration as **rolled back** (ignored/failed) |
-| `--schema` | Path to schema file |
-| `--config` | Custom path to your Prisma config file |
-
-## Examples
-
-### Mark as Applied (Baselining)
-
-If you have existing tables and want to initialize migrations without running the SQL:
-
-```bash
-prisma migrate resolve --applied 20240101000000_initial_migration
-```
-
-This tells Prisma "Assume this migration has already run".
-
-### Mark as Rolled Back (Fixing Failures)
-
-If a migration failed (e.g., syntax error) and you fixed the SQL or want to retry:
-
-```bash
-prisma migrate resolve --rolled-back 20240115120000_failed_migration
-```
-
-This tells Prisma "Forget this migration run, let me try applying it again".
-
-## Use Cases
-
-1. **Baselining**: Adopting Prisma Migrate on an existing production database.
-2. **Failed Migrations**: Recovering from a failed `migrate deploy` in production.
-3. **Hotfixes**: reconciling manual database changes (rare).
-
-## References
-
-- [Baselining](https://www.prisma.io/docs/guides/database/developing-with-prisma-migrate/baselining)
-- [Troubleshooting](https://www.prisma.io/docs/guides/database/production-troubleshooting)

package/template/.agents/skills/data/prisma-cli/references/migrate-status.md

@@ -1,65 +0,0 @@
-# prisma migrate status
-
-Checks the status of your database migrations.
-
-## Command
-
-```bash
-prisma migrate status [options]
-```
-
-## What It Does
-
-- Connects to the database
-- Checks the `_prisma_migrations` table
-- Compares applied migrations with local migration files
-- Reports:
-    - **Status**: Database is up-to-date or behind
-    - **Unapplied migrations**: Count of pending migrations
-    - **Missing migrations**: Migrations present in DB but missing locally
-    - **Failed migrations**: Any migrations that failed to apply
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--schema` | Path to schema file |
-| `--config` | Custom path to your Prisma config file |
-
-## Examples
-
-### Check status
-
-```bash
-prisma migrate status
-```
-
-Output example (Up to date):
-```
-Database schema is up to date!
-```
-
-Output example (Pending):
-```
-Following migration have not yet been applied:
-  20240115120000_add_user
-
-To apply migrations in development, run:
-  prisma migrate dev
-
-To apply migrations in production, run:
-  prisma migrate deploy
-```
-
-## When to Use
-
-- **Debugging**: Why is `migrate dev` complaining about drift?
-- **CI/CD**: Verify database state before deploying
-- **Production**: Check if migrations are needed (`migrate deploy`) or if a deployment failed
-
-## Exit Codes
-
-- `0`: Success (may have pending migrations, but command ran successfully)
-- `1`: Error
-
-To check for pending migrations programmatically, you might need to parse the output or use `migrate diff` with exit code flags.

package/template/.agents/skills/data/prisma-cli/references/studio.md

@@ -1,137 +0,0 @@
-# prisma studio
-
-Opens a visual database browser for viewing and editing data.
-
-## Command
-
-```bash
-prisma studio [options]
-```
-
-## What It Does
-
-- Starts a web-based database GUI
-- View all your models and records
-- Create, update, and delete records
-- Filter and sort data
-- Navigate relations
-
-## Options
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `--port` / `-p` | Port to start Studio on | `5555` |
-| `--browser` / `-b` | Browser to open Studio in | System default |
-| `--config` | Custom path to your Prisma config file | - |
-| `--url` | Database connection string (overrides the one in your Prisma config) | - |
-
-## Examples
-
-### Open Studio
-
-```bash
-prisma studio
-```
-
-Opens at http://localhost:5555
-
-### Custom port
-
-```bash
-prisma studio --port 3000
-```
-
-### Specific browser
-
-```bash
-prisma studio --browser firefox
-```
-
-### Don't open browser
-
-```bash
-BROWSER=none prisma studio
-```
-
-Useful for remote servers.
-
-## Features
-
-### View Records
-
-- See all records in table format
-- Pagination for large datasets
-- Column sorting
-
-### Filter Data
-
-- Filter by any field
-- Multiple conditions
-- Relation filtering
-
-### Edit Records
-
-- Click to edit inline
-- Add new records
-- Delete records (with confirmation)
-
-### Navigate Relations
-
-- Click relations to view related records
-- See counts of related items
-- Follow relation links
-
-## Recent Studio Capabilities
-
-Recent Prisma Studio releases added richer editor workflows:
-
-- multi-cell selection and editing
-- full-table search and more intuitive filtering
-- command palette shortcuts
-- dark mode
-- copy selections as Markdown
-- back-relation navigation
-- SQL workflows including raw SQL queries
-
-Some recent builds also expose AI-assisted SQL authoring. Treat these as interactive Studio features rather than a replacement for checked-in migrations or application queries.
-
-## Use Cases
-
-- **Development**: Quick data inspection
-- **Debugging**: Check data state
-- **Testing**: Verify seed data
-- **Demo**: Show data to stakeholders
-
-## Limitations
-
-- Development tool only
-- Not for production use
-- Limited to configured database
-- Prisma Studio in Prisma 7 currently targets PostgreSQL, MySQL, and SQLite first
-- For reproducible application logic, prefer Prisma Client and checked-in SQL scripts
-
-## Common Workflow
-
-1. Run migrations:
-   ```bash
-   prisma migrate dev
-   ```
-
-2. Seed data:
-   ```bash
-   prisma db seed
-   ```
-
-3. Open Studio to verify:
-   ```bash
-   prisma studio
-   ```
-
-4. Make manual edits if needed
-
-## Security Note
-
-Studio provides direct database access. Only run on:
-- Local development machines
-- Secure internal networks
-- Never expose publicly

package/template/.agents/skills/data/prisma-cli/references/validate.md

@@ -1,53 +0,0 @@
-# prisma validate
-
-Validates your Prisma schema file.
-
-## Command
-
-```bash
-prisma validate [options]
-```
-
-## What It Does
-
-- Parses the `schema.prisma` file
-- Checks for syntax errors
-- Validates model definitions, relations, and types
-- Reports any errors or warnings without generating code
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--schema` | Path to schema file |
-| `--config` | Custom path to your Prisma config file |
-
-## Examples
-
-### Validate default schema
-
-```bash
-prisma validate
-```
-
-### Validate specific schema
-
-```bash
-prisma validate --schema=./custom/schema.prisma
-```
-
-### Use in CI
-
-Run `validate` in your CI pipeline to catch schema errors early:
-
-```yaml
-- name: Validate Schema
-  run: npx prisma validate
-```
-
-## Common Errors
-
-- Missing `@relation` fields
-- Invalid types
-- Duplicate model names
-- Syntax errors (missing braces, etc.)