# Claude Design — ten module prompts
Universal AI Institute

These original prompts use the fictional Open Studio project. Outputs vary. Review content, rights, accessibility, and actual exported files. Do not treat a prototype confirmation as a real reservation.

## 1. Meet your design workspace
```text
Create a design artifact for a fictional free community workshop called Open Studio. Audience: adults exploring creative AI for the first time. One page, one clear action: Explore the sessions. Use only these facts: a fictional event; no confirmed date, venue, capacity, or registration link. Mark unknown details as placeholders. Explain the intended reading order before designing. Do not publish or send anything.
```

Keep: A first invitation artifact plus a note identifying its three most important elements.

## 2. Write a visual brief
```text
Design two distinct directions for Open Studio. Audience: first-time adult AI learners. Goal: help them explore a fictional workshop. Fixed content: the event name, a one-sentence purpose, three sample sessions, and one Explore sessions action. Direction A: quiet editorial, warm paper, strong serif headline. Direction B: energetic geometric, bold color blocks, crisp sans serif. Keep the same information in both. Explain the tradeoff of each. Mark dates and venue as unconfirmed.
```

Keep: A six-part brief and two directions with a written selection rationale.

## 3. Build a coherent brand system
```text
Create a compact Open Studio design system. Define ink, paper, accent, and secondary-surface color roles; a two-level type scale; a spacing scale; a button; a card; and a small label. Explain when each role is used. Then apply the same system to an event invitation, a session card, and a square social tile. Preserve the same fictional content and identify any unavailable font substitutes.
```

Keep: A one-page brand kit with three consistent applications.

## 4. Shape typography and layout
```text
Revise the selected Open Studio direction for stronger hierarchy. Make the event name first, the one-sentence promise second, and Explore sessions third. Keep body text comfortable at normal viewing size. Align related elements to a shared grid and group each session title with its description. Preserve the palette and all facts. Explain the three changes you made and why.
```

Keep: A before-and-after layout with three annotated hierarchy decisions.

## 5. Design across artboards
```text
Create desktop and phone artboards for Open Studio using the same brand system and content. Recompose the layout for the phone rather than shrinking the desktop. Keep the main action prominent, allow long session titles to wrap, and avoid horizontal scrolling. Add notes describing stacking, spacing, and navigation behavior. Distinguish the visual mockup from any working responsive implementation.
```

Keep: Two artboards plus explicit layout behavior notes.

## 6. Make a prototype people can try
```text
Build a clickable Open Studio session-selection prototype. States: welcome, choose one of three fictional sessions, review the choice, and confirmation. Require a selection before review. Let the user go back and change the choice. Include a reset action. Do not send data or connect services. Label the result as a simulation and list which production features are not implemented.
```

Keep: A working prototype with happy-path, error-path, and back-navigation test results.

## 7. Iterate with precise feedback
```text
Revise only the hero action label to “Explore sessions.” The current wording is vague for first-time visitors. Preserve the palette, typography, layout, and factual content. Show the revision and explain what changed. Then check that the longer label remains readable on the phone artboard and that its destination still matches its wording.
```

Keep: An annotated revision with a preserved-requirements checklist.

## 8. Create a visual campaign
```text
Create an Open Studio campaign on separate artboards: a desktop event page, an A4 portrait poster, and a square social tile. Share the same palette, typography, and core message. Adapt the composition and amount of text to each format. Leave unconfirmed details visibly marked. Explain recommended export choices for each and list the checks I should perform after opening the actual exported files.
```

Keep: Three coherent assets with an export inspection record.

## 9. Review accessibility and quality
```text
Review this Open Studio artifact for readable text, text contrast, clear labels, visible keyboard focus where interactive, logical reading order, and narrow-screen layout. Check facts against the brief. Separate observed failures from items that require implementation or assistive-technology testing. Propose focused corrections and preserve the existing design direction.
```

Keep: A quality review with evidence, corrections, and explicitly unverified checks.

## 10. Capstone: ship a reviewed design
```text
Help me prepare the final handoff for my Open Studio design package. Inventory the brief, brand kit, desktop and phone artboards, four-state prototype, poster, and social tile. Compare them against the requirements. Report verified checks, failures, and checks not run. Draft a concise handoff note with implementation behavior, source assets, export formats, and remaining work. Do not publish or send the package.
```

Keep: A reviewed design package, evidence log, and implementation handoff.