superpowers-sage:acorn-routes

To create Acorn routes safely, define them in routes/web.php or routes/api.php and use route-group prefixing to avoid rewrite rule conflicts. This prevents breaking WordPress permalink behavior while adding custom endpoints.

Acorn routes can return JSON API responses by using controller classes structured for APIs and ensuring clients send the Accept: application/json header. The Skill generates API controllers to handle these responses correctly with proper middleware.

Acorn routing supports optional route model binding for both Eloquent models and WordPress posts, including slug bindings. This allows automatic resolution of models from route parameters within your controller methods.

Generate a resource controller for Acorn routes by running the create-controller.sh script with the desired controller name and the --api flag. This creates a structured controller class for your JSON endpoints.

Acorn routes support Laravel middleware chains for authentication and access control, along with rate limiting and token auth. This secures your custom JSON endpoints within the WordPress environment.

Controller-based Acorn routes must be cache-safe to function after caching. Verify your routes using Lando acorn route:list and route:cache commands, ensuring all routes are properly named for reliable redirects.