ba-brand-prompt-gen

Generate a structured Design System prompt from product and brand inputs.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill ba-brand-prompt-gen-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ba-brand-prompt-gen
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/.agent/skills/ba-brand-prompt-gen
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill ba-brand-prompt-gen-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Collects input from stakeholders and converts it into a comprehensive, ready-to-run Design System prompt, ensuring alignment between product goals and DS output.

Core Features & Use Cases

  • Collects product, audience, platform, and asset context from stakeholders.
  • Validates and briefs the prompt according to a formal checklist and references.
  • Generates a structured, token-ready Design System prompt suitable for base-gen, design tooling, and development handoff.
  • Use Case: a BA runs this skill to produce a DS prompt for a new SaaS product across Web Admin and Mobile platforms.

Quick Start

Proceed by interviewing stakeholders in checklist sections, summarize after each group for confirmation, and generate the final Design System prompt saved to docs-BA/Prototype/Design System/.

Frequently Asked Questions about ba-brand-prompt-gen

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

FAQPage Schema
How do I generate a Design System prompt from stakeholder input?

To generate a Design System prompt, this Skill collates product, audience, platform, and asset context from stakeholders into a structured, token-ready document aligned with a formal brand checklist.

What is a design system prompt and when do I need one for base-gen?

A design system prompt is a structured, output-ready document covering product context, tokens, and components. You need one to drive base-gen and design work without ambiguity across platforms like Web Admin and Mobile.

How do I collect brand information for a design brief?

You collect brand information by interviewing stakeholders in checklist sections, summarizing after each group for confirmation, and validating the brief against references before generating the final document.

Can I create design tokens for Web Admin and Mobile platforms from a design brief?

Yes, the generated Design System prompt is token-ready and supports multiple platforms. It covers platform-specific context and components needed for design tooling and development handoff.

What's the best way to structure a Design System prompt for development handoff?

The best way is to align the prompt with a formal template covering product context, audience, platforms, tokens, components, and design principles, ensuring downstream design work proceeds without ambiguity.

Why does my Design System prompt lack token and component details?

Your prompt lacks details if stakeholder input is incomplete. This Skill validates input against a formal brand checklist and references to ensure all token and component context is captured before output.