design-brief

To create a contextual design brief, you define the product purpose, user specificity, design principles, and anti-goals. This ensures your product UI work is grounded in real context rather than relying on generic templates.

A design brief should include product purpose, user definitions, emotional targets, and anti-goals. Establishing these design principles prevents generic visual outputs by enforcing strict product context and user specificity.

You define anti-goals and emotional targets by auditing references and establishing clear design context at project kickoff. This guides early-stage design work by setting explicit constraints and success metrics for the team.

Yes, you can use a structured design brief for cross-disciplinary alignment and handoffs. It provides a shared foundation of product context, design principles, and user definitions that supports consistent design reviews across teams.

Yes, the design brief supports adding optional resources like scripts, references, and assets. You can enrich the brief by including these components alongside the required YAML frontmatter defining the name and description.

You need a contextual design brief instead of a standard template when starting branding or UI work that requires specific user definitions and emotional targets. It grounds your design decisions in actual product context to avoid generic outcomes.