Solo Developer Workflow

Store in memory: Our project is a SaaS dashboard built with Next.js 14,
Tailwind CSS, Prisma with PostgreSQL, and deployed on Vercel.
Authentication uses NextAuth with Google OAuth.
Category: architecture, Tags: stack, nextjs, prisma, vercel

Store in memory: We use functional components only, no classes.
All API routes return { success: boolean, data?: T, error?: string }.
We use zod for all input validation.
Category: coding-rules, Tags: react, api, validation

Store in memory: Never use any type. Never use inline styles.
Never use console.log in production code — use our logger utility.
Category: anti-patterns, Tags: typescript, style

Query memory for recent architecture decisions and coding rules.

Spawn the analyst agent to analyze the impact of adding
real-time notifications to our dashboard.

Spawn the architect agent to design the WebSocket
integration for real-time updates.

Spawn the developer agent to implement the notification
service based on the architect's design.

Spawn the reviewer agent to review the changes in
src/services/notifications/ for security and performance.

Store in memory: Implemented WebSocket notifications using Socket.io.
The NotificationService in src/services/notifications/service.ts
handles connection management. Events are typed in src/types/events.ts.
Category: service-context, Tags: websocket, notifications, socket-io

Create a skill called "pr-checklist" that reviews code against:
1. Our TypeScript coding rules (query memory for coding-rules)
2. Security best practices
3. Performance considerations
4. Test coverage requirements

Invoke the pr-checklist skill on the auth middleware changes.

Create a pipeline called "morning-briefing":
1. Trigger (schedule, cron: "0 9 * * 1-5")
2. Agent (manager) — summarize kanban tasks in progress
3. Memory Search — find recent architecture decisions
4. Transform — combine into a morning brief
5. Output (log)