quiver-cli 1.3.1 → 2.0.0

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

@@ -1,157 +0,0 @@
-# prisma dev
-
-Starts a local Prisma Postgres database for development. Provides a PostgreSQL-compatible database that runs entirely on your machine.
-
-## Command
-
-```bash
-prisma dev [options]
-```
-
-## What It Does
-
-- Starts a local PostgreSQL-compatible database
-- Runs in your terminal or as a background process
-- Perfect for development and testing
-- Easy migration to Prisma Postgres cloud in production
-
-## Options
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `--name` / `-n` | Name for the database instance | `default` |
-| `--port` / `-p` | HTTP server port | `51213` |
-| `--db-port` / `-P` | Database server port | `51214` |
-| `--shadow-db-port` | Shadow database port (for migrations) | `51215` |
-| `--detach` / `-d` | Run in background | `false` |
-| `--debug` | Enable debug logging | `false` |
-
-## Examples
-
-### Start local database
-
-```bash
-prisma dev
-```
-
-Interactive mode with keyboard shortcuts:
-- `q` - Quit
-- `h` - Show HTTP URL  
-- `t` - Show TCP URLs
-
-### Named instance
-
-```bash
-prisma dev --name myproject
-```
-
-Useful for multiple projects.
-
-### Background mode
-
-```bash
-prisma dev --detach
-```
-
-Frees your terminal for other commands.
-
-### Custom ports
-
-```bash
-prisma dev --port 5000 --db-port 5432
-```
-
-## Instance Management
-
-### List all instances
-
-```bash
-prisma dev ls
-```
-
-Shows all local Prisma Postgres instances with status.
-
-### Start existing instance
-
-```bash
-prisma dev start myproject
-```
-
-Starts a previously created instance in background.
-
-### Stop instance
-
-```bash
-prisma dev stop myproject
-```
-
-### Stop with glob pattern
-
-```bash
-prisma dev stop "myproject*"
-```
-
-Stops all instances matching pattern.
-
-### Remove instance
-
-```bash
-prisma dev rm myproject
-```
-
-Removes instance data from filesystem.
-
-### Force remove (stops first)
-
-```bash
-prisma dev rm myproject --force
-```
-
-## Configuration
-
-Configure your `prisma.config.ts` to use local Prisma Postgres:
-
-```typescript
-import 'dotenv/config'
-import { defineConfig, env } from 'prisma/config'
-
-export default defineConfig({
-  schema: 'prisma/schema.prisma',
-  migrations: {
-    path: 'prisma/migrations',
-  },
-  datasource: {
-    // Local Prisma Postgres URL (from prisma dev output)
-    url: env('DATABASE_URL'),
-  },
-})
-```
-
-## Workflow
-
-1. Start local database:
-   ```bash
-   prisma dev
-   ```
-
-2. In another terminal, run migrations:
-   ```bash
-   prisma migrate dev
-   ```
-
-3. Generate client:
-   ```bash
-   prisma generate
-   ```
-
-4. Run your application
-
-## Production Migration
-
-When ready for production, switch to Prisma Postgres cloud:
-
-```bash
-prisma init --db
-```
-
-Update your `DATABASE_URL` to the cloud connection string.

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

@@ -1,48 +0,0 @@
-# prisma format
-
-Formats your Prisma schema file.
-
-## Command
-
-```bash
-prisma format [options]
-```
-
-## What It Does
-
-- Fixes formatting (indentation, spacing)
-- Adds missing back-relations (e.g., adds the other side of a relation)
-- Adds missing relation arguments (e.g., `fields`, `references`)
-- Sorts fields and attributes (opinionated)
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--schema` | Path to schema file |
-| `--config` | Custom path to your Prisma config file |
-
-## Examples
-
-### Format default schema
-
-```bash
-prisma format
-```
-
-### Format specific schema
-
-```bash
-prisma format --schema=./custom/schema.prisma
-```
-
-## Behavior
-
-`prisma format` modifies the file in place. It is equivalent to "Prettier for Prisma schemas" but also has semantic understanding to fix/add missing schema definitions.
-
-## Use in Editor
-
-Most Prisma editor extensions (VS Code, WebStorm) run `prisma format` automatically on save. This command is useful for:
-- CI pipelines (check formatting)
-- CLI-based workflows
-- Fixing large schema refactors

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

@@ -1,173 +0,0 @@
-# prisma generate
-
-Generates assets based on the generator blocks in your Prisma schema, most commonly Prisma Client.
-
-## Command
-
-```bash
-prisma generate [options]
-```
-
-## Bun Runtime
-
-If you're using Bun, run Prisma with `bunx --bun` so it doesn't fall back to Node.js:
-
-```bash
-bunx --bun prisma generate
-```
-
-## What It Does
-
-1. Reads your `schema.prisma` file
-2. Generates a customized Prisma Client based on your models
-3. Outputs to the directory specified in the generator block
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--schema` | Custom path to your Prisma schema |
-| `--config` | Custom path to your Prisma config file |
-| `--sql` | Generate typed sql module |
-| `--watch` | Watch the Prisma schema and rerun after a change |
-| `--generator` | Generator to use (may be provided multiple times) |
-| `--no-hints` | Hides the hint messages but still outputs errors and warnings |
-| `--require-models` | Do not allow generating a client without models |
-
-## Examples
-
-### Basic generation
-
-```bash
-prisma generate
-```
-
-### Watch mode (development)
-
-```bash
-prisma generate --watch
-```
-
-Auto-regenerates when `schema.prisma` changes.
-
-### Specific generator
-
-```bash
-prisma generate --generator client
-```
-
-### Multiple generators
-
-```bash
-prisma generate --generator client --generator zod_schemas
-```
-
-### Typed SQL generation
-
-```bash
-prisma generate --sql
-```
-
-## Schema Configuration
-
-```prisma
-generator client {
-  provider = "prisma-client"
-  output   = "../generated"
-}
-```
-
-### Current Generator Behavior
-
-- `prisma-client` is the standard generator
-- `output` is required when using `prisma-client`
-- `prisma-client` supports both ESM and CommonJS via `moduleFormat`
-- `compilerBuild` supports `fast` and `small` query compiler artifacts
-- Use TypeScript `satisfies` for typed query fragments with `prisma-client`
-- Import Prisma Client from your generated output path, for example:
-
-```typescript
-import { PrismaClient } from '../generated/prisma/client'
-```
-
-### Compiler Build Tuning
-
-Use `compilerBuild` when you need to trade artifact size against the default build:
-
-```prisma
-generator client {
-  provider      = "prisma-client"
-  output        = "../generated"
-  compilerBuild = "small"
-}
-```
-
-- `fast` is the default build for most targets
-- `small` is useful for size-constrained targets
-- Prisma defaults `vercel-edge` targets to `small`
-
-## Common Patterns
-
-### After schema changes
-
-```bash
-prisma migrate dev --name my_migration
-prisma generate
-```
-
-Run `prisma generate` whenever you need refreshed client code after schema-changing commands.
-
-### CI/CD pipeline
-
-```bash
-prisma generate
-```
-
-Run before building your application.
-
-### Multiple generators
-
-```prisma
-generator client {
-  provider = "prisma-client"
-  output   = "../generated"
-}
-
-generator zod {
-  provider = "zod-prisma-types"
-  output   = "../generated/zod"
-}
-```
-
-```bash
-prisma generate  # Runs all generators
-```
-
-## Output Structure
-
-After running `prisma generate`, your output directory contains:
-
-```
-generated/
-├── browser.ts
-├── client.ts
-├── commonInputTypes.ts
-├── models/
-├── enums.ts
-├── models.ts
-└── ...
-```
-
-Import the client:
-
-```typescript
-import { PrismaClient, Prisma } from '../generated/prisma/client'
-```
-
-Import browser-safe types:
-
-```typescript
-import { Prisma } from '../generated/prisma/browser'
-import { Role } from '../generated/prisma/enums'
-import type { UserModel } from '../generated/prisma/models/User'
-```

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

@@ -1,139 +0,0 @@
-# prisma init
-
-Bootstraps a fresh Prisma ORM project in the current directory.
-
-## Command
-
-```bash
-prisma init [options]
-```
-
-## Bun Runtime
-
-If you're using Bun, run Prisma with `bunx --bun` so it doesn't fall back to Node.js:
-
-```bash
-bunx --bun prisma init
-```
-
-## What It Creates
-
-- `prisma/schema.prisma` - Your Prisma schema file
-- `prisma.config.ts` - TypeScript configuration for Prisma CLI
-- `.env` - Environment variables (DATABASE_URL)
-- `.gitignore` - Ensures `.env` is ignored and appends the generated client path
-
-## Options
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `--datasource-provider` | Database provider: `postgresql`, `mysql`, `sqlite`, `sqlserver`, `mongodb`, `cockroachdb` | `postgresql` |
-| `--db` | Provisions a fully managed Prisma Postgres database on the Prisma Data Platform | - |
-| `--url` | Define a custom datasource url | - |
-| `--generator-provider` | Define the generator provider to use | `prisma-client` |
-| `--output` | Define Prisma Client generator output path to use | - |
-| `--preview-feature` | Define a preview feature to use | - |
-| `--with-model` | Add example model to created schema file | - |
-| `--no-skills` | Skip the best-effort installation of Prisma agent skills | - |
-
-`prisma init` attempts to install `prisma/skills` for detected agents. This is best-effort and does not make project initialization fail. Use `--no-skills` in minimal or controlled environments.
-
-## Examples
-
-### Basic initialization
-
-```bash
-prisma init
-```
-
-Creates a PostgreSQL project setup.
-
-### SQLite project
-
-```bash
-prisma init --datasource-provider sqlite
-```
-
-### MySQL with custom URL
-
-```bash
-prisma init --datasource-provider mysql --url "mysql://user:password@localhost:3306/mydb"
-```
-
-### Prisma Postgres (cloud)
-
-```bash
-prisma init --db
-```
-
-Opens browser for authentication, creates cloud database instance.
-
-### Add an example model
-
-```bash
-prisma init --with-model
-```
-
-Adds a starter model to the generated schema.
-
-### With preview features
-
-```bash
-prisma init --preview-feature relationJoins --preview-feature fullTextSearch
-```
-
-## Generated Schema
-
-```prisma
-generator client {
-  provider = "prisma-client"
-  output   = "../generated/prisma"
-}
-
-datasource db {
-  provider = "postgresql"
-}
-```
-
-## Generated Config (Node.js default)
-
-```typescript
-// prisma.config.ts
-import "dotenv/config";
-import { defineConfig } from 'prisma/config'
-
-export default defineConfig({
-  schema: 'prisma/schema.prisma',
-  migrations: {
-    path: 'prisma/migrations',
-  },
-  datasource: {
-    url: process.env['DATABASE_URL'],
-  },
-})
-```
-
-## Generated Config (Bun)
-
-```typescript
-import { defineConfig, env } from 'prisma/config'
-
-export default defineConfig({
-  schema: 'prisma/schema.prisma',
-  migrations: {
-    path: 'prisma/migrations',
-  },
-  datasource: {
-    url: env('DATABASE_URL'),
-  },
-})
-```
-
-## Next Steps After Init
-
-1. Configure `DATABASE_URL` in `.env` (and let `prisma.config.ts` read it)
-2. Define your models in `prisma/schema.prisma`
-3. Run `prisma dev` for local development or connect to remote DB
-4. Run `prisma migrate dev` to create migrations
-5. Run `prisma generate` to generate Prisma Client
-6. Run `prisma db seed` explicitly if you want seed data

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

@@ -1,39 +0,0 @@
-# prisma mcp
-
-Starts Prisma's MCP server for AI development tools.
-
-## Command
-
-```bash
-prisma mcp
-```
-
-## What It Does
-
-- Starts a Model Context Protocol (MCP) server for your Prisma project
-- Exposes Prisma schema and database context to compatible AI tools
-- Helps AI assistants understand models, generate queries, and suggest migrations
-
-## Usage
-
-```bash
-prisma mcp
-```
-
-## Typical Use Cases
-
-- Connect Prisma to ChatGPT, Claude, or other MCP-aware tools
-- Give an AI assistant access to your Prisma schema structure
-- Help an agent propose queries, schema updates, and migration steps with project context
-
-## Notes
-
-- Run this from the project that contains your Prisma schema and `prisma.config.ts`
-- The command is separate from Prisma Studio and does not open a browser UI
-- The MCP server exposes `migrate-status`, `migrate-dev`, and Prisma Studio tooling. It does not expose the destructive `migrate-reset` tool; do not claim it is available or try to bypass that safety boundary.
-- For destructive shell commands, follow `agent-safety.md` and obtain explicit user consent.
-
-## References
-
-- [Prisma CLI `mcp` command](https://docs.prisma.io/docs/cli/mcp)
-- [Prisma MCP Server](https://www.prisma.io/docs/ai/tools/chatgpt)

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

@@ -1,127 +0,0 @@
-# prisma migrate deploy
-
-Applies pending migrations in production/staging environments.
-
-## Command
-
-```bash
-prisma migrate deploy
-```
-
-## What It Does
-
-- Applies all pending migrations from `prisma/migrations/`
-- Updates `_prisma_migrations` table
-- Does NOT generate new migrations
-- Does NOT run seed scripts
-- Safe for CI/CD and production
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--schema` | Custom path to your Prisma schema |
-| `--config` | Custom path to your Prisma config file |
-
-## When to Use
-
-- Production deployments
-- Staging environments  
-- CI/CD pipelines
-- Any non-development environment
-
-## Examples
-
-### Basic deployment
-
-```bash
-prisma migrate deploy
-```
-
-### In CI/CD pipeline
-
-```yaml
-# GitHub Actions example
-- name: Apply migrations
-  run: npx prisma migrate deploy
-  env:
-    DATABASE_URL: ${{ secrets.DATABASE_URL }}
-```
-
-### Docker deployment
-
-```dockerfile
-# Run migrations before starting app
-CMD npx prisma migrate deploy && node dist/index.js
-```
-
-## Comparison with migrate dev
-
-| Feature | migrate dev | migrate deploy |
-|---------|-------------|----------------|
-| Creates migrations | Yes | No |
-| Applies migrations | Yes | Yes |
-| Detects drift | Yes | No |
-| Prompts for input | Yes | No |
-| Uses shadow database | Yes | No |
-| Safe for production | No | Yes |
-| Resets on issues | Prompts | Fails |
-
-## Production Workflow
-
-1. **Development**: Create migrations locally
-   ```bash
-   prisma migrate dev --name add_feature
-   ```
-
-2. **Commit**: Include migration files in version control
-   ```bash
-   git add prisma/migrations
-   git commit -m "Add feature migration"
-   ```
-
-3. **Deploy**: Apply in production
-   ```bash
-   prisma migrate deploy
-   ```
-
-## Error Handling
-
-### Failed migration
-
-If a migration fails, `migrate deploy` exits with error. The failed migration is marked as failed in `_prisma_migrations`.
-
-To fix:
-1. Resolve the issue (fix SQL, database state, etc.)
-2. Mark as resolved: `prisma migrate resolve --applied <migration_name>`
-3. Re-run: `prisma migrate deploy`
-
-### Check status first
-
-```bash
-prisma migrate status
-```
-
-Shows pending and applied migrations before deploying.
-
-## Configuration
-
-Ensure `prisma.config.ts` has the production database URL:
-
-```typescript
-import 'dotenv/config'
-import { defineConfig, env } from 'prisma/config'
-
-export default defineConfig({
-  datasource: {
-    url: env('DATABASE_URL'),
-  },
-})
-```
-
-## Best Practices
-
-1. Always run `migrate status` before `migrate deploy` in CI
-2. Have a rollback plan (backup before migrations)
-3. Test migrations in staging first
-4. Never use `migrate dev` in production