Show HN: Formvana – I built a "Cursor for forms" in a week
1 comments
This is a neat angle — “AI session doesn’t end after the first draft” is exactly the missing piece in most form builders.
Two questions from the automation/agent side: 1) Do you store the user’s edits as structured deltas (so the system learns preferences like validation rules, conditional logic patterns, copy tone)? 2) When requirements change, how do you keep the form stable without breaking downstream integrations (webhooks, schema, analytics events)?
I’m working on SkillForge (https://skillforge.expert) — we’re tackling a similar problem but for web workflows: record a process once, then convert it into a reusable skill with checkpoints + retries so it stays maintainable as UIs evolve. Curious if you’ve considered an “audit trail” of changes + checkpoints for form evolution too.
Two questions from the automation/agent side: 1) Do you store the user’s edits as structured deltas (so the system learns preferences like validation rules, conditional logic patterns, copy tone)? 2) When requirements change, how do you keep the form stable without breaking downstream integrations (webhooks, schema, analytics events)?
I’m working on SkillForge (https://skillforge.expert) — we’re tackling a similar problem but for web workflows: record a process once, then convert it into a reusable skill with checkpoints + retries so it stays maintainable as UIs evolve. Curious if you’ve considered an “audit trail” of changes + checkpoints for form evolution too.
I’ve always found building complex forms tedious. Even in 2026, most "AI" form builders are just legacy drag-and-drop tools with a one-shot AI generator slapped on top. You describe a form, it gives you a draft, and then the AI session ends. You’re back to clicking dropdowns for conditional logic and dragging fields.
I wanted the "Cursor experience" for data collection.
So I built Formvana (https://formvana.live). It’s AI-native from the ground up.
The core difference: The chat interface is the product, not a sidebar feature.
Persistent Context: The model holds the entire state of the form. You don't just generate; you iterate. "Add a branching path if they select 'Enterprise'", "Change all email fields to required", or "Restructure the flow to be multi-step"—all through chat.
No Configuration Menus: No more hunting through nested settings to find how to hide a field.
Built in 1 week: Shipped the first version as a solo dev to see if others felt the same frustration.
Tech Stack: Node.js, React.
It's still early, and the logic can sometimes get tricky with very complex schemas, but I'd love to hear what the HN community thinks.
Live Demo: https://formvana.live
I'll be hanging out in the comments to answer any questions!