quiver-cli 1.3.1 → 2.0.0

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

@@ -1,27 +0,0 @@
-# AI safety checkpoint for destructive commands
-
-Prisma detects common AI-agent environments and blocks these commands until the user gives explicit consent:
-
-- `prisma migrate reset`
-- `prisma db push --force-reset`
-- `prisma db push --accept-data-loss`
-
-## Required workflow
-
-1. Inspect the target database/config and explain exactly what can be deleted or reset.
-2. Ask the user for explicit consent immediately before the action.
-3. Run the command only after that consent.
-
-For an agent-run subprocess, Prisma accepts the exact consent text through:
-
-```bash
-PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION='<exact user consent message>' prisma migrate reset --force
-```
-
-The value must match the user's message exactly and must not contain added quotes or newlines. Never fabricate consent, reuse an old unrelated approval, or bypass the checkpoint by hiding agent-detection environment variables.
-
-The MCP server has no `migrate-reset` tool. Use the shell command only after consent.
-
-## Reference
-
-- [Prisma ORM 7.9.0 release](https://github.com/prisma/prisma/releases/tag/7.9.0)

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

@@ -1,22 +0,0 @@
-# prisma complete
-
-Prints a shell completion script.
-
-```bash
-prisma complete zsh
-prisma complete bash
-prisma complete fish
-prisma complete powershell
-```
-
-For a direct global CLI installation, load the output using the shell's normal startup mechanism. For example, in zsh:
-
-```bash
-source <(prisma complete zsh)
-```
-
-Prisma also integrates with supported package-manager completion flows. `npx` and `bunx` do not themselves provide completion; invoke the installed binary or the package manager's supported execution form such as `npm exec` or `bun x`.
-
-## Reference
-
-- [Prisma ORM 7.9.0 release](https://github.com/prisma/prisma/releases/tag/7.9.0)

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

@@ -1,78 +0,0 @@
-# prisma db execute
-
-Execute native commands (SQL) to your database.
-
-## Command
-
-```bash
-prisma db execute [options]
-```
-
-## What It Does
-
-- Connects to your database using the configured datasource
-- Executes a script provided via file (`--file`) or stdin (`--stdin`)
-- Useful for running raw SQL, maintenance tasks, or applying diffs from `migrate diff`
-- Not supported on MongoDB
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--file` | Path to a file containing the script to execute |
-| `--stdin` | Use terminal standard input as the script |
-| `--config` | Custom path to your Prisma config file |
-
-## Current Option Surface
-
-`prisma db execute` uses the datasource configured in `prisma.config.ts`. Use `--config` if you need a separate config file for another environment.
-
-## Examples
-
-### Execute from file
-
-```bash
-prisma db execute --file ./script.sql
-```
-
-### Execute from stdin
-
-```bash
-echo "TRUNCATE TABLE User;" | prisma db execute --stdin
-```
-
-### Execute `migrate diff` output
-
-Pipe the output of `migrate diff` directly to the database:
-
-```bash
-prisma migrate diff \
-  --from-empty \
-  --to-schema prisma/schema.prisma \
-  --script \
-| prisma db execute --stdin
-```
-
-## Configuration
-
-Uses `datasource` from `prisma.config.ts`:
-
-```typescript
-export default defineConfig({
-  datasource: {
-    url: env('DATABASE_URL'),
-  },
-})
-```
-
-## Use Cases
-
-- **Manual Migrations**: Applying raw SQL changes
-- **Data Maintenance**: Truncating tables, cleaning up data
-- **Schema Synchronization**: Applying `migrate diff` scripts
-- **Debugging**: Running test queries (though typically not for fetching data)
-
-## Limitations
-
-- **No Data Return**: The command reports success/failure, not query results (rows). Use Prisma Client or `prisma studio` to view data.
-- **SQL Only**: Primarily for SQL databases.

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

@@ -1,185 +0,0 @@
-# prisma db pull
-
-Introspects an existing database and updates your Prisma schema to reflect its structure.
-
-## Command
-
-```bash
-prisma db pull [options]
-```
-
-## What It Does
-
-- Connects to your database
-- Reads the database schema (tables, columns, relations, indexes)
-- Updates `schema.prisma` with corresponding Prisma models
-- For MongoDB, samples data to infer schema
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--force` | Ignore current Prisma schema file |
-| `--print` | Print the introspected Prisma schema to stdout |
-| `--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 |
-| `--composite-type-depth` | Specify the depth for introspecting composite types (default: -1 for infinite, 0 = off) |
-| `--schemas` | Specify the database schemas to introspect |
-| `--local-d1` | Generate a Prisma schema from a local Cloudflare D1 database |
-
-## Examples
-
-### Basic introspection
-
-```bash
-prisma db pull
-```
-
-### Preview without writing
-
-```bash
-prisma db pull --print
-```
-
-Outputs schema to terminal for review.
-
-### Force overwrite
-
-```bash
-prisma db pull --force
-```
-
-Replaces schema file, losing any manual customizations.
-
-## Prerequisites
-
-Configure database connection in `prisma.config.ts`:
-
-```typescript
-import 'dotenv/config'
-import { defineConfig, env } from 'prisma/config'
-
-export default defineConfig({
-  schema: 'prisma/schema.prisma',
-  datasource: {
-    url: env('DATABASE_URL'),
-  },
-})
-```
-
-## Workflow
-
-### Starting from existing database
-
-1. Initialize Prisma:
-   ```bash
-   prisma init
-   ```
-
-2. Configure database URL
-
-3. Pull schema:
-   ```bash
-   prisma db pull
-   ```
-
-4. Review and customize generated schema
-
-5. Generate client:
-   ```bash
-   prisma generate
-   ```
-
-### Syncing changes from database
-
-When database changes are made outside Prisma:
-
-```bash
-prisma db pull
-prisma generate
-```
-
-## Generated Schema Example
-
-Database tables become Prisma models:
-
-```sql
--- Database tables
-CREATE TABLE users (
-  id SERIAL PRIMARY KEY,
-  email VARCHAR(255) UNIQUE NOT NULL,
-  name VARCHAR(100)
-);
-
-CREATE TABLE posts (
-  id SERIAL PRIMARY KEY,
-  title VARCHAR(255) NOT NULL,
-  author_id INTEGER REFERENCES users(id)
-);
-```
-
-Becomes:
-
-```prisma
-model users {
-  id    Int     @id @default(autoincrement())
-  email String  @unique @db.VarChar(255)
-  name  String? @db.VarChar(100)
-  posts posts[]
-}
-
-model posts {
-  id        Int    @id @default(autoincrement())
-  title     String @db.VarChar(255)
-  author_id Int?
-  users     users? @relation(fields: [author_id], references: [id])
-}
-```
-
-## Post-Introspection Cleanup
-
-After `db pull`, consider:
-
-1. **Rename models** to PascalCase:
-   ```prisma
-   model User {  // Was: users
-     @@map("users")
-   }
-   ```
-
-2. **Rename fields** to camelCase:
-   ```prisma
-   authorId Int? @map("author_id")
-   ```
-
-3. **Add relation names** for clarity:
-   ```prisma
-   author User? @relation("PostAuthor", fields: [authorId], references: [id])
-   ```
-
-4. **Add documentation**:
-   ```prisma
-   /// User account information
-   model User {
-     /// Primary email for authentication
-     email String @unique
-   }
-   ```
-
-## MongoDB Introspection
-
-For MongoDB, `db pull` samples documents to infer schema:
-
-```bash
-prisma db pull
-```
-
-May require manual refinement since MongoDB is schemaless.
-
-## Warning
-
-`db pull` overwrites your schema file. Always:
-- Commit current schema before pulling
-- Use `--print` to preview first
-- Backup customizations you want to keep

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

@@ -1,150 +0,0 @@
-# prisma db push
-
-Pushes schema changes directly to database without creating migrations. Ideal for prototyping.
-
-## Command
-
-```bash
-prisma db push [options]
-```
-
-## What It Does
-
-- Syncs your Prisma schema to the database
-- Creates database if it doesn't exist
-- Does NOT create migration files
-- Does NOT track migration history
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--force-reset` | Force a reset of the database before push |
-| `--accept-data-loss` | Ignore data loss warnings |
-| `--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 |
-
-When Prisma detects an AI agent, `--force-reset` and `--accept-data-loss` require explicit user consent. Follow `agent-safety.md`; never infer or fabricate the consent text.
-
-### Follow-up Command
-
-- Run `prisma generate` explicitly when you need refreshed client output
-
-## Examples
-
-### Basic push
-
-```bash
-prisma db push
-```
-
-### Accept data loss
-
-```bash
-prisma db push --accept-data-loss
-```
-
-Required when changes would delete data (dropping columns, etc.)
-
-### Force reset
-
-```bash
-prisma db push --force-reset
-```
-
-Completely resets database and applies schema.
-
-### Full workflow
-
-```bash
-prisma db push
-prisma generate
-```
-
-## When to Use
-
-- **Prototyping** - Rapid schema iteration
-- **Local development** - Quick schema changes
-- **MongoDB** - Primary workflow (migrations not supported)
-- **Testing** - Setting up test databases
-
-## When NOT to Use
-
-- **Production** - Use `migrate deploy`
-- **Team collaboration** - Use migrations for trackable changes
-- **When you need rollback** - Migrations provide history
-
-## Comparison with migrate dev
-
-| Feature | db push | migrate dev |
-|---------|---------|-------------|
-| Creates migration files | No | Yes |
-| Tracks history | No | Yes |
-| Requires shadow database | No | Yes |
-| Speed | Faster | Slower |
-| Rollback capability | No | Yes |
-| Best for | Prototyping | Development |
-
-## MongoDB Workflow
-
-MongoDB doesn't support migrations. Use `db push` exclusively:
-
-```bash
-# Schema changes for MongoDB
-prisma db push
-prisma generate
-```
-
-## Common Patterns
-
-### Prototyping workflow
-
-```bash
-# Make schema changes
-# ...
-
-# Push to database
-prisma db push
-
-# Generate client
-prisma generate
-
-# Test your changes
-# Repeat as needed
-```
-
-### Reset and start fresh
-
-```bash
-prisma db push --force-reset
-prisma db seed
-```
-
-### Handling conflicts
-
-If `db push` can't apply changes safely:
-
-```
-Error: The following changes cannot be applied:
-  - Removing field `email` would cause data loss
-  
-Use --accept-data-loss to proceed
-```
-
-Decide whether data loss is acceptable, then:
-
-```bash
-prisma db push --accept-data-loss
-```
-
-## Transition to Migrations
-
-When ready for production, switch to migrations:
-
-```bash
-# Create baseline migration from current schema
-prisma migrate dev --name init
-```
-
-Then use `migrate dev` for future changes.

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

@@ -1,188 +0,0 @@
-# prisma db seed
-
-Runs your database seed script to populate data.
-
-## Command
-
-```bash
-prisma db seed [options]
-```
-
-## What It Does
-
-- Executes your configured seed script
-- Populates database with initial/test data
-- Runs independently (not auto-run by migrations in v7)
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--config` | Custom path to your Prisma config file |
-| `--` | Pass custom arguments to seed script |
-
-## Configuration
-
-Configure seed script in `prisma.config.ts`:
-
-```typescript
-import 'dotenv/config'
-import { defineConfig, env } from 'prisma/config'
-
-export default defineConfig({
-  schema: 'prisma/schema.prisma',
-  migrations: {
-    path: 'prisma/migrations',
-    seed: 'tsx prisma/seed.ts',  // Your seed command
-  },
-  datasource: {
-    url: env('DATABASE_URL'),
-  },
-})
-```
-
-### Common seed commands
-
-```typescript
-// TypeScript with tsx
-seed: 'tsx prisma/seed.ts'
-
-// TypeScript with ts-node
-seed: 'ts-node prisma/seed.ts'
-
-// JavaScript
-seed: 'node prisma/seed.js'
-```
-
-## Seed Script Example
-
-```typescript
-// prisma/seed.ts
-import { PrismaClient } from '../generated/client'
-
-const prisma = new PrismaClient()
-
-async function main() {
-  // Create users
-  const alice = await prisma.user.upsert({
-    where: { email: 'alice@prisma.io' },
-    update: {},
-    create: {
-      email: 'alice@prisma.io',
-      name: 'Alice',
-      posts: {
-        create: {
-          title: 'Hello World',
-          published: true,
-        },
-      },
-    },
-  })
-
-  const bob = await prisma.user.upsert({
-    where: { email: 'bob@prisma.io' },
-    update: {},
-    create: {
-      email: 'bob@prisma.io',
-      name: 'Bob',
-    },
-  })
-
-  console.log({ alice, bob })
-}
-
-main()
-  .then(async () => {
-    await prisma.$disconnect()
-  })
-  .catch(async (e) => {
-    console.error(e)
-    await prisma.$disconnect()
-    process.exit(1)
-  })
-```
-
-## Examples
-
-### Run seed
-
-```bash
-prisma db seed
-```
-
-### With custom arguments
-
-```bash
-prisma db seed -- --environment development
-```
-
-Arguments after `--` are passed to your seed script.
-
-## Current Workflow
-
-Run seeding explicitly after migrations when you need seed data:
-
-```bash
-prisma migrate dev --name init
-prisma generate
-prisma db seed  # Must run explicitly
-```
-
-## Idempotent Seeding
-
-Use `upsert` to make seeds re-runnable:
-
-```typescript
-// Good: Can run multiple times
-await prisma.user.upsert({
-  where: { email: 'alice@prisma.io' },
-  update: {},  // Don't change existing
-  create: { email: 'alice@prisma.io', name: 'Alice' },
-})
-
-// Bad: Fails on second run
-await prisma.user.create({
-  data: { email: 'alice@prisma.io', name: 'Alice' },
-})
-```
-
-## Common Patterns
-
-### Development reset
-
-```bash
-prisma migrate reset --force
-prisma db seed
-```
-
-### Conditional seeding
-
-```typescript
-// prisma/seed.ts
-const count = await prisma.user.count()
-if (count === 0) {
-  // Only seed if empty
-  await seedUsers()
-}
-```
-
-### Environment-specific seeds
-
-```typescript
-// prisma/seed.ts
-const env = process.env.NODE_ENV || 'development'
-
-if (env === 'development') {
-  await seedDevData()
-} else if (env === 'test') {
-  await seedTestData()
-}
-```
-
-## Best Practices
-
-1. Use `upsert` for idempotent seeds
-2. Keep seeds focused and minimal
-3. Use realistic but fake data
-4. Document required seed data
-5. Version control your seed scripts

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

@@ -1,46 +0,0 @@
-# prisma debug
-
-Prints information helpful for debugging and bug reports.
-
-## Command
-
-```bash
-prisma debug [options]
-```
-
-## What It Does
-
-Outputs details about your Prisma environment, including:
-- Prisma CLI version
-- Prisma Client version (if installed)
-- Engine binaries (Query Engine, Migration Engine, etc.)
-- Platform information (OS, Architecture)
-- Node.js version
-- Configured datasource provider
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--schema` | Path to schema file |
-| `--config` | Custom path to your Prisma config file |
-
-## Example Output
-
-```
-prisma               : 7.3.0
-@prisma/client       : 7.3.0
-Operating System     : darwin
-Architecture         : arm64
-Node.js              : v20.10.0
-TypeScript           : 5.3.3
-Query Compiler       : enabled
-PSL                  : ...
-Schema Engine        : ...
-```
-
-## When to Use
-
-- **Troubleshooting**: Checking version mismatches
-- **Reporting Issues**: Including environment info in GitHub issues
-- **Verifying Installation**: Ensuring correct binaries are downloaded