claude-environments

Evaluates and enforces layered middleware architecture for authentication, authorization, and usage enforcement on API routes. Use when building request middleware, enforcing plans or feature access, or attaching request context to downstream handlers.

Selects Cloudflare infrastructure services and LLM providers for a feature set based on dependency chains, storage needs, and settled policy. Use when assigning services (D1, KV, R2, Durable Objects, Queues, Workflows, Workers AI, Hyperdrive), evaluating whether a feature needs Workflows or Durable Objects, choosing between LLM providers, or confirming a build follows the Workers-first topology.

Audits request handling pipelines for explicit data flow, visible transformations, and traceability through logs. Use when designing request handling pipelines, reviewing code for debuggability, tracing production issues, or evaluating whether a new developer could follow the flow.

Audits stateful logic and error handling to verify single sources of truth, boundary-layer error handling, and explicit recovery paths. Use when designing APIs or workflows, refactoring stateful logic, or reviewing retries, fallback behavior, or recovery flows.

Traces feature implementation from UI through handlers, middleware, and storage to identify broken wiring, dead paths, and coverage gaps. Use when reviewing implementation completeness, validating frontend-to-backend wiring, or checking route/handler/middleware/storage consistency.

Audits authentication, authorization, and input validation boundaries to verify trust is established once at entry and not re-checked ad hoc throughout business logic. Use when building or reviewing auth, designing middleware, handling user/webhook/third-party input, or performing security-oriented review.

Designs or builds a page, screen, or component system following the project's strict visual and technical rules. Use when designing a page or screen, building a component system, or reviewing frontend polish and hierarchy.

Evaluates whether work is ready to ship by verifying test evidence, checking for blockers, and confirming deployment readiness. Use when deciding whether work is ready to ship, reviewing critical-path evidence, or preparing deployment.

Breaks a product document or broad request into concrete, dependency-ordered implementation tasks with acceptance criteria. Use when turning product documents into implementation work, refining a broad request, or repairing a weak plan.

Designs or audits caching layers by classifying data staleness tolerance, selecting cache strategies, and verifying write-time invalidation. Use when designing data access patterns, reviewing performance, adding caching to existing systems, or debugging stale data issues.

Evaluates schemas and systems for intrinsic observability — timestamps, status tracking, and usage data that enable monitoring through database queries rather than external tools. Use when designing database schemas, reviewing operational readiness, adding monitoring to existing systems, or evaluating whether production issues can be diagnosed.

Designs or reviews multi-tenant database schemas for tenant isolation, lifecycle tracking, usage auditing, and query safety. Use when designing SaaS schema, reviewing tenant isolation, or adding company or workspace scoping to data models.

Evaluates components, tasks, and modules for size and coupling, then identifies what must be split to maintain small blast radius. Use when planning or reviewing architecture, when a task feels too broad, when a module absorbs unrelated concerns, or when failures are hard to localize.

Evaluates proxy endpoints to ensure they stay thin — routing, logging, and enriching errors without absorbing business logic. Use when building proxy endpoints, forwarding requests between services, or reviewing boundary layers.

Evaluates error responses for actionable context and verifies that user-facing errors guide next steps while service-layer errors remain technical and reusable. Use when designing error responses, reviewing API output quality, building user-facing error handling, or evaluating support burden from poor error messages.

Implements or reviews authentication — password hashing, session management, OAuth integration, and secret comparison — using secure, platform-appropriate primitives. Use when implementing login, adding account creation, reviewing session handling, or integrating OAuth or external identity providers.

Implements or reviews Stripe subscription billing — checkout, webhook handling, subscription state management, caching, and plan enforcement. Use when adding billing, implementing checkout, handling Stripe webhooks, or reviewing subscription state changes.