writing-design-prompt

Translate vague UI ideas into structured design prompts and briefs.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Conradmaker/copilot-cockpit --skill writing-design-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-design-prompt
Source: https://github.com/Conradmaker/copilot-cockpit/tree/main/.github/skills/writing-design-prompt
Command: npx skills add https://github.com/Conradmaker/copilot-cockpit --skill writing-design-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate ambiguous design directions, research findings, and vague UI ideas into clear, actionable design prompts and briefs.

Core Features & Use Cases

  • Convert messy design briefs and conflicting guidance into structured prompts for Designer handoff.
  • Translate research evidence into design prompts (evidence → brief) following the project's design system constraints.
  • Preserve design intent with drift-free framing across prompts and design context blocks.

Quick Start

Describe a vague UI direction or research finding and generate a ready-to-use design-prompt brief for Designer handoff.

Frequently Asked Questions about writing-design-prompt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert vague design directions into structured design prompts?

A design prompt brief structures messy design directions and research evidence into a clear format for Designer handoff. It prevents intent drift by framing constraints explicitly, ensuring the generated UI aligns with project-specific design contexts and visual systems.

What is the best way to translate UX research findings into a design brief?

Translating UX research into a design brief requires mapping evidence directly to prompt constraints. This converts raw research data into actionable design prompts that adhere to project-specific design system constraints and visual patterns.

How do I prevent design intent drift when creating UI prompts for designer handoff?

Prevent design intent drift by using preserve-without-drift framing across screen and flow references. This ensures core visual and functional goals remain consistent throughout the prompt generation and designer handoff execution phases.

Do I need a design context file to generate accurate design prompts?

You need a design context file like DESIGN.md to generate accurate design prompts. Aligning with project design contexts and relevant design-system owners ensures the output respects established visual and UI pattern constraints.

Can I use this to sharpen a messy design brief with conflicting visual guidance?

You can use this to sharpen a messy design brief with conflicting visual guidance. It converts contradictory instructions and vague UI ideas into a single, structured prompt that aligns with your project's design system owners.