MakFly

Map entities to API DTOs in API Platform v4 with the Symfony Object Mapper (#[Map], stateOptions) for decoupled input/output contracts

Implement API Platform filters - v4 Parameters API (QueryParameter) and legacy

Configure API Platform v4 resources with explicit operations, pagination, and typed OpenAPI for clean, versioned REST/GraphQL APIs

Secure API Platform resources with security expressions, voters, securityPostValidation, and operation-level access control

Control API Platform serialization with groups,

Master API Platform v4 State Providers and Processors (ProviderInterface/ProcessorInterface) to decouple data retrieval and persistence from entities

Test API Platform resources with ApiTestCase; assert collections, items, filters, JSON schema, and authentication

Evolve API Platform APIs via deprecation (deprecationReason/sunset, RFC 8594/9745), the recommended alternative to versioning; plus path/header strategies

Strengthen Laravel validation/auth/authorization boundaries with explicit failure-safe implementation patterns. Use for api authentication tasks.

Apply production-grade Laravel architecture and execution discipline for focused, low-risk delivery. Use for api resources tasks.

Apply production-grade Laravel architecture and execution discipline for focused, low-risk delivery. Use for bootstrap check tasks.

Apply production-grade Laravel architecture and execution discipline for focused, low-risk delivery. Use for brainstorming tasks.

Implement reliable Laravel async workflows (queues/events/cache) with idempotency and failure handling. Use for cache strategies tasks.

Model and evolve Laravel data structures safely with integrity, performance, and rollout-aware migrations. Use for eloquent casts accessors tasks.

Model and evolve Laravel data structures safely with integrity, performance, and rollout-aware migrations. Use for eloquent relations tasks.

Apply production-grade Laravel architecture and execution discipline for focused, low-risk delivery. Use for executing plans tasks.

Design, implement, audit, or debug authentication and authorization in TanStack Start. Use for sessions, cookies, login, logout, OAuth state and PKCE, password reset, CSRF, rate limiting, protected routes, RBAC, tenant isolation, secret handling, or auth tests.

Prepare, review, or debug TanStack Start production builds and deployments. Use for Vite or Rsbuild output, Cloudflare Workers, Netlify, Railway, Nitro, Node, Docker, Bun, Vercel, Appwrite, environment wiring, assets, CDN caching, early hints, observability, health checks, or production-only failures.

Design, implement, review, or debug TanStack Start middleware and server routes. Use for request middleware, server-function middleware, typed context, global middleware, CSRF, request or response transforms, API endpoints, webhooks, health routes, HTTP methods, headers, status codes, or route conflicts.

Choose, implement, review, or debug TanStack Start rendering behavior. Use for SSR, selective SSR, SPA mode, static prerendering, ISR, streaming, deferred hydration, hydration mismatches, React Server Components, SEO output, or caching interactions.

Design, implement, review, or debug TanStack Start and TanStack Router routes. Use for file-route structure, root routes, layouts, params, search validation, loaders, loader dependencies, navigation, preloading, pending states, errors, not-found behavior, or route-tree generation.

Implement, secure, review, or debug TanStack Start server functions. Use for createServerFn handlers, input validation, request context, redirects, not-found results, raw responses, progressive enhancement, streaming, static functions, cancellation, serialization, or server-only data access.

Create verification plans, write tests, review coverage, or diagnose TanStack Start failures. Use for validators, server functions, middleware, server routes, route loaders, rendering, hydration, production builds, browser scenarios, ESLint Start rules, or evidence-first debugging.

Plan and execute non-trivial TanStack Start features, refactors, upgrades, or migrations. Use when a task crosses routing, server functions, rendering, data access, build configuration, or deployment boundaries and needs an evidence-first implementation plan with explicit verification.

Keep the project's Claude Code / Codex / Gemini CLI configuration in sync with upstream — model catalogue, effort levels, context windows, beta headers, default flags. Use when the user says "mets à jour les modèles", "refresh CLI config", "y a-t-il un nouveau modèle Claude/Codex", "check effort levels", "context window à jour", "1M beta header", or before any release notes / model launch (Anthropic, OpenAI). Runs WebSearch + fetches official docs, diffs against the current catalogue, and patches the source files.

Build, extend, and debug chat UIs using the assistant-ui library and its shadcn registry. Triggers on "assistant-ui", "Thread component", "ChatModelAdapter", "AssistantRuntimeProvider", "useLocalRuntime", or when working on files under src/components/assistant-ui/. Use for adding chat surfaces, wiring a runtime (local/mock/cloud/transport), customizing Thread/ThreadList/AssistantSidebar, or integrating tool-calling and reasoning UIs.

Native browser automation for LLM agents. Use whenever the user asks to scrape, navigate, click, type, screenshot, extract data from a webpage, or run a browser-based workflow. Triggers on "scrape X", "navigate to X", "extract from X", "automate X site", "fill the form on X", "screenshot X", "récupère les annonces X", "ouvre X dans un navigateur", "click on X", "test X website". Avoid for: pure HTTP fetches (use curl), reading static files (use Read), one-off URL inspection (use WebFetch).