presentation-design

Turn presentation inputs into governed presentation artifacts.

presentation-design governs the presentation-focused part of the Software Development Lifecycle. It helps teams normalize UI, UX, branding, template, and visual inputs so those constraints can influence broader design work through a reviewable, specialized interpretation step.

What it does

• Reads design packs and related inputs under _hirmos/inputs/presentation-design/.
• Produces normalized presentation runtime context under _hirmos/artifacts/context/presentation-design/.
• Generates governed presentation artifacts such as _hirmos/artifacts/sot/PRESENTATION_SOT.md when applicable.
• Integrates with system-design-agent through specialized hook points.
• Keeps presentation interpretation specialized instead of letting it silently distort broader system design truth.

Why software teams use it

• It gives UI, UX, branding, and template concerns a governed place in the workflow.
• It helps teams avoid mixing specialized presentation interpretation with broader system design ownership.
• It makes downstream design work easier when customer-facing constraints genuinely matter.
• It keeps presentation inputs reviewable instead of buried in scattered files and comments.

Fast mental model

Key outputs

• Normalized presentation runtime context in _hirmos/artifacts/context/presentation-design/
• Governed presentation artifacts such as _hirmos/artifacts/sot/PRESENTATION_SOT.md
• Specialized signals that can enrich system-design-agent when presentation constraints matter

Best fit: projects where presentation constraints are real design inputs and should influence downstream design through a governed interpretation step.

How this extension looks inside HIRMOS

FAQ

When should I use presentation-design?
Use it when UI, UX, branding, template, or other presentation constraints should influence downstream design work.

Where it fits in the Software Development Lifecycle?
– After presentation inputs exist: it starts once design packs, template constraints, branding direction, or customer-facing visual guidance are available.
– Before or alongside system design: it normalizes those presentation signals so broader system design can account for them truthfully.
– At design integration: it provides specialized presentation artifacts that system-design-agent can consume when presentation constraints materially affect the project.

What does it produce?
Its core outputs are normalized presentation artifacts in _hirmos/artifacts/context/presentation-design/ and, when generated, artifacts such as _hirmos/artifacts/sot/PRESENTATION_SOT.md.

Does it replace final system design truth?
No. It owns specialized presentation interpretation, not final integrated project design truth.

Who uses its outputs?
Its outputs are primarily consumed by system-design-agent, maintainers, and teams that need a governed understanding of presentation constraints before design continues.