quiver-cli 1.3.1 → 2.0.0

package/template/.agents/skills/code/vercel-react-best-practices/rules/server-dedup-props.md

@@ -1,65 +0,0 @@
----
-title: Avoid Duplicate Serialization in RSC Props
-impact: LOW
-impactDescription: reduces network payload by avoiding duplicate serialization
-tags: server, rsc, serialization, props, client-components
----
-
-## Avoid Duplicate Serialization in RSC Props
-
-**Impact: LOW (reduces network payload by avoiding duplicate serialization)**
-
-RSC→client serialization deduplicates by object reference, not value. Same reference = serialized once; new reference = serialized again. Do transformations (`.toSorted()`, `.filter()`, `.map()`) in client, not server.
-
-**Incorrect (duplicates array):**
-
-```tsx
-// RSC: sends 6 strings (2 arrays × 3 items)
-<ClientList usernames={usernames} usernamesOrdered={usernames.toSorted()} />
-```
-
-**Correct (sends 3 strings):**
-
-```tsx
-// RSC: send once
-<ClientList usernames={usernames} />
-
-// Client: transform there
-'use client'
-const sorted = useMemo(() => [...usernames].sort(), [usernames])
-```
-
-**Nested deduplication behavior:**
-
-Deduplication works recursively. Impact varies by data type:
-
-- `string[]`, `number[]`, `boolean[]`: **HIGH impact** - array + all primitives fully duplicated
-- `object[]`: **LOW impact** - array duplicated, but nested objects deduplicated by reference
-
-```tsx
-// string[] - duplicates everything
-usernames={['a','b']} sorted={usernames.toSorted()} // sends 4 strings
-
-// object[] - duplicates array structure only
-users={[{id:1},{id:2}]} sorted={users.toSorted()} // sends 2 arrays + 2 unique objects (not 4)
-```
-
-**Operations breaking deduplication (create new references):**
-
-- Arrays: `.toSorted()`, `.filter()`, `.map()`, `.slice()`, `[...arr]`
-- Objects: `{...obj}`, `Object.assign()`, `structuredClone()`, `JSON.parse(JSON.stringify())`
-
-**More examples:**
-
-```tsx
-// ❌ Bad
-<C users={users} active={users.filter(u => u.active)} />
-<C product={product} productName={product.name} />
-
-// ✅ Good
-<C users={users} />
-<C product={product} />
-// Do filtering/destructuring in client
-```
-
-**Exception:** Pass derived data when transformation is expensive or client doesn't need original.

package/template/.agents/skills/code/vercel-react-best-practices/rules/server-hoist-static-io.md

@@ -1,149 +0,0 @@
----
-title: Hoist Static I/O to Module Level
-impact: HIGH
-impactDescription: avoids repeated file/network I/O per request
-tags: server, io, performance, next.js, route-handlers, og-image
----
-
-## Hoist Static I/O to Module Level
-
-**Impact: HIGH (avoids repeated file/network I/O per request)**
-
-When loading static assets (fonts, logos, images, config files) in route handlers or server functions, hoist the I/O operation to module level. Module-level code runs once when the module is first imported, not on every request. This eliminates redundant file system reads or network fetches that would otherwise run on every invocation.
-
-**Incorrect (reads font file on every request):**
-
-```typescript
-// app/api/og/route.tsx
-import { ImageResponse } from 'next/og'
-
-export async function GET(request: Request) {
-  // Runs on EVERY request - expensive!
-  const fontData = await fetch(
-    new URL('./fonts/Inter.ttf', import.meta.url)
-  ).then(res => res.arrayBuffer())
-
-  const logoData = await fetch(
-    new URL('./images/logo.png', import.meta.url)
-  ).then(res => res.arrayBuffer())
-
-  return new ImageResponse(
-    <div style={{ fontFamily: 'Inter' }}>
-      <img src={logoData} />
-      Hello World
-    </div>,
-    { fonts: [{ name: 'Inter', data: fontData }] }
-  )
-}
-```
-
-**Correct (loads once at module initialization):**
-
-```typescript
-// app/api/og/route.tsx
-import { ImageResponse } from 'next/og'
-
-// Module-level: runs ONCE when module is first imported
-const fontData = fetch(
-  new URL('./fonts/Inter.ttf', import.meta.url)
-).then(res => res.arrayBuffer())
-
-const logoData = fetch(
-  new URL('./images/logo.png', import.meta.url)
-).then(res => res.arrayBuffer())
-
-export async function GET(request: Request) {
-  // Await the already-started promises
-  const [font, logo] = await Promise.all([fontData, logoData])
-
-  return new ImageResponse(
-    <div style={{ fontFamily: 'Inter' }}>
-      <img src={logo} />
-      Hello World
-    </div>,
-    { fonts: [{ name: 'Inter', data: font }] }
-  )
-}
-```
-
-**Correct (synchronous fs at module level):**
-
-```typescript
-// app/api/og/route.tsx
-import { ImageResponse } from 'next/og'
-import { readFileSync } from 'fs'
-import { join } from 'path'
-
-// Synchronous read at module level - blocks only during module init
-const fontData = readFileSync(
-  join(process.cwd(), 'public/fonts/Inter.ttf')
-)
-
-const logoData = readFileSync(
-  join(process.cwd(), 'public/images/logo.png')
-)
-
-export async function GET(request: Request) {
-  return new ImageResponse(
-    <div style={{ fontFamily: 'Inter' }}>
-      <img src={logoData} />
-      Hello World
-    </div>,
-    { fonts: [{ name: 'Inter', data: fontData }] }
-  )
-}
-```
-
-**Incorrect (reads config on every call):**
-
-```typescript
-import fs from 'node:fs/promises'
-
-export async function processRequest(data: Data) {
-  const config = JSON.parse(
-    await fs.readFile('./config.json', 'utf-8')
-  )
-  const template = await fs.readFile('./template.html', 'utf-8')
-
-  return render(template, data, config)
-}
-```
-
-**Correct (hoists config and template to module level):**
-
-```typescript
-import fs from 'node:fs/promises'
-
-const configPromise = fs
-  .readFile('./config.json', 'utf-8')
-  .then(JSON.parse)
-const templatePromise = fs.readFile('./template.html', 'utf-8')
-
-export async function processRequest(data: Data) {
-  const [config, template] = await Promise.all([
-    configPromise,
-    templatePromise,
-  ])
-
-  return render(template, data, config)
-}
-```
-
-When to use this pattern:
-
-- Loading fonts for OG image generation
-- Loading static logos, icons, or watermarks
-- Reading configuration files that don't change at runtime
-- Loading email templates or other static templates
-- Any static asset that's the same across all requests
-
-When not to use this pattern:
-
-- Assets that vary per request or user
-- Files that may change during runtime (use caching with TTL instead)
-- Large files that would consume too much memory if kept loaded
-- Sensitive data that shouldn't persist in memory
-
-With Vercel's [Fluid Compute](https://vercel.com/docs/fluid-compute), module-level caching is especially effective because multiple concurrent requests share the same function instance. The static assets stay loaded in memory across requests without cold start penalties.
-
-In traditional serverless, each cold start re-executes module-level code, but subsequent warm invocations reuse the loaded assets until the instance is recycled.

package/template/.agents/skills/code/vercel-react-best-practices/rules/server-no-shared-module-state.md

@@ -1,50 +0,0 @@
----
-title: Avoid Shared Module State for Request Data
-impact: HIGH
-impactDescription: prevents concurrency bugs and request data leaks
-tags: server, rsc, ssr, concurrency, security, state
----
-
-## Avoid Shared Module State for Request Data
-
-For React Server Components and client components rendered during SSR, avoid using mutable module-level variables to share request-scoped data. Server renders can run concurrently in the same process. If one render writes to shared module state and another render reads it, you can get race conditions, cross-request contamination, and security bugs where one user's data appears in another user's response.
-
-Treat module scope on the server as process-wide shared memory, not request-local state.
-
-**Incorrect (request data leaks across concurrent renders):**
-
-```tsx
-let currentUser: User | null = null
-
-export default async function Page() {
-  currentUser = await auth()
-  return <Dashboard />
-}
-
-async function Dashboard() {
-  return <div>{currentUser?.name}</div>
-}
-```
-
-If two requests overlap, request A can set `currentUser`, then request B overwrites it before request A finishes rendering `Dashboard`.
-
-**Correct (keep request data local to the render tree):**
-
-```tsx
-export default async function Page() {
-  const user = await auth()
-  return <Dashboard user={user} />
-}
-
-function Dashboard({ user }: { user: User | null }) {
-  return <div>{user?.name}</div>
-}
-```
-
-Safe exceptions:
-
-- Immutable static assets or config loaded once at module scope
-- Shared caches intentionally designed for cross-request reuse and keyed correctly
-- Process-wide singletons that do not store request- or user-specific mutable data
-
-For static assets and config, see [Hoist Static I/O to Module Level](./server-hoist-static-io.md).

package/template/.agents/skills/code/vercel-react-best-practices/rules/server-parallel-fetching.md

@@ -1,83 +0,0 @@
----
-title: Parallel Data Fetching with Component Composition
-impact: CRITICAL
-impactDescription: eliminates server-side waterfalls
-tags: server, rsc, parallel-fetching, composition
----
-
-## Parallel Data Fetching with Component Composition
-
-React Server Components execute sequentially within a tree. Restructure with composition to parallelize data fetching.
-
-**Incorrect (Sidebar waits for Page's fetch to complete):**
-
-```tsx
-export default async function Page() {
-  const header = await fetchHeader()
-  return (
-    <div>
-      <div>{header}</div>
-      <Sidebar />
-    </div>
-  )
-}
-
-async function Sidebar() {
-  const items = await fetchSidebarItems()
-  return <nav>{items.map(renderItem)}</nav>
-}
-```
-
-**Correct (both fetch simultaneously):**
-
-```tsx
-async function Header() {
-  const data = await fetchHeader()
-  return <div>{data}</div>
-}
-
-async function Sidebar() {
-  const items = await fetchSidebarItems()
-  return <nav>{items.map(renderItem)}</nav>
-}
-
-export default function Page() {
-  return (
-    <div>
-      <Header />
-      <Sidebar />
-    </div>
-  )
-}
-```
-
-**Alternative with children prop:**
-
-```tsx
-async function Header() {
-  const data = await fetchHeader()
-  return <div>{data}</div>
-}
-
-async function Sidebar() {
-  const items = await fetchSidebarItems()
-  return <nav>{items.map(renderItem)}</nav>
-}
-
-function Layout({ children }: { children: ReactNode }) {
-  return (
-    <div>
-      <Header />
-      {children}
-    </div>
-  )
-}
-
-export default function Page() {
-  return (
-    <Layout>
-      <Sidebar />
-    </Layout>
-  )
-}
-```

package/template/.agents/skills/code/vercel-react-best-practices/rules/server-parallel-nested-fetching.md

@@ -1,34 +0,0 @@
----
-title: Parallel Nested Data Fetching
-impact: CRITICAL
-impactDescription: eliminates server-side waterfalls
-tags: server, rsc, parallel-fetching, promise-chaining
----
-
-## Parallel Nested Data Fetching
-
-When fetching nested data in parallel, chain dependent fetches within each item's promise so a slow item doesn't block the rest.
-
-**Incorrect (a single slow item blocks all nested fetches):**
-
-```tsx
-const chats = await Promise.all(
-  chatIds.map(id => getChat(id))
-)
-
-const chatAuthors = await Promise.all(
-  chats.map(chat => getUser(chat.author))
-)
-```
-
-If one `getChat(id)` out of 100 is extremely slow, the authors of the other 99 chats can't start loading even though their data is ready.
-
-**Correct (each item chains its own nested fetch):**
-
-```tsx
-const chatAuthors = await Promise.all(
-  chatIds.map(id => getChat(id).then(chat => getUser(chat.author)))
-)
-```
-
-Each item independently chains `getChat` → `getUser`, so a slow chat doesn't block author fetches for the others.

package/template/.agents/skills/code/vercel-react-best-practices/rules/server-serialization.md

@@ -1,38 +0,0 @@
----
-title: Minimize Serialization at RSC Boundaries
-impact: HIGH
-impactDescription: reduces data transfer size
-tags: server, rsc, serialization, props
----
-
-## Minimize Serialization at RSC Boundaries
-
-The React Server/Client boundary serializes all object properties into strings and embeds them in the HTML response and subsequent RSC requests. This serialized data directly impacts page weight and load time, so **size matters a lot**. Only pass fields that the client actually uses.
-
-**Incorrect (serializes all 50 fields):**
-
-```tsx
-async function Page() {
-  const user = await fetchUser()  // 50 fields
-  return <Profile user={user} />
-}
-
-'use client'
-function Profile({ user }: { user: User }) {
-  return <div>{user.name}</div>  // uses 1 field
-}
-```
-
-**Correct (serializes only 1 field):**
-
-```tsx
-async function Page() {
-  const user = await fetchUser()
-  return <Profile name={user.name} />
-}
-
-'use client'
-function Profile({ name }: { name: string }) {
-  return <div>{name}</div>
-}
-```

package/template/.agents/skills/data/prisma-cli/SKILL.md

@@ -1,265 +0,0 @@
----
-name: prisma-cli
-description: Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, validate, format, debug, and mcp. Use for ORM/database CLI workflows, not the Prisma Platform CLI. Triggers on "prisma init", "prisma generate", "prisma migrate", "prisma db", "prisma complete", "prisma studio", "prisma mcp".
-license: MIT
-metadata:
-  author: prisma
-  version: "7.9.1"
----
-
-# Prisma CLI Reference
-
-Reference for Prisma ORM CLI commands. This skill provides guidance on command usage, options, and best practices for current Prisma ORM releases.
-
-## Boundary: Platform and Compute
-
-Do not confuse the stable ORM command (`prisma`) with the public-beta Platform package (`@prisma/cli`, binary `prisma-cli`). Use `prisma-compute` for Compute apps and workspace auth, and `prisma-postgres` for Platform projects and databases.
-
-## When to Apply
-
-Reference this skill when:
-- Setting up a new Prisma project (`prisma init`)
-- Generating Prisma Client (`prisma generate`)
-- Running database migrations (`prisma migrate`)
-- Managing database state (`prisma db push/pull`)
-- Using local development database (`prisma dev`)
-- Debugging Prisma issues (`prisma debug`)
-- Generating shell completions (`prisma complete`)
-
-## Rule Categories by Priority
-
-| Priority | Category | Impact | Prefix |
-|----------|----------|--------|--------|
-| 1 | Setup | HIGH | `init` |
-| 2 | Generation | HIGH | `generate` |
-| 3 | Development | HIGH | `dev` |
-| 4 | Database | HIGH | `db-` |
-| 5 | Migrations | CRITICAL | `migrate-` |
-| 6 | Utility | MEDIUM | `complete`, `studio`, `validate`, `format`, `debug`, `mcp` |
-
-## Command Categories
-
-| Category | Commands | Purpose |
-|----------|----------|---------|
-| Setup | `init` | Initialize a Prisma project |
-| Generation | `generate` | Generate Prisma Client |
-| Validation | `validate`, `format` | Schema validation and formatting |
-| Development | `dev` | Local Prisma Postgres for development |
-| Database | `db pull`, `db push`, `db seed`, `db execute` | Direct database operations |
-| Migrations | `migrate dev`, `migrate deploy`, `migrate reset`, `migrate status`, `migrate diff`, `migrate resolve` | Schema migrations |
-| Utility | `complete`, `studio`, `mcp`, `version`, `debug` | Shell, development, and AI tooling |
-
-## Quick Reference
-
-### Project Setup
-
-```bash
-# Initialize new project (creates prisma/ folder and prisma.config.ts)
-prisma init
-
-# Initialize with specific database
-prisma init --datasource-provider postgresql
-prisma init --datasource-provider mysql
-prisma init --datasource-provider sqlite
-
-# Initialize with Prisma Postgres (cloud)
-prisma init --db
-
-# Initialize with an example model
-prisma init --with-model
-
-```
-
-### Client Generation
-
-```bash
-# Generate Prisma Client
-prisma generate
-
-# Watch mode for development
-prisma generate --watch
-
-# Generate specific generator only
-prisma generate --generator client
-```
-
-### Bun Runtime
-
-When using Bun, always add the `--bun` flag so Prisma runs with the Bun runtime (otherwise it falls back to Node.js because of the CLI shebang):
-
-```bash
-bunx --bun prisma init
-bunx --bun prisma generate
-```
-
-### Local Development Database
-
-```bash
-# Start local Prisma Postgres
-prisma dev
-
-# Start with specific name
-prisma dev --name myproject
-
-# Start in background (detached)
-prisma dev --detach
-
-# List all local instances
-prisma dev ls
-
-# Stop instance
-prisma dev stop myproject
-
-# Remove instance data
-prisma dev rm myproject
-```
-
-### Database Operations
-
-```bash
-# Pull schema from existing database
-prisma db pull
-
-# Push schema to database (no migrations)
-prisma db push
-
-# Seed database
-prisma db seed
-
-# Execute raw SQL
-prisma db execute --file ./script.sql
-```
-
-### Migrations (Development)
-
-```bash
-# Create and apply migration
-prisma migrate dev
-
-# Create migration with name
-prisma migrate dev --name add_users_table
-
-# Create migration without applying
-prisma migrate dev --create-only
-
-# Reset database and apply all migrations
-prisma migrate reset
-```
-
-### Migrations (Production)
-
-```bash
-# Apply pending migrations (CI/CD)
-prisma migrate deploy
-
-# Check migration status
-prisma migrate status
-
-# Compare schemas and generate diff
-prisma migrate diff --from-config-datasource --to-schema schema.prisma --script
-```
-
-### Utility Commands
-
-```bash
-# Open Prisma Studio (database GUI)
-prisma studio
-
-# Start Prisma's MCP server for AI tools
-prisma mcp
-
-# Show version info
-prisma version
-prisma -v
-
-# Debug information
-prisma debug
-
-# Validate schema
-prisma validate
-
-# Format schema
-prisma format
-
-# Generate shell completion code
-prisma complete zsh
-```
-
-## AI Safety Checkpoint
-
-Prisma blocks destructive commands when it detects an AI agent until the agent has obtained explicit user consent. This covers `migrate reset`, `db push --force-reset`, and `db push --accept-data-loss`.
-
-- Explain the exact data-loss impact and ask for consent immediately before running the command.
-- Do not infer consent from earlier or unrelated messages.
-- If automation needs the consent variable, set `PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION` to the user's exact consent message. Do not invent the text.
-- The Prisma MCP server deliberately has no `migrate-reset` tool.
-
-Read `references/agent-safety.md` before any destructive Prisma command.
-
-## Current Prisma CLI Setup
-
-### New Configuration File
-
-Use `prisma.config.ts` for CLI configuration:
-
-```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',
-  },
-  datasource: {
-    url: env('DATABASE_URL'),
-  },
-})
-```
-
-### Current Command Behavior
-
-- Run `prisma generate` explicitly after `migrate dev`, `db push`, or other schema syncs when you need fresh client output
-- Run `prisma db seed` explicitly after `migrate dev` or `migrate reset` when you need seed data
-- Use `prisma db execute --file ...` for raw SQL scripts
-
-### Environment Variables
-
-Load environment variables explicitly in `prisma.config.ts`, commonly with `dotenv`:
-
-```typescript
-// prisma.config.ts
-import 'dotenv/config'
-```
-
-## Rule Files
-
-See individual rule files for detailed command documentation:
-
-```
-references/init.md           - Project initialization
-references/generate.md       - Client generation
-references/dev.md            - Local development database
-references/db-pull.md        - Database introspection
-references/db-push.md        - Schema push
-references/db-seed.md        - Database seeding
-references/db-execute.md     - Raw SQL execution
-references/migrate-dev.md    - Development migrations
-references/migrate-deploy.md - Production migrations
-references/migrate-reset.md  - Database reset
-references/migrate-status.md - Migration status
-references/migrate-resolve.md - Migration resolution
-references/migrate-diff.md   - Schema diffing
-references/studio.md         - Database GUI
-references/mcp.md            - Prisma MCP server
-references/complete.md       - Shell completion generation
-references/agent-safety.md   - AI consent checkpoint for destructive commands
-references/validate.md       - Schema validation
-references/format.md         - Schema formatting
-references/debug.md          - Debug info
-```
-
-## How to Use
-
-Use the command categories above for navigation, then open the specific command reference file you need.