When there is a 404 output a message that lets you easily create a new action from command line

Should probably not do this if requesting paths in /public, /js, etc. Also only in dev/test

GET /guides/getting-started/installing
  ▸ Sent 404 (414.0µs)
  ▸ Generate action with: lucky gen.action.from /guides/getting-started/installing

This will then show a wizard with profiled values that can be edited:

Action name (hit enter for 'Guides::GettingStarted::Installing'):
HTTP method (hit enter for 'GET'):
Path (hit enter for /guides/getting-started/installing):

This allows you to use the defaults, but customize for trickier stuff. Like where params are involved you want /users/1 to be /users/:user_id not /users/1

Possible improvements:

I've never done this but would be cool to prefill so you could start with /users/1 but then delete the last bit and add to it. Rather than having to copy/paste the suggestion and edit it

Start by tracing how the framework handles 404 responses in development and test, then inspect the existing lucky gen.action.from command and its wizard entry point. Reproduce the shown request and verify that public or asset paths are excluded, while an application path prints a command with the profiled method and path.