UX, visual design, image, video and audio briefs. 43 reviewed prompts for design and media.
Reviews or designs the navigation and key user flows of an app or website and returns a clear structure, problem list and prototype suggestions. Use it when people struggle to find things.
Reviews web or app interfaces, designs, or front-end code for accessibility barriers and reports each issue with severity, affected users, guideline reference, and a concrete fix. Use when reviewing a page, component, or design before release.
Builds a slide-by-slide plan with key messages, visual suggestions and speaker notes for a talk. Use when you know the audience and goal but not how to organize or design the deck.
Creates a design document for one game level: goals, beats, player guidance, encounters, difficulty curve, and playtest questions. Use when planning a new level or reworking one that tests poorly.
Gives a prioritized critique of one app screen from the viewpoints of a designer, a developer and a first-time user. Use it before a design review or hand-off.
Turns a short scene idea into a six-panel storyboard plan with shot type, camera angle, action, emotion and transition for each panel. Use it before sketching, commissioning art or briefing an illustrator.
Checks the colors used across a product or design against a brand palette and proposes a consistent, accessible set. Use it when screens look uneven or after adding new colors.
Compares a built website or app against its design across browsers and screen sizes and returns a prioritized list of visual and interaction defects. Use it before launching a page or release.
Compares your written design system documentation with what the code actually uses and lists undocumented, outdated and conflicting values with fixes. Use when docs and product have drifted apart.
Turns a plain-language description of a system, process or data model into a clean diagram (SVG, diagram code or ASCII) with consistent shapes, labelled arrows and a legend. Use it for docs, proposals and slides.
Describes an interface screenshot as a precise written spec a developer can build from, covering layout, styles, states and responsive behavior. Use when handing a design to engineering without a design file.
Creates a design system specification with the reasoning behind it: color, type, spacing and radius tokens, component state rules, contrast checks and do/don't pairs. Use when starting a product's visual system or making an inconsistent UI coherent.
