presentation-model-designer
Purpose
Design the presentation model for a web feature including pages, components, dynamic states, validation messages, and navigation outcomes.
Expected inputs
- feature scope
- existing routes or pages
- data inputs/outputs
- constraints or stack context
Deliverables
- structured recommendation
- design notes
- risks or gaps
- recommended next artifact
Trigger this skill when
- You are designing or reviewing a web feature rather than a generic backend-only function.
- Request flow, form handling, rendering, state, or navigation decisions materially affect correctness.
- A feature needs clearer boundaries between route handling, server logic, and presentation.
Operating procedure
- Clarify the feature, request path, actors, and current or intended flow.
- Separate facts, assumptions, constraints, and unresolved web-specific risks.
- Prefer concrete request/response behavior over abstract framework talk.
- Explicitly handle invalid, missing, unauthorized, and degraded states where relevant.
- Recommend the next most useful web engineering or testing skill.
Quality gates
- The recommendation respects actual web request boundaries and browser behavior.
- Missing and invalid states are not ignored.
- Assumptions and unresolved decisions are visible.
- Output is specific enough to influence implementation or testing.
Output style
- Be concrete and structured.
- Separate findings, assumptions, and recommendations.
- Prefer explicit tradeoffs over single-answer absolutism.
- Use severity or priority where useful.
Failure modes to avoid
- Do not rely on client-side behavior as the only safeguard.
- Do not blur controller, rendering, validation, and persistence responsibilities.
- Do not describe happy-path behavior only.
- Do not hide uncertainty behind framework-specific jargon.
Minimum output skeleton
## Summary
## Findings or proposal
## Evidence vs assumptions
## Risks or tradeoffs
## Recommended next skill
Handoff targets
- template-rendering-reviewer
- web-navigation-structure-reviewer
- error-page-and-fallback-planner
1---2name: presentation-model-designer3description: presentation-model-designer4---5# presentation-model-designer67## Purpose8Design the presentation model for a web feature including pages, components, dynamic states, validation messages, and navigation outcomes.910## Expected inputs11- feature scope12- existing routes or pages13- data inputs/outputs14- constraints or stack context1516## Deliverables17- structured recommendation18- design notes19- risks or gaps20- recommended next artifact2122## Trigger this skill when23- You are designing or reviewing a web feature rather than a generic backend-only function.24- Request flow, form handling, rendering, state, or navigation decisions materially affect correctness.25- A feature needs clearer boundaries between route handling, server logic, and presentation.2627## Operating procedure281. Clarify the feature, request path, actors, and current or intended flow.292. Separate facts, assumptions, constraints, and unresolved web-specific risks.303. Prefer concrete request/response behavior over abstract framework talk.314. Explicitly handle invalid, missing, unauthorized, and degraded states where relevant.325. Recommend the next most useful web engineering or testing skill.3334## Quality gates35- The recommendation respects actual web request boundaries and browser behavior.36- Missing and invalid states are not ignored.37- Assumptions and unresolved decisions are visible.38- Output is specific enough to influence implementation or testing.3940## Output style41- Be concrete and structured.42- Separate findings, assumptions, and recommendations.43- Prefer explicit tradeoffs over single-answer absolutism.44- Use severity or priority where useful.4546## Failure modes to avoid47- Do not rely on client-side behavior as the only safeguard.48- Do not blur controller, rendering, validation, and persistence responsibilities.49- Do not describe happy-path behavior only.50- Do not hide uncertainty behind framework-specific jargon.5152## Minimum output skeleton53```md54## Summary55## Findings or proposal56## Evidence vs assumptions57## Risks or tradeoffs58## Recommended next skill59```6061## Handoff targets62- template-rendering-reviewer63- web-navigation-structure-reviewer64- error-page-and-fallback-planner