Re:Show HN: Formvana – I built a "Cursor for forms" in a week
by YaraDori on Sunday February 22, 2026 @05:47PM
(#47115619)
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.