
Branding
- 85 installs
- 125 repo stars
- Updated February 4, 2026
- igorwarzocha/opencode-workflows
Apply configured corporate colors and typography to presentations, reports, and documents, refusing to invent undefined brand values.
About
A skill that enforces corporate visual identity on professional artifacts using defined hex codes and font families. A developer uses it to brand decks, reports, and documents or verify they are on-brand.
- Refuses to assume brand values; requests hex codes and fonts when placeholders are undefined
- Applies primary/accent colors and heading/body fonts consistently
Branding by the numbers
- 85 all-time installs (skills.sh)
- +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #1,165 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/igorwarzocha/opencode-workflows --skill brandingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 85 |
|---|---|
| repo stars | ★ 125 |
| Last updated | February 4, 2026 |
| Repository | igorwarzocha/opencode-workflows ↗ |
What it does
Apply configured corporate colors and typography to presentations, reports, and documents, refusing to invent undefined brand values.
Files
<instructions> The agent MUST apply official corporate visual standards to all professional artifacts. However, these standards MUST NOT be assumed if they are not explicitly defined in the <visual_standards> section.
If the placeholders in <visual_standards> have not been replaced with actual values, the agent MUST: 1. Notify the user that branding guidelines are not yet configured. 2. Request the specific Hex codes and Font families from the user. 3. Suggest that the user updates this SKILL.md file or provides a BRANDING.md in the vault for long-term persistence. </instructions>
<visual_standards>
🎨 Corporate Identity Placeholders
The following values are currently UNDEFINED. The agent MUST NOT invent these values.
1. Primary Colors
- Primary (Dark): [INSERT_HEX_CODE] (Recommended for primary text)
- Secondary (Light): [INSERT_HEX_CODE] (Recommended for backgrounds)
- Neutral: [INSERT_HEX_CODE] (Recommended for secondary elements)
2. Accent Colors
- Accent 1: [INSERT_HEX_CODE]
- Accent 2: [INSERT_HEX_CODE]
- Accent 3: [INSERT_HEX_CODE]
3. Typography
- Headings Font: [FONT_FAMILY_NAME] (e.g., Poppins, Helvetica)
- Body Font: [FONT_FAMILY_NAME] (e.g., Lora, Georgia)
</visual_standards>
<workflow> 1. Validation: Check <visual_standards> for active placeholders. If found, the agent MUST pause and request details from the user. 2. Analysis: Once defined, identify headings vs. body text in the target artifact. 3. Mapping: Assign primary colors to text and accent colors to shapes/charts/highlights. 4. Execution: Update the font and color properties in the target file (DOCX/PPTX XML, CSS, or HTML). 5. Verification: The agent SHOULD verify accessibility (color contrast) and visual hierarchy after applying the brand. </workflow>