Design pack reference
Every skill in the Design pack — what it makes, when to use it, what it needs, its quality bar, and what it hands off to.
On-brand visual work: capture a brand once as a brand.json the Word and PowerPoint converters apply, and plan a deck slide by slide for its audience.
| Install | npx skilldrop-cli install --pack design |
| Skills | 2 plus 5 from core |
| Loops | none |
| How-to | Use the Design pack |
Skills
brand-kit
Capture a brand once as a reusable brand.json — logo files (and an on-dark version), colour roles as hex codes, heading and body fonts, voice, imagery rules, a PowerPoint template, contact details and the legal footer — plus a one-page BRAND.md, with text contrast checked and every value traced to where it came from.
Tier standard · v0.1.4 · SKILL.md · skill page
Use it when the user wants decks, flyers or documents in their branding, says "use our brand", "here's our logo and colours", "set up our brand kit", or hands over brand guidelines.
Needs: Python 3 for its scripts (standard library only).
A good result:
- Every colour is a hex code with a role. "Our green" is not a brand colour;
#0E5A46used for title bars is. - Text on background passes 4.5:1, checked by the script rather than by eye.
- Every value says where it came from, and inferred values are marked as inferred.
- Logo files are real paths that exist, with a PNG for PowerPoint and an on-dark version when the brand has one.
- Nothing is invented. A field the user didn't supply and couldn't be read from their sources is left out and listed, not guessed.
- BRAND.md fits on one page. A person checks the brand from it without opening the JSON.
Not for:
- Designing a new brand from scratch: this captures a brand, it doesn't invent one
- Building the deck itself; convert its Markdown with
md-to-pptx - A one-off document where the user only wants the default look
slide-outliner
Outline an architecture review or technical pitch deck — slide titles, key points per slide, and speaker notes. Does NOT generate PowerPoint/Keynote files; produces a structured outline the user can paste into any deck tool.
Tier standard · v0.1.0 · SKILL.md · skill page
Use it when the user is preparing for an architecture review, design review, sales pitch, partner meeting, or steering-committee presentation.
A good result:
- Slide titles assert, don't label. ✅ "We can ship the migration in two quarters" — ❌ "Migration timeline".
- No slide has both "high-level overview" and "deep technical detail". Pick one. If you need both, that's two slides.
- Speaker notes carry the narrative; slides carry the evidence. Don't put your script on the slide.
- One idea per slide. If the slide has two takeaways, split it.
- Appendix slides are labeled as such so the presenter doesn't accidentally walk into them.
Included from core
Installed with this pack. Details: Core pack reference.
brief-intake: Turn raw mess — a Slack thread, meeting transcript, Jira ticket, half-written Notion page, email chain, or paragraph of free-form context — into a structured brief that the downstream skill (adr-generator, design-doc, runbook-generator, exec-summary, slide-outliner) can consume without further intake.context-graph: Map the decisions behind a codebase from its ADRs, RFCs and design records — each record's status and date, what supersedes or amends what, which records cite which, the files and folders each decision governs, and with git the commits that implemented it and the commits that changed each decision's code since it was made, and who made them — then answer "why is it like this?" from the record and check the record is still true. Finds supersessions only one side records, current decisions pointing at code that is gone, code that has drifted from its decision, two current decisions governing the same path, and references to records that don't exist.council-review: Convene a council of distinct senior-engineer personas (Architect, Security, Operator/SRE, Pragmatist, User-Advocate, plus optional bench seats) to deliberate a decision, design, or code change — each takes an independent stance, the genuine disagreements are surfaced as named cruxes, and a Chair issues a reconciled verdict that records dissents and states what would change the decision. The "Claude Council."doc-critique: Review an existing document — ADR, design doc, runbook, exec summary, tech-comparison matrix, deck outline, decision log — and produce a structured critique against the same quality bars the skilldrop generators enforce. Categorizes findings by severity (blocker / major / minor / nit), points to the exact section/line, and suggests a concrete fix for each.output-hygiene: Review agent-written text before it ships and strip the machine artifacts it carries — invisible Unicode, non-breaking spaces, homoglyphs, harness-added provenance trailers, trailing chat closers — then flag the prose tells a script cannot catch, each quoted with a rewrite.