Claude Skill

brand-content-design

Use when user says "create presentation", "make slides", "make carousel", "LinkedIn carousel", "create HTML page", "make landing page", "build web page", "html design system", "design system", "setup brand", "brand init", "extract brand", "get outline", "color palette", "alternat

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download camoa-claude-skills-brand-content-design_skills_brand-content-design-c73ba2a.zip · 46 KB

Install

skills CLI npx skills add https://github.com/camoa/claude-skills/tree/main/brand-content-design/skills/brand-content-design
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install camoa-claude-skills@llmmart
Git git clone https://github.com/camoa/claude-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole camoa/claude-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Brand Content Design

Create branded visual content (presentations, LinkedIn carousels, HTML pages) with consistent brand identity.

Trigger Phrases

  • "create presentation" / "make slides"
  • "create carousel" / "LinkedIn carousel"
  • "create HTML page" / "make landing page" / "build web page"
  • "html design system" / "design system"
  • "setup brand" / "brand init" / "extract brand"
  • "create template" / "new template"
  • "get outline" / "outline for template" / "prepare content"
  • "color palette" / "generate palette" / "alternative colors"
  • NOT for: General design questions, non-branded content
  • NOT for: Drupal conversion (use design-system-converter plugin instead)

Project Detection

Before ANY operation, find the PROJECT_PATH using this search order:

  1. Current directory - Check if ./brand-philosophy.md exists
  2. Parent directory - Check if ../brand-philosophy.md exists
  3. Subdirectories - Use find . -maxdepth 2 -name "brand-philosophy.md" to find nearby projects
  4. If multiple found - Ask user which project to use
  5. If none found - Direct user to run /brand-init first

Once PROJECT_PATH is set, the folder structure is:

{PROJECT_PATH}/
├── brand-philosophy.md          # Always exists
├── templates/
│   ├── presentations/
│   │   └── {template-name}/
│   │       ├── template.md
│   │       ├── canvas-philosophy.md
│   │       └── sample.pptx
│   ├── carousels/
│   │   └── {template-name}/
│   │       ├── template.md
│   │       ├── canvas-philosophy.md
│   │       └── sample.pdf
│   └── html/
│       └── {design-system-name}/
│           ├── canvas-philosophy.md
│           ├── design-system.md
│           └── components/      # Reusable HTML components
├── presentations/               # Output folder
├── carousels/                   # Output folder
├── html-pages/                  # Output folder (HTML pages)
└── assets/                      # Brand assets

Finding templates:

  • Presentations: find {PROJECT_PATH}/templates/presentations -name "template.md"
  • Carousels: find {PROJECT_PATH}/templates/carousels -name "template.md"

Three-Layer System

Apply this layered approach when creating content:

  1. Layer 1 - Brand Philosophy (brand-philosophy.md in project)

    • Load and apply visual DNA (colors, typography, imagery)
    • Load and apply verbal DNA (voice, tone, vocabulary)
  2. Layer 2 - Content Type Guide (from plugin references/)

    • Read references/presentations-guide.md for presentations
    • Read references/carousels-guide.md for carousels
  3. Layer 3 - Template (from project templates/)

    • Load template's canvas-philosophy.md for visual design rules
    • Follow template's structure for slide/card sequence

Commands

Route user requests to the appropriate command:

User Intent Command
Status, switch projects, or start /brand
Initialize new project /brand-init
Extract brand from sources /brand-extract
Generate alternative color palettes /brand-palette
Manage assets (logos, icons, fonts) /brand-assets
Create presentation template /template-presentation
Create carousel template /template-carousel
Get outline template + AI prompt with slide/card definitions /outline
Create presentation (guided) /presentation
Create presentation (quick) /presentation-quick
Create carousel (guided) /carousel
Create carousel (quick) /carousel-quick
Create HTML design system /design-html
Create HTML page (guided) /html-page
Create HTML page (quick) /html-page-quick
Add new content type /content-type-new

Effort-Adaptive Variant Selection

Presentations, carousels, and HTML pages each ship a guided command and a quick command. When the user names a variant explicitly ("quick carousel", "guided presentation"), honor it. When they don't ("make a presentation"), pick the variant from the active effort level — ${CLAUDE_EFFORT}:

${CLAUDE_EFFORT} Variant Command examples
low Quick — paste-and-go, minimal prompting /presentation-quick, /carousel-quick, /html-page-quick, /infographic-quick
medium / high / xhigh / max Guided — step-by-step wizard /presentation, /carousel, /html-page, /infographic

When ${CLAUDE_EFFORT} is unset (model without effort support), default to the guided variant. The quick end of this gradient pairs naturally with the Proactive output style — low effort plus Proactive style yields fully autonomous quick-content generation.

Commands without a quick/guided split (/brand, /brand-init, /brand-extract, /brand-palette, /brand-assets, /design-html, the /template-* wizards, /outline, /content-type-new) are unaffected — route to them directly.

Underlying Skills

Use these skills during content generation:

Skill When to Use
visual-content Generate visual output from canvas philosophy (bundled)
html-generator Generate HTML pages and components from design system (bundled)
pptx Convert presentation PDFs to PowerPoint
pdf Create multi-page carousel PDFs

The visual-content skill is bundled with this plugin. For HTML-to-Drupal conversion, use the design-system-converter plugin.

References

Bundled (Plugin-Specific)

  • references/brand-philosophy-template.md - Template for brand philosophy
  • references/template-structure.md - Template for template.md files
  • references/canvas-philosophy-template.md - Template for canvas philosophy
  • references/presentations-guide.md - Presentation best practices
  • references/carousels-guide.md - Carousel best practices
  • references/style-constraints.md - 18 visual styles with enforcement blocks
  • references/color-palettes.md - Color theory and palette types
  • references/output-specs.md - Dimensions, formats, file sizes
  • references/bias-prevention.md - Brand bias prevention checks
  • references/style-recommendation-engine.md - Intelligent style selection by brand personality, purpose, audience
  • references/slide-composition-rules.md - Per-slide-type focal points, layout modifiers, component frequency limits

Online Dev-Guides (Design Systems)

For design system recognition and analysis methodology, use the dev-guides-navigator plugin:

Invoke /dev-guides-navigator with keywords like "design system recognition", "Bootstrap mapping", or "component analysis". The navigator handles caching and disambiguation — never fetch dev-guides URLs directly.

Files (claude-skills)
  • references
    • bias-prevention.md 4.6 KB
      Loading…
    • brand-philosophy-template.md 4.7 KB
      Loading…
    • canvas-philosophy-template.md 10 KB
      Loading…
    • carousels-guide.md 9.6 KB
      Loading…
    • color-palettes.md 6.2 KB
      Loading…
    • output-specs.md 4.2 KB
      Loading…
    • presentations-guide.md 9.8 KB
      Loading…
    • slide-composition-rules.md 15.4 KB
      Loading…
    • style-constraints.md 43.4 KB
      Loading…
    • style-recommendation-engine.md 10.1 KB
      Loading…
    • template-structure.md 2.1 KB
      Loading…
  • SKILL.md 7.4 KB
    ---
    name: brand-content-design
    description: Use when user says "create presentation", "make slides", "make carousel", "LinkedIn carousel", "create HTML page", "make landing page", "build web page", "html design system", "design system", "setup brand", "brand init", "extract brand", "get outline", "color palette", "alternative colors", "infographic", "brand assets", "brand project". Use PROACTIVELY when user wants to create any visual content with consistent branding. MUST be invoked for branded content — routes to the correct command for presentations, carousels, infographics, and HTML pages.
    version: 3.2.0
    allowed-tools: Read, Glob, Grep, Write, Bash, AskUserQuestion, Skill
    user-invocable: false
    ---
    
    # Brand Content Design
    
    Create branded visual content (presentations, LinkedIn carousels, HTML pages) with consistent brand identity.
    
    ## Trigger Phrases
    
    - "create presentation" / "make slides"
    - "create carousel" / "LinkedIn carousel"
    - "create HTML page" / "make landing page" / "build web page"
    - "html design system" / "design system"
    - "setup brand" / "brand init" / "extract brand"
    - "create template" / "new template"
    - "get outline" / "outline for template" / "prepare content"
    - "color palette" / "generate palette" / "alternative colors"
    - NOT for: General design questions, non-branded content
    - NOT for: Drupal conversion (use design-system-converter plugin instead)
    
    ## Project Detection
    
    Before ANY operation, find the PROJECT_PATH using this search order:
    
    1. **Current directory** - Check if `./brand-philosophy.md` exists
    2. **Parent directory** - Check if `../brand-philosophy.md` exists
    3. **Subdirectories** - Use `find . -maxdepth 2 -name "brand-philosophy.md"` to find nearby projects
    4. **If multiple found** - Ask user which project to use
    5. **If none found** - Direct user to run `/brand-init` first
    
    **Once PROJECT_PATH is set**, the folder structure is:
    ```
    {PROJECT_PATH}/
    ├── brand-philosophy.md          # Always exists
    ├── templates/
    │   ├── presentations/
    │   │   └── {template-name}/
    │   │       ├── template.md
    │   │       ├── canvas-philosophy.md
    │   │       └── sample.pptx
    │   ├── carousels/
    │   │   └── {template-name}/
    │   │       ├── template.md
    │   │       ├── canvas-philosophy.md
    │   │       └── sample.pdf
    │   └── html/
    │       └── {design-system-name}/
    │           ├── canvas-philosophy.md
    │           ├── design-system.md
    │           └── components/      # Reusable HTML components
    ├── presentations/               # Output folder
    ├── carousels/                   # Output folder
    ├── html-pages/                  # Output folder (HTML pages)
    └── assets/                      # Brand assets
    ```
    
    **Finding templates:**
    - Presentations: `find {PROJECT_PATH}/templates/presentations -name "template.md"`
    - Carousels: `find {PROJECT_PATH}/templates/carousels -name "template.md"`
    
    ## Three-Layer System
    
    Apply this layered approach when creating content:
    
    1. **Layer 1 - Brand Philosophy** (`brand-philosophy.md` in project)
       - Load and apply visual DNA (colors, typography, imagery)
       - Load and apply verbal DNA (voice, tone, vocabulary)
    
    2. **Layer 2 - Content Type Guide** (from plugin `references/`)
       - Read `references/presentations-guide.md` for presentations
       - Read `references/carousels-guide.md` for carousels
    
    3. **Layer 3 - Template** (from project `templates/`)
       - Load template's `canvas-philosophy.md` for visual design rules
       - Follow template's structure for slide/card sequence
    
    ## Commands
    
    Route user requests to the appropriate command:
    
    | User Intent | Command |
    |-------------|---------|
    | Status, switch projects, or start | `/brand` |
    | Initialize new project | `/brand-init` |
    | Extract brand from sources | `/brand-extract` |
    | Generate alternative color palettes | `/brand-palette` |
    | Manage assets (logos, icons, fonts) | `/brand-assets` |
    | Create presentation template | `/template-presentation` |
    | Create carousel template | `/template-carousel` |
    | Get outline template + AI prompt with slide/card definitions | `/outline` |
    | Create presentation (guided) | `/presentation` |
    | Create presentation (quick) | `/presentation-quick` |
    | Create carousel (guided) | `/carousel` |
    | Create carousel (quick) | `/carousel-quick` |
    | Create HTML design system | `/design-html` |
    | Create HTML page (guided) | `/html-page` |
    | Create HTML page (quick) | `/html-page-quick` |
    | Add new content type | `/content-type-new` |
    
    ## Effort-Adaptive Variant Selection
    
    Presentations, carousels, and HTML pages each ship a **guided** command and a
    **quick** command. When the user names a variant explicitly ("quick carousel",
    "guided presentation"), honor it. When they don't ("make a presentation"), pick
    the variant from the active effort level — `${CLAUDE_EFFORT}`:
    
    | `${CLAUDE_EFFORT}` | Variant | Command examples |
    |--------------------|---------|------------------|
    | `low` | Quick — paste-and-go, minimal prompting | `/presentation-quick`, `/carousel-quick`, `/html-page-quick`, `/infographic-quick` |
    | `medium` / `high` / `xhigh` / `max` | Guided — step-by-step wizard | `/presentation`, `/carousel`, `/html-page`, `/infographic` |
    
    When `${CLAUDE_EFFORT}` is unset (model without effort support), default to the
    guided variant. The quick end of this gradient pairs naturally with the
    **Proactive** output style — low effort plus Proactive style yields fully
    autonomous quick-content generation.
    
    Commands without a quick/guided split (`/brand`, `/brand-init`, `/brand-extract`,
    `/brand-palette`, `/brand-assets`, `/design-html`, the `/template-*` wizards,
    `/outline`, `/content-type-new`) are unaffected — route to them directly.
    
    ## Underlying Skills
    
    Use these skills during content generation:
    
    | Skill | When to Use |
    |-------|-------------|
    | **visual-content** | Generate visual output from canvas philosophy (bundled) |
    | **html-generator** | Generate HTML pages and components from design system (bundled) |
    | **pptx** | Convert presentation PDFs to PowerPoint |
    | **pdf** | Create multi-page carousel PDFs |
    
    The `visual-content` skill is bundled with this plugin. For HTML-to-Drupal conversion, use the `design-system-converter` plugin.
    
    ## References
    
    ### Bundled (Plugin-Specific)
    - `references/brand-philosophy-template.md` - Template for brand philosophy
    - `references/template-structure.md` - Template for template.md files
    - `references/canvas-philosophy-template.md` - Template for canvas philosophy
    - `references/presentations-guide.md` - Presentation best practices
    - `references/carousels-guide.md` - Carousel best practices
    - `references/style-constraints.md` - 18 visual styles with enforcement blocks
    - `references/color-palettes.md` - Color theory and palette types
    - `references/output-specs.md` - Dimensions, formats, file sizes
    - `references/bias-prevention.md` - Brand bias prevention checks
    - `references/style-recommendation-engine.md` - Intelligent style selection by brand personality, purpose, audience
    - `references/slide-composition-rules.md` - Per-slide-type focal points, layout modifiers, component frequency limits
    
    ### Online Dev-Guides (Design Systems)
    
    For design system recognition and analysis methodology, use the dev-guides-navigator plugin:
    
    Invoke `/dev-guides-navigator` with keywords like "design system recognition", "Bootstrap mapping", or "component analysis". The navigator handles caching and disambiguation — never fetch dev-guides URLs directly.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.