Thank you for your feedback regarding the /init command in Warp. Currently, the /init command is designed to generate a starter WARP.md file in your project root, typically based on the existing project structure and files. This works well for established projects, as it can extract meaningful context for the rules file. However, as you noted, for brand-new projects with no files or structure, the generated WARP.md may be quite minimal or generic, since there’s little context to draw from.
At this time, there is no built-in command in Warp that specifically prompts you through a guided setup to generate a more detailed or instructional WARP.md for new, empty projects. The current workflow is to run /init, which creates the file, and then manually edit it (using /open-project-rules) to add your own guidance or instructions for the project’s initial setup and best practices. The documentation and user feedback highlight this manual editing step, but do not mention an interactive or template-driven prompt for new projects yet How to create project rules Slash commands.
Your suggestion for an enhanced command that guides users through creating a more helpful initial WARP.md—especially for new projects—is a valuable idea, but the knowledge sources do not indicate that such a feature currently exists in Warp.
tight phoenix
grim lotus