generate-brand-section

Generate a Brand section UI with 15 lazy-loaded tabs from merged design tokens and article data.

Updated Aug 23, 2025
One-click install
npx skills add https://github.com/therealityreport/trr-app --skill generate-brand-section
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-brand-section
Source: https://github.com/therealityreport/trr-app/tree/main/.agents/skills/design-docs-agent/generate-brand-section
Command: npx skills add https://github.com/therealityreport/trr-app --skill generate-brand-section

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This frontmatter-driven Skill generates a complete Brand section page component from merged design tokens and article data, automating the creation of a consistent admin design-doc experience.

Core Features & Use Cases

  • Automates the assembly of a multi-tab Brand section with 15 tabs, all wired to dynamic article data and lazy-rendered sub-sections.
  • Aggregates fonts, colors, layout tokens, and resources across design-token extractions to produce a cohesive brand presence in the design-docs UI.
  • Use case: when onboarding a new brand, run the skill to scaffold Brand{BrandName}Section.tsx and all 15 tab components, ensuring consistent structure and later population from ARTICLES.

Quick Start

Run the create-brand workflow to scaffold Brand{Name}Section.tsx and all 15 tab components from the design tokens and article data.

Frequently Asked Questions about generate-brand-section

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

FAQPage Schema
How do I auto-generate a multi-tab brand section in React from design tokens?

To auto-generate a multi-tab brand section from design tokens, this Skill merges fonts, colors, and layout tokens with article data to scaffold a complete React component with 15 lazy-loaded tab pages. It enforces type-safe routing and frontmatter-driven configuration without hard-coded data.

What is frontmatter-driven configuration for design-docs UI?

Frontmatter-driven configuration for design-docs UI means dynamic data aggregation from ARTICLES and extracted design tokens builds the page structure. This approach populates 15 tab pages and renders sub-sections automatically, avoiding hard-coded data in the component.

How do I scaffold a scalable brand design system component with TypeScript?

You scaffold a scalable brand design system component by running the create-brand workflow, which generates a main BrandSection.tsx file and 15 tab components. It uses TypeScript to ensure type-safe routing and aggregates resources across multiple design token extractions.

Can I use this to merge design tokens across multiple articles for a new brand?

Yes, you can merge design tokens across multiple articles for a new brand. The Skill automates the assembly of fonts, colors, layout tokens, and resources across extractions to produce a cohesive brand presence and consistent admin design-doc experience.

Does the generated brand section support lazy-loaded sub-pages?

Yes, the generated brand section supports lazy-loaded sub-pages. It automates the construction of 15 tab pages that are all wired to dynamic article data and lazy-rendered to ensure scalable performance for the design-docs UI.

Why should I avoid hard-coded data when building design docs components?

Avoiding hard-coded data when building design docs components ensures scalability and consistency across brands. This Skill enforces dynamic data aggregation from ARTICLES and frontmatter-driven configuration, so all 15 tab pages populate automatically from merged design tokens.