company-theme

Inject Company brand colors, typography, voice, and components into HTML, PPTX, and DOC artifacts.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/devsarangi2/company-theme --skill company-theme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: company-theme
Source: https://github.com/devsarangi2/company-theme/tree/main/skill/company-theme
Command: npx skills add https://github.com/devsarangi2/company-theme --skill company-theme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Company-theme automates the application of the Company brand to artifacts, ensuring consistent colors, typography, voice, and component patterns across HTML, presentations, and documents.

Core Features & Use Cases

  • Inject brand context into artifacts (HTML, PPTX, and DOC) to enforce consistent branding.
  • Load and apply brand files (brand.md, colors.md, typography.md, components.md, and assets/tokens.css for HTML; brand.md, colors.md, typography.md for PPTX; brand.md, voice.md, typography.md for DOC) to generate contextually accurate output.
  • Use case: apply the Company identity to an HTML dashboard or a PPTX deck to align visuals and language.

Quick Start

Invoke company-theme with a target artifact type to load and apply the branding guidelines immediately.

Frequently Asked Questions about company-theme

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

FAQPage Schema
How do I apply brand identity to HTML, PPTX, and DOC artifacts?

Applying brand identity to HTML, PPTX, and DOC artifacts involves injecting brand colors, typography, voice, and component patterns. The system auto-detects or uses explicit type flags to load appropriate brand files, ensuring visual and contextual consistency across all generated outputs.

What is a design system and how does it automate branding for generated documents?

A design system automates branding for documents by loading predefined brand files like colors.md, typography.md, and components.md. This mechanism enforces consistent visual identity, typography, and voice across HTML, presentations, and documents without requiring manual formatting adjustments.

Can I use custom typography and color tokens for HTML branding?

Yes, you can use custom typography and color tokens for HTML branding by loading assets/tokens.css alongside typography.md and colors.md. These files provide the necessary design system context to inject accurate brand styles and component patterns into HTML outputs.

Does the branding process work differently for DOC files compared to HTML dashboards?

Yes, branding differs for DOC files compared to HTML dashboards. DOC outputs load brand.md, voice.md, and typography.md to focus on language and text styling, whereas HTML dashboards also load components.md and assets/tokens.css to apply visual component patterns and design tokens.

What are the limitations of using templates for brand identity injection?

A limitation of using templates for brand identity injection is the reliance on predefined files like components.md and typography.md. If these source files lack comprehensive design tokens or voice guidelines, the automated branding output may appear incomplete or generic across different artifact types.