Design brief
“Make it look good” is not a task you can give to anyone, to a person or to a model. The design brief turns the product you described into a direction a designer can work with. It is also written so that a tool like Claude Design can generate a design system and a detailed prototype from it.
Skill name: discovery-design-atlassian. It reads the
brief, the personas and the
journeys, and the
domain model if it already exists.
How to start it
Section titled “How to start it”In a session that already has the journeys in it:
Let's do the design brief next. What direction would you propose?In a new session, name the skill and say where the pages are:
/discovery-design-atlassian The brief, the personas and the journeys are at<Confluence URL>. Let's work out the design direction.What it works out with you
Section titled “What it works out with you”Section by section, and every section is a proposal that you correct.
| Section | What it wants from you |
|---|---|
| Design goal (north star) | One sentence: the feeling or the outcome the design has to achieve. |
| Brand personality and tone | How the product feels and how it sounds. |
| Design principles | Three to five. They come from what the personas need, not from a style guide. |
| Visual direction | Colours, images, typography and shapes, as a direction. No final values yet. |
| Key screens | From the journeys, each one with the task it has to do. |
| Interaction and platform | Decided here, from the journeys and the personas: mobile first, offline, one-tap actions, whatever applies here. |
| Accessibility | Contrast, touch targets, and never information in colour alone. |
| Brand and assets | What already exists, or nothing at all. |
At the end it checks the screens against the journeys, so the list holds the screens the journeys really need.
Where it lands
Section titled “Where it lands”One Confluence page under the brief. It holds the north star, the brand personality and tone, the design principles, the visual direction, accessibility, and what a generated design should deliver.
The technical frame. It reads this page: the interaction and platform section is a stack decision, because offline needs local storage and a sync path, and a PWA needs a service worker. You decide the shape of the interface here, and the technical frame decides what builds it.