Manage visual design themes for the workspace — extract themes from live websites (via Chrome), PowerPoint templates, or presets, then store and apply them to all visual outputs (slides, documents, diagrams, reports). Also audits and improves existing themes: contrast/accessibility checks, palette harmony, typography pairing, and completeness review. Use this skill whenever the user mentions themes, brand colors, visual identity, extracting styles, or wants consistent look-and-feel across outputs. Also triggers when the user wants to review, audit, fix, or improve a theme — e.g., "my theme feels off", "check contrast", "improve my colors". Also triggers when the user needs help choosing or building a theme — e.g., "what theme for my brand?", "help me pick a theme", "I need a visual identity for my startup". Even if the user just says "make it match our brand", "use our company colors", or "grab the style from that site", this skill applies.
Manage visual design themes for the cogni-works workspace. Themes are compact markdown files containing color palettes, typography, and design principles consumed by all plugins that produce visual output (slides, documents, diagrams, reports).
Before any operation, resolve the workspace themes directory:
${COGNI_WORKSPACE_ROOT}/themes/ if the env var is set{workspace}/cogni-workspace/themes/_template/ inside it) before proceedingIf Chrome browser automation tools are unavailable, inform the user upfront and suggest PPTX extraction or theme-factory presets as alternatives.
All themes live in the resolved themes directory. Each theme gets its own directory:
themes/
├── _template/theme.md # Canonical template (see Theme File Format below)
├── digital-x/theme.md # Brand theme
├── cogni-work/theme.md # Brand theme
└── {custom}/theme.md # User themes
When a theme slug already exists, ask the user whether to overwrite or create a versioned alternative (e.g., acme-v2).
When the user asks for theme advice — e.g., "what theme for my brand?", "help me pick a theme", "I need a visual identity" — guide them through a short discovery to route them to the best creation path.
Discovery questions (ask only what's needed, skip what you can infer from context):
Routing logic based on answers:
| User has... | Action |
|---|---|
| A website URL | → Operation #2 (Grab from Website) — extract the real brand |
| A PPTX template | → Operation #3 (Grab from PPTX) — extract from the template |
| Specific colors/fonts but no file | → Create a custom theme.md directly from their inputs, following the template |
| Nothing concrete, just a description | → Operation #4 (Create from Preset) — recommend 2-3 theme-factory presets that match their mood/industry, let them pick or blend |
| An existing workspace theme that's close | → Operation #5 (Audit/Improve) — review it and suggest targeted tweaks |
After creating or selecting a theme, always run a quick audit (Operation #5) on the result before finalizing — this catches contrast issues and missing sections early. Then offer to generate a theme showcase (Operation #7) so the user can see all tokens in action.
When the user asks to list or show available themes, scan the themes directory:
Use the Glob tool to find all themes: