Ask HN: Do you write a technical doc first or just vibe code? When starting a greenfield project, do you take the time to write things down sketching out the domain, architectural direction, and key trade-offs to clarify your thinking upfront, or do you prefer to let the design emerge incrementally as you vibe code? |
This helps me get an idea of what we’re doing. I get pushback and have to be clear and Opus is good at asking questions.
Then I get it to write a set of documents for Claude Code describing the vision, the solution, the technical choices, the testing plan, the validation approach, how to share with colleagues, future ideas and a table of contents.
It's great that we can iterate on the solutions and they become general.
At minimum prepare project specs with features as .md file. I found claude to be useful for this task.
If you’re using Cursor, pick a template from here. https://cursor.directory/rules