A screen that looks right and enforces nothing, because the prompt said what it should look like and never said what it must not allow.
Add "Build a screen" from ntent to this repo.
Fetch https://ntent.app/r/f/prompt-build-screen as plain text. Use it as written, replacing anything in [brackets].
It needs a screen inventory and the stages for the entity and a component registry. If this repo does not have them, stop and tell me.
Then check it: The first output has every field, every rule and every stage. You spend your time on density, not on missing pieces.Reads https://ntent.app/r/f/prompt-build-screen
Read the prompt
27 lines
Build a screen for the [ACTOR] portal at route /[actor]/[screen-name].
**Purpose:** [one sentence describing what the user accomplishes here]
**Layout:** [table / card grid / form / dashboard / wizard]
**Data displayed:**
- [Field 1] from [ENTITY] : [text / date / number / one of a fixed list]
- [Field 2] from [ENTITY] : [type]
**Actions available:**
- [Action 1] : [what it does, and which journey step it is]
**Rules to enforce:**
- [BR-NNN]: [the rule] : [disable X when Y, warn when Z]
**Stages shown:**
- [Stage 1] → badge colour: [role], actions available: [list]
- [Stage 2] → badge colour: [role], actions available: [list]
**Interaction patterns:**
- Row click opens [panel / modal / detail page]
- [Action] uses [modal confirm / inline edit / panel form]
**References:**
- Follow the design system for colour roles. Never introduce a colour that is not a token.
- Use components from the registry. Check the component index before building anything new.How to tell it works: The first output has every field, every rule and every stage. You spend your time on density, not on missing pieces.