Agents

What Are Agents

Agents are specialized subprocesses that Claude delegates tasks to. Each agent has a focused role, specific tools it can use, and a model it runs on. They live in .claude/agents/.

Available Agents

typescript-reviewer

Model: Sonnet | Tools: Read, Grep, Glob, Bash

Reviews TypeScript code for type safety, async correctness, and Vue 3 patterns.

Checks:

• any usage without justification
• Non-null assertion abuse (value!)
• Unhandled promise rejections
• shallowRef direct mutation (will not trigger reactivity)
• Computed with side effects
• Reactive destructuring (loses reactivity)
• Missing return types on exports

Runs first: vue-tsc --noEmit and pnpm lint. Stops if either fails.

When to use: after writing or modifying TypeScript or Vue files.

code-reviewer

Model: Sonnet | Tools: Read, Grep, Glob, Bash

General code review covering security, quality, Vue and Nuxt patterns, PowerSync/Supabase patterns.

Checks:

• Security: secrets, auth checks, input validation
• Code quality: function size, nesting depth, dead code
• Vue patterns: computed purity, reactive destructuring, Lazy prefix
• PowerSync/Supabase patterns: RLS policies + sync rules, client-generated UUID ids, optimistic write + rollback
• Performance: bundle size, N+1 queries

Output format: findings grouped by severity (CRITICAL, HIGH, MEDIUM, LOW) with a summary table and verdict (APPROVE, WARNING, BLOCK).

When to use: after finishing a feature or before opening a PR.

build-error-resolver

Model: Sonnet | Tools: Read, Write, Edit, Bash, Grep, Glob

Fixes build and TypeScript errors with minimal diffs. No refactoring, no architecture changes.

Handles:

• Type inference errors, missing types
• Import and module resolution
• Nuxt auto-import issues (npx nuxi prepare)
• PowerSync schema mismatches (AppSchema.ts) + Supabase migration errors
• Vue template type errors

When to use: build broke, vue-tsc failing, need a quick fix.

planner

Model: Opus | Tools: Read, Grep, Glob

Creates detailed implementation plans for complex features.

Plan structure:

1. Requirements analysis
2. Architecture review (affected components, stores, Supabase/PowerSync data flow)
3. Step breakdown with file paths, dependencies, risks
4. Phased implementation (backend, store, UI)
5. Testing strategy

Finapp specifics: considers offline support, optimistic UI, client-generated UUIDs, shallowRef stores, Supabase migrations + PowerSync sync rules, i18n, premium layer impact.

When to use: before starting any non-trivial feature or refactoring.