PROJECTS
Vibe Coding Project Ideas
Start with an output someone can use: a saved intake, a stable text tree or editable diagram source. The ideas here borrow the shape of documented tasks, with room to choose your own audience and product.
On this page
Choose an input, preserve an output, define completion
01An intake form needs confirmation, export and invalid-input behavior.
02A tree editor needs explicit undo and persistence.
03A diagram helper needs a clear boundary between visual and text editing.
Idea: a focused intake form
Choose one audience and one submission workflow, such as gathering a brief for a local service. Define required fields, a confirmation state and an export. Test duplicate submissions and invalid input before adding integrations. DummyForms offers a source-documented example of the broader form-building task.
Idea: a text tree editor
Let a user add, reorder and rename nodes, then export a stable text representation. Make undo and persistence explicit. ASCII Tree Editor illustrates this narrow problem; use the original maker record for context instead of copying its product identity.
Idea: a diagram helper
Pick one diagram format and preserve an editable source as the output. Define what can be adjusted visually and what remains textual. TikZ Editor is a useful example of keeping a tool focused rather than attempting a general design suite.
A few more details
How small should the first version be?
Small enough to complete and verify one user journey, including its failure states. Add adjacent features only after that journey works with representative input.

