Beyond Autocomplete. Prompts That Architect.

// Start typing a test function
test("should...
// Copilot autocompletes one test at a time

You are a senior QA engineer specializing in comprehensive test coverage.

Generate a complete test suite for: [MODULE/COMPONENT]
Framework: [Vitest / Jest / Playwright]
Code under test: [PASTE CODE]

Generate:
1. Unit tests for every public method
2. Edge cases: null, undefined, empty arrays, boundary values
3. Error path tests (invalid input, network failures)
4. Integration test for the happy path
5. Mock strategy: what to mock vs. what to test live
6. Test data factories using builder pattern

Target: >90% branch coverage. No implementation details in assertions.

# Copilot cannot help — no file context for CI/CD
# You end up Googling "github actions node.js"

You are a DevOps engineer building production CI/CD pipelines.

Create a GitHub Actions workflow for: [PROJECT TYPE]
- Runtime: Node.js 20
- Package manager: [npm / pnpm / bun]
- Deploy target: [Vercel / AWS / Docker]

Generate:
1. CI job: lint, typecheck, test with coverage threshold
2. Security: dependency audit, SAST with CodeQL
3. Build with caching (node_modules + Next.js .next/cache)
4. Deploy job with environment-specific variables
5. Slack/Discord notification on failure
6. Concurrency control (cancel outdated runs)

Use composite actions for reusable steps.

CREATE TABLE users (
  -- Copilot suggests basic columns
  id SERIAL PRIMARY KEY,
  name VARCHAR(255)
)

You are a database architect designing for scale and data integrity.

Design a PostgreSQL schema for: [FEATURE/DOMAIN]
Scale target: [10K / 100K / 1M+ rows]
Access patterns: [LIST PRIMARY QUERIES]

Generate:
1. Tables with appropriate types (uuid vs serial, timestamptz, etc.)
2. Indexes for every access pattern (B-tree, GIN for JSONB/arrays)
3. Foreign keys with ON DELETE behavior
4. Check constraints for business rules
5. Row-level security policies if multi-tenant
6. Migration script (up + down)
7. Seed data for development

Explain index choices and expected query plans.