CakePHP Controllers

When to use

• The user is adding or editing a CakePHP controller action that responds to a routed request.
• The user wants to share request-handling logic (auth, flash, pagination) across controllers via a component.
• The user needs to read request data (query, post, params) or build a response (redirect, JSON, status) in a CakePHP controller.

When NOT to use

• Do not put app-wide request concerns (CORS, HTTPS enforcement, body parsing) in a controller; handle them in PSR-15 middleware in the application stack.
• Do not use this skill for Symfony, Laravel, or Laminas controllers; the action, component, and ServerRequest API is CakePHP specific.

Core guidance