skulter

Use when an unfamiliar codebase, ticket, specification, design, API, or error must be investigated before deciding implementation scope.

Use when investigating slow rendering, excessive requests, large bundles, expensive computation, or scalability concerns.

Use when code handles authentication, authorization, secrets, untrusted input, uploads, redirects, external requests, or sensitive data.

Use when checking or changing user-facing translations, locale dictionaries, status labels, dates, numbers, or language-specific UI.

Use for React, Next.js, and TypeScript UI work involving components, hooks, server state, forms, or effects.

Use when diagnosing runtime errors, broken UI, failed requests, intermittent behavior, stale data, or performance symptoms.

Use when planning module boundaries, shared ownership, a cross-cutting refactor, or a system change with multiple consumers.

Use when turning verified code, routes, APIs, or decisions into concise technical documentation, IA, runbooks, or diagrams.

Use when the user asks to implement, fix, or refactor code within an established repository.

Use when renaming routes, packages, modules, APIs, configuration keys, or persisted contracts while existing consumers may remain.

Use when preparing a commit message, pull request body, change summary, or explicitly requested Git handoff.

Use when preparing a deployment or release checklist, rollout plan, or production verification.