Resource creation UX

Product requirements

The product had seven resource creation flows, each vibe coded by a different backend engineer.

• Establish a repeatable pattern for creating every type of resource.
• Make it possible to give an agent a PRD and API schema and automate the entire resource creation UX.
• Use protobuf to drive automated field and form validation.

Key decisions

• Use the same layout on the view page, with read-only versions of the configuration fields.
  • Make each section a self-contained form so users can edit incrementally from the view page, making create, read, and update flows repeatable.
• Support nested resource creation within the same route, both for resources this one depends on and for dependent resources or subresources.