Html Ppt Zhangzara Creative Mode
A brand visual-identity system reveal for an outdoor label — logo, color, type, and the rules that keep it consistent. Built as a decision-grade design craft deck for brand team, client.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Html Ppt Zhangzara Creative Mode when an AI agent needs a reusable SKILL.md workflow for this job: A brand visual-identity system reveal for an outdoor label — logo, color, type, and the rules that keep it consistent. Built as a decision-grade design craft deck for brand team, client.
When not to use it
Skip Html Ppt Zhangzara Creative Mode when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/html-ppt-zhangzara-creative-mode # Save SKILL.md to ~/.claude/skills/html-ppt-zhangzara-creative-mode/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/html-ppt-zhangzara-creative-mode/SKILL.md. For a shared project, commit the folder at .claude/skills/html-ppt-zhangzara-creative-mode/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Html Ppt Zhangzara Creative Mode skill for this task: Clone example.html AND the assets/ folder into the user's workspace. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Creative Mode
> Cream paper canvas with confident multi-color (green, pink, orange, yellow) accents and Archivo Black display.
A single self-contained HTML deck — typography, palette, decorative system, and slide vocabulary are all tuned together. Mixing layouts across templates breaks the system; stay inside this one.
## At a glance
- **Scheme:** light - **Formality:** medium - **Density:** medium-high - **Slides in demo:** 8
## Best for
Anything that should feel design-led and confident: creative agency pitches, design studio decks, ad shop credentials, brand creative reviews, art-direction reviews. Also a great unexpected pick for a tech talk, research findings, or finance review when the speaker wants to lead with taste rather than convention.
## Avoid for
Contexts that demand institutional restraint and a quiet authority — the saturated multi-accent palette will read as expressive, not formal.
## Workflow
1. **Clone `example.html` AND the `assets/` folder** into the user's workspace. This template ships an `assets/deck-stage.js` runtime (keyboard navigation, stage rendering); the HTML references it as `assets/deck-stage.js`, so the file must sit next to the cloned HTML or that path will 404 in the generated artifact and navigation will silently break. Inlining the JS into a single `<script>` block in the HTML is an acceptable alternative when a single self-contained file is preferred. 2. **Replace placeholder content** with the user's real headlines, body copy, numbers, names, dates, and section labels. Match existing dimensions when swapping image placeholders. 3. **Preserve the design system.** Never substitute fonts, recolor the palette, restructure the layout grid, or strip decorative elements (corner brackets, paper grain, geometric shapes, illustrated SVGs). They are part of the identity. 4. **Adjust deck length by duplicating layouts.** If the user has more content than the demo holds, duplicate an existing slide of the most appropriate layout. If less, drop slides from the bottom. Update page-number labels. 5. **Designing missing layouts:** if a slide needs a layout the template doesn't have, design it from scratch using the same fonts, palette, decorative vocabulary, spacing rhythm, and component grammar — never bail to a different template. 6. **Keep the navigation runtime as shipped.** If the deck ships an `assets/deck-stage.js` or inline keyboard handler, leave it intact.
## Output contract
Emit between `<artifact>` tags:
``` <artifact identifier="zhangzara-creative-mode" type="text/html" title="Deck Title"> <!doctype html> <html>...</html> </artifact> ```
## Source & license
Vendored from upstream MIT-licensed [`zarazhangrui/beautiful-html-templates`](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/creative-mode).
The full upstream MIT license text — including the original copyright notice — ships in this skill at [`LICENSE`](./LICENSE) and must be redistributed alongside any copy of `example.html`, `template.json`, or any vendored `assets/` runtime. See `template.json` for the upstream metadata snapshot.
Intended uses
- Clone example.html AND the assets/ folder into the user's workspace.
- Replace placeholder content with the user's real headlines, body copy,
- Preserve the design system. Never substitute fonts, recolor the palette,
- Adjust deck length by duplicating layouts. If the user has more content
- Designing missing layouts: if a slide needs a layout the template
- Keep the navigation runtime as shipped. If the deck ships an
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.