backend-patterns
API design, database operations, error handling, and backend architecture patterns. Use when creating APIs, database schemas, or server-side logic.
What this skill does
# Backend Patterns
Comprehensive patterns for API design, database operations, error handling, and backend architecture.
## When to Use
- Creating API endpoints
- Designing database schemas
- Implementing business logic
- Error handling and logging
- Background jobs and queues
- Caching strategies
## API Design Patterns
### RESTful API Structure
```typescript
// app/api/users/route.ts
export async function GET(request: Request) {
const { searchParams } = new URL(request.url)
const page = parseInt(searchParams.get('page') || '1')
const limit = parseInt(searchParams.get('limit') || '10')
const users = await db.users.findMany({
skip: (page - 1) * limit,
take: limit
})
return NextResponse.json({
success: true,
data: users,
pagination: {
page,
limit,
total: await db.users.count()
}
})
}
export async function POST(request: Request) {
const body = await request.json()
// Validate input
const validated = CreateUserSchema.parse(body)
const user = await db.users.create({ data: validated })
return NextResponse.json(
{ success: true, data: user },
{ status: 201 }
)
}
// app/api/users/[id]/route.ts
export async function GET(
request: Request,
{ params }: { params: { id: string } }
) {
const user = await db.users.findUnique({
where: { id: params.id }
})
if (!user) {
return NextResponse.json(
{ error: 'User not found' },
{ status: 404 }
)
}
return NextResponse.json({ success: true, data: user })
}
export async function PATCH(
request: Request,
{ params }: { params: { id: string } }
) {
const body = await request.json()
const validated = UpdateUserSchema.parse(body)
const user = await db.users.update({
where: { id: params.id },
data: validated
})
return NextResponse.json({ success: true, data: user })
}
export async function DELETE(
request: Request,
{ params }: { params: { id: string } }
) {
await db.users.delete({ where: { id: params.id } })
return NextResponse.json({ success: true }, { status: 204 })
}
```
### Consistent API Response Format
```typescript
type ApiResponse<T> = {
success: true
data: T
meta?: {
pagination?: {
page: number
limit: number
total: number
}
}
} | {
success: false
error: string
details?: any
}
// Success response helper
function successResponse<T>(data: T, meta?: any): Response {
return NextResponse.json({ success: true, data, meta })
}
// Error response helper
function errorResponse(error: string, status: number, details?: any): Response {
return NextResponse.json(
{ success: false, error, details },
{ status }
)
}
// Usage
export async function GET(request: Request) {
try {
const users = await db.users.findMany()
return successResponse(users)
} catch (error) {
return errorResponse('Failed to fetch users', 500)
}
}
```
### API Versioning
```typescript
// app/api/v1/users/route.ts
export async function GET(request: Request) {
// Version 1 implementation
return NextResponse.json({ version: 1, users: [] })
}
// app/api/v2/users/route.ts
export async function GET(request: Request) {
// Version 2 implementation with breaking changes
return NextResponse.json({ version: 2, data: { users: [] } })
}
```
### Request Validation
```typescript
import { z } from 'zod'
const CreateMarketSchema = z.object({
name: z.string().min(3).max(100),
description: z.string().min(10).max(1000),
category: z.enum(['politics', 'sports', 'entertainment', 'crypto']),
endDate: z.string().datetime(),
options: z.array(z.object({
name: z.string().min(1).max(50),
probability: z.number().min(0).max(1).optional()
})).min(2).max(10)
})
export async function POST(request: Request) {
try {
const body = await request.json()
const validated = CreateMarketSchema.parse(body)
// Safe to use validated data
const market = await db.markets.create({ data: validated })
return NextResponse.json({ success: true, data: market })
} catch (error) {
if (error instanceof z.ZodError) {
return NextResponse.json(
{
success: false,
error: 'Validation failed',
details: error.errors
},
{ status: 400 }
)
}
return NextResponse.json(
{ success: false, error: 'Internal server error' },
{ status: 500 }
)
}
}
```
## Database Patterns
### Database Schema Design
```typescript
// Prisma schema example
model User {
id String @id @default(cuid())
email String @unique
name String
passwordHash String
role Role @default(USER)
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
posts Post[]
comments Comment[]
@@index([email])
@@index([createdAt])
}
model Post {
id String @id @default(cuid())
title String
content String @db.Text
published Boolean @default(false)
authorId String
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
author User @relation(fields: [authorId], references: [id], onDelete: Cascade)
comments Comment[]
tags Tag[]
@@index([authorId])
@@index([published])
@@index([createdAt])
@@fulltext([title, content]) // For search
}
model Comment {
id String @id @default(cuid())
content String @db.Text
postId String
authorId String
createdAt DateTime @default(now())
post Post @relation(fields: [postId], references: [id], onDelete: Cascade)
author User @relation(fields: [authorId], references: [id], onDelete: Cascade)
@@index([postId])
@@index([authorId])
}
enum Role {
USER
MODERATOR
ADMIN
}
```
### Transaction Patterns
```typescript
// ❌ WRONG: No transaction (race condition)
export async function transferFunds(fromId: string, toId: string, amount: number) {
const sender = await db.accounts.findUnique({ where: { id: fromId } })
if (sender.balance < amount) {
throw new Error('Insufficient funds')
}
// Race condition: balance could change between these operations
await db.accounts.update({
where: { id: fromId },
data: { balance: sender.balance - amount }
})
await db.accounts.update({
where: { id: toId },
data: { balance: { increment: amount } }
})
}
// ✅ CORRECT: Use transactions
export async function transferFunds(fromId: string, toId: string, amount: number) {
await db.$transaction(async (tx) => {
// Lock sender account for update
const sender = await tx.accounts.findUnique({
where: { id: fromId }
})
if (!sender || sender.balance < amount) {
throw new Error('Insufficient funds')
}
// Atomic updates
await tx.accounts.update({
where: { id: fromId },
data: { balance: { decrement: amount } }
})
await tx.accounts.update({
where: { id: toId },
data: { balance: { increment: amount } }
})
// Create transaction record
await tx.transactions.create({
data: {
fromId,
toId,
amount,
status: 'completed'
}
})
})
}
```
### Query Optimization
```typescript
// ❌ WRONG: N+1 query problem
const users = await db.users.findMany()
for (const user of users) {
user.posts = await db.posts.findMany({
where: { authorId: user.id }
})
}
// ✅ CORRECT: Use includes/eager loading
const users = await db.users.findMany({
include: {
posts: true
}
})
// ✅ CORRECT: Select only needed fields
const users = await db.users.findMany({
select: {
id: true,
name: true,
email: true,
posts: {
select: {
id: true,
title: true,
createdAt: true
}
}
}
})
// ✅ CORRECT: Pagination for large datasets
const posts = await db.posts.findMany({
take: 20,
skip: (page - 1) * 20,
orderBy: { createdAt: 'desc' }
})
```
### Supabase Patterns
```typescript
imRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.