design-brief

Generate structured design briefs aligned with existing codebase patterns.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/hschne/pi-stuff --skill design-brief-hschne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-brief
Source: https://github.com/hschne/pi-stuff/tree/main/skills/design-brief
Command: npx skills add https://github.com/hschne/pi-stuff --skill design-brief-hschne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of creating inconsistent, misaligned design briefs for new features, pages, and UI initiatives, ensuring all stakeholders share a clear, actionable vision before development begins.

Core Features & Use Cases

  • Interactive Requirement Gathering: Conducts structured interviews to capture user jobs-to-be-done, constraints, aesthetic preferences, and success metrics for the target interface.
  • Codebase-Aware Exploration: Automatically scans the existing project for design tokens, UI components, framework configurations, and established patterns to ensure the brief aligns with current systems.
  • Standardized Template Output: Generates a consistent design brief covering problem definition, experience principles, aesthetic direction, component inventory, and accessibility requirements, saved to a dedicated .design directory for downstream workflow use.
  • Use Case: A product manager planning a new user onboarding flow can use this skill to generate a comprehensive, codebase-aligned design brief in minutes, reducing misalignment between design and engineering teams.

Quick Start

Use the design-brief skill to create a design brief for the new user onboarding flow, including all required sections aligned with the project's existing design system.

Frequently Asked Questions about design-brief

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

FAQPage Schema
How do I create a design brief for a new feature that aligns with my existing codebase?

To create a design brief aligned with your codebase, you can use an automated skill that scans your project for design tokens and UI components, then generates a structured document covering experience principles and component reuse.

What is a codebase-aware design brief and when do I need one?

A codebase-aware design brief is a standardized document defining UI direction, aesthetic preferences, and accessibility constraints for new features. You need one before development to ensure product, design, and engineering teams share a clear vision.

How do I standardize UI direction and feature planning documentation across product teams?

You can standardize feature planning documentation by generating a consistent design brief template that captures user jobs-to-be-done, success metrics, and component inventory, saving it to a dedicated .design directory for downstream workflows.

Can I generate a design brief that includes existing design system components and accessibility constraints?

Yes, you can generate a design brief that automatically inventories existing design system components and frameworks, while explicitly documenting accessibility requirements to ensure the new UI initiative remains compliant.

Does the design brief generation process require manual input for user requirements?

The design brief process uses interactive requirement gathering, conducting structured interviews to capture user jobs-to-be-done, constraints, and aesthetic preferences before outputting the final standardized documentation.

What's the best way to document experience design principles for a new user onboarding flow?

The best way to document experience design principles for an onboarding flow is generating a structured brief that defines the problem, aesthetic direction, and component reuse strategy, ensuring alignment between design and engineering teams.