---
title: Design prompt — instruction
route: /resources/prompt-design-instruction
lang: en
part_of: Onirion
version: "4.0"
date: 2026-09-22
author: Alexis Boyer
license: CC BY 4.0
one_line: The short layer typed into the design tool alongside the specification and the attachments.
kind: prompt
layers:
  summary: /resources/prompt-design-instruction
  complete_text: /complete.md
  markdown: /resources/prompt-design-instruction.md
---

<!-- source: public-kit/prompts/gate-3-design-instruction.md -->

# The design prompt — short instruction layer

**A method by Alexis Boyer · version 4.0 · September 22, 2026**

**Gate 3.** What gets typed into the design tool alongside the long specification and the attachments. It is quoted here exactly as it appears in [the core guide](/resources/method-guide).

## The text to copy

```text
Design [PRODUCT NAME], [SHORT PRODUCT DESCRIPTION].

Use the attached design system and product documents as source material. Treat the long design prompt as the full specification and this short prompt as the instruction layer.

Do not create a landing page or a concept dashboard. Start with the real product experience: [PRIMARY WORK SURFACE], [SECONDARY WORK SURFACE], [DETAIL WORKSPACE], [DEEPEST WORKFLOW].

Design deeply across the product, not only the top-level pages. Include states, variants, drawers, modals, empty, error and loading states, permission-restricted states, audit views, escalation, handoff, and safe output previews where relevant. Each main flow must be walkable end to end.

Core UX:
- [PRINCIPLE]
- [PRINCIPLE]

Must include:
- [SURFACE / FLOW]
- [CRITICAL STATE MODEL]
- [ROLE / PERMISSION VARIANTS]

Use compact, calm, high-density operational UI. Make it feel production-ready, not like a presentation.
```