shiquda/open-pptd-skill / skills/open-pptd
open-pptd
FlaggedCreate, edit, reverse-decompile, and export presentations using the open PPTD format and native pptd compiler. For every PPT task, default deliverables are BOTH (1) a self-contained PPTD project folder (deck.pptd manifest + pages/*.page) and (2) a locally compiled native .pptx with vector shapes, connector arrows, LaTeX math formulas, speaker notes, and native tables. Completely offline — zero dependency on browser automation or cloud logins.
reference/design_system/work/blue-flame-brand/design.md
View on GitHub# Blue Flame Brand · work_report STYLE DESIGN SYSTEM
## PART A — work_report Baseline (Universal Floor)
Conclusion-first business reporting, benchmarked against top-tier business reviews and project progress briefings: every page scannable in 30 seconds, every number able to withstand drill-down — status backed by evidence, deviations attributed, asks spelled out.
Content and layout:
1. Management structure: executive overview (one-page verdict on completion) → core metrics vs. targets → revenue/mix analysis → deviation attribution → project status (red/amber/green) → cost and efficiency → next-period actions → items needing decisions and support.
2. Status visualization is the signature: red/amber/green status lights, target vs. actual tables, progress bars with numeric labels, variance waterfalls, milestone timelines.
3. Medium-high density, grid discipline: pages are built from aligned status modules and tables; zero decoration; every module answers "so what" on the spot.
Visual style:
1. Aesthetics: crisp, corporate, instrumental; the reader can audit the quarter from the pages alone.
2. Type: a single sans-serif family throughout, hierarchy built on weight and size; numbers column-aligned; never use serif display type (except the serif pairing specified in PART B).
3. Color: a neutral structural palette plus one accent for emphasis and current-period highlights; green/amber/red express status only, never decoration.
4. Graphics: simple chart types (bar comparisons, line trends, waterfall attribution); fine table rules, right-aligned numbers; no 3D, no pictographs as data, no gradient fills.
Structure and discipline:
1. Page one is always the verdict: one sentence on overall completion + target vs. actual for 3–5 headline metrics; no filler cover fluff.
2. Every metric shows the trio — target / actual / attainment rate; actual without target is a defect.
3. Deviation pages attribute quantitatively: the gap decomposes into named causes that sum exactly to the total gap — no unexplained remainder.
4. Project status comes as a trio: status light + evidence (progress %, milestones) + corrective action (with owner and date); a red item without a recovery plan is a defect.
5. Next-period actions are commitments: each carries an owner, a deadline, and an expected quantified effect.
6. Trend pages mark the reporting-period boundary, with inflection causes annotated inside the chart; forecast segments use dashed lines labeled as plan/estimate.
7. Parallel modules align strictly to the grid: same row, same height, same baseline; mixed content is grouped by meaning, not scattered.
8. Numbers must carry unit, period, and basis; estimates and modeled values follow the conventions of the underlying project materials.
9. The deck closes on items for management decision and support — listed one by one, each with the consequence of delay; no thank-you page endings.
Default baseline (PART B may override): progress / attainment / red-amber-green status use one unified lightweight component, drawn one way across the deck; each page has 1 theme + 2–4 supporting points, the conclusion graspable within 5 seconds; every metric carries its "so what" — cause, impact, or next action — no bare-number piles. Density anchor: per-page minimums for evidence modules, charts, and labeling habits follow this style's density-baseline section; this baseline imposes no uniform numbers.
**Headline read-through test**: reading only the page titles across the deck should tell the complete story; if the read-through fails, the structure has not been established.
### Global Prohibitions (AI Default Patterns · Mandatory)
1. **No default cards**: strictly no rounded-rectangle cards to build hierarchy or alignment — containers serving information functions (status lights, decision cards, quote boxes) do not count as cards. Rules, whitespace, and size/weight contrast are the better solution.
2. **No evenly split compositions**: no default three-way, four-way, or 2×2 matrix splits — even splits must be justified by content structure.
3. **No unmotivated AI color schemes**: palettes specified in the body are exempt; what is banned is the mediocre, unjustified default — blue-purple gradients, cyan-purple neon, rainbow flares, glass cards, glowing borders.
4. **No element that clashes with the overall style**: nothing outside the style may appear.
5. **Transparent chart backgrounds**: transparent or the page background color, except reversed-out on dark.
6. **Care with large empty areas**: whitespace for breathing, grouping, and rhythm is allowed; padding to fill space, or stretching thin content into a crowded page, is treated as a defect.
## PART B — Signature System
One-line style signature: a late-night operations war room — on a near-black blue ground, flame cyan and ice blue form two tiers carrying data and attainment, amber owns anomalies and consequences, mixed-weight conclusion titles sit in a fixed four-corner skeleton, and photography stays on the cover only.
【Color Palette】
- Background: body pages in near-black blue #06070B (approx.), cover and closing one step deeper at #020307 (approx.); this dark family is the only one allowed, chart areas get no separate fill.
- Main titles / key assertions: cold white #F7F8FA (approx.).
- Body #C6CCD3 (approx.); secondary explanation #969DA3 (approx.); footer / weak annotation #6E757B (approx.); faintest atmosphere layer #414548 (approx., reserved for decorative-quote elements).
- Flame cyan #1FB9D5 (approx.): the brand anchor — sole primary chart color, progress fills, attainment state; no large color blocks in body areas.
- Ice blue #B8ECF9 (approx.): big numbers, in-ring values, table-top rules, milestone nodes, decision-card outlines — the brightest data tier.
- Mid cyan #4FA0BB (approx.): leader lines, route connectors, and other structural hints; the cover eyebrow may use light cyan #88D3E8 (approx.).
- Amber #DFA93C (approx.): reserved for warnings, misses, risks, and consequences of delay — never decoration.
- Status green #58CA8F, coral red #D96A56 (both approx.): enter only status lights and linked progress bars, expressing on-track / delayed; "attained" never borrows green — always flame cyan.
- Structural colors (all approx.): structural lines #1A222C, track beds #141B23, card outline dark cyan #214A59, axis baseline #536780, phase dashes #527490.
- Decorative mist blobs: low-opacity ellipses of deep navy #050A1E and deep teal #06191D (approximate ranges), clipped by the canvas edges, never overlapping text or charts.
【Layout Skeleton】
Source facts: 16:9 canvas (sample images 1467×825), left/right safe margins ~6%. Header at ~3%–7% from top: business ownership at top left, report info at top right; title band at ~16%–25%: one-line conclusory title + one-line basis subtitle; body at ~27%–86%; bottom conclusion band at ~83%–90%: full-width hairline + one closing-loop judgment; footer pinned to the bottom: source/basis at lower left, "NN / total pages" page number at lower right. The reading path is fixed: "title conclusion → left-column judgment/annotation → right-side evidence chart → bottom closing sentence". Body column ratios are commonly 35:65 or 60:40; comparison types use a ~23% overview column + three isomorphic columns of ~25% each, separated by ultra-fine vertical rules. No breadcrumbs, no side navigation anywhere; modules are tiered purely by hairlines, whitespace, and weight — never by panels.
【Typography】
Source facts: modern sans-serif dominates absolutely, with narrow numerals carrying an industrial-instrument feel; table body text may switch wholesale to a serif face in the Song/Mincho manner, pairing against the sans-serif titles — the most distinctive type signature of this style. Titles use same-sentence mixed setting of "regular-weight statement + bold conclusion", about 2.3–2.5x body size; KPI big numbers 2–3.5x, units shrunk to about half on the same baseline; subtitle/body = 1x; module subheads ~1.2x medium; notes and sources 0.65–0.8x; the two-line cover title collides light and heavy weights. Decorative quotation marks use serif in the faintest color, as atmosphere only. No italics, no script, no display lettering; numbers receive no ornamental treatment.
【Chart Language】
- ⭐ Ring progress gauges (many pages): thick ring + dark track, one short tick at 12 o'clock reinforcing the instrument feel; big number + metric name at the ring's center, two lines of target/actual basis below; flame cyan = attained, amber = gap; at most 3 side by side per page.
- ⭐ Single-series bar chart (trend pages): all bars the same flame cyan, small rounded caps, values labeled directly per bar; ~4 ultra-dark horizontal gridlines + one brighter axis baseline; vertical dashed lines split before/after phases, circled-number event callouts hug their bars, mapping one-to-one to left-column notes; no legend, no y-axis title.
- ⭐ Horizontal progress bars (status pages): dark track + status-colored fill, the value or result written to the right of the bar, never on top of it; progress itself uses flame cyan, status lights use green/amber/red — progress and status are deliberately color-separated.
- ⭐ Vertical-line-free matrix table (diagnosis pages): no fill, no vertical lines, no zebra striping; an ice-blue full-width rule on top, a dark rule closing the bottom; number columns aligned, status column as "dot + word", a fixed drill-down note column at far right; table body in serif, the actual column bolded as a vertical anchor.
- Invisible-table scorecard (comparison pages): labels left, values right, fine horizontal and vertical rules dividing zones; no header, no legend, no outer frame.
- Three-phase roadmap (closing page): one full-length hairline + ice-blue hollow nodes; phase names above the nodes, milestones and entry gates below; a narrative route with no time scale.
- Concentric-ring bullseye (attribution pages): double rings + multiple converging rays channeling left-side factors into the core number; a decorative convergence figure that encodes no proportions.
【Signature Components】
- Fixed four-corner skeleton: ownership top left / report ID top right / source bottom left / "NN / total" page number bottom right — never missing anywhere in the deck.
- Bottom conclusion strip: full-width hairline + one closing-loop judgment (or a short vertical ice-blue line + single sentence), one per body page, containerless.
- Clipped mist blobs: low-opacity deep teal/navy ellipses entering from canvas edges, at most one per page, never intruding into data zones.
- Status dot + word: ● plus a two-character status word, an in-place legend, never a separate legend area.
- Circled-number cross-references: ①② markers appear both in left-column notes and inside the chart, building the narrative–evidence mapping.
- Serif table pairing: sans-serif titles + serif table bodies, used only on diagnostic table pages.
- Decision-card syntax: ice-blue thin-outlined cards (no shadow, no glow, fill close to the background), fixed as "decision number + main decision sentence + composition note + amber consequence of delay".
- Cover triple KPI: separated by thin vertical rules, number/unit/label on one baseline; ultra-wide night photograph with a dim blue-cyan thin outline, one cover page only.
【Prohibited】
- No light full-page backgrounds or white chart frames; the deck is dark throughout, charts get no separate fill.
- No multi-series rainbow chart colors: charts allow the flame-cyan single-hue family only; amber/green/coral red are spent only on status semantics.
- No green as "attained": attainment uses flame cyan; green enters status lights only.
- No legend dependence: labels sit directly beside the data; no axis titles, no explicit y-axes, no complex grids.
- No 3D, shadows, glows, highlight gradients, or glassmorphism; clipped mist blobs are the only permitted gradient element.
- No colored icons, emoji, or illustrations on body pages; photography is allowed on the one cover page only.
- No centered display titles, no thank-you-style endings; the close must land on roadmap + decisions.
- No text overlaid on progress bars; no highlighted card fills or shadows.
【Slide Types and Layouts】
Cover | title cluster + triple KPI + ultra-wide photo | text occupies the left ~50%, upper right left dark | photo ~4.2:1, cut off early on the right | ice-blue numerals with thin vertical dividers | the only page with a photo.
KPI overview | one judgment verified by three gauges | left 35% judgment + right 65% three rings | 4–6 status lines + 3 rings | bottom attribution closing sentence | not suited to parallel multi-topic content.
Diagnostic table | metric audit and drill-down | 6-column matrix, metric column ~24%, drill-down column ~32% | 5–8 rows | status-dot column, serif table body, bottom conclusion strip | not suited to narrative pages.
Trend evidence | time series and inflection attribution | left ~24% circled-number notes + right ~71% bar chart | 8–10 bars, 2 event callouts | phase dashes, big number at lower left | not suited to multi-series comparison.
Deviation attribution | gap decomposition and reconciliation | left 60% grouped delta list + right 40% bullseye | 4–6 factor rows in two groups | converging rays, bottom sealing sentence | not suited to precise waterfalls.
Horizontal comparison | same-basis multi-object scoring | ~23% overview + three isomorphic columns of ~25% | per column: 1 primary metric + 3 KV rows + 1 diagnostic passage | invisible tables, status dots | no more than 4 columns.
Status governance | project red/amber/green tracking | 3 equal-height horizontal cards stacked vertically, ~62:38 inside each | five fields per card: status / progress / blocker / correction / owner and date | progress bars, status lights | no more than 3 cards.
Roadmap-decision close | next-phase route + sign-off | upper half three-node roadmap + lower half two decision cards | 2 lines of description per node | ice-blue gates, amber consequences | no thank-you pages.
【Density Baseline】
Body pages carry 4–7 core modules and 8–26 independently readable text blocks; diagnostic table pages are densest, at ~6 columns × 5–8 rows and 30+ cell-level information groups. Each page has 1 main chart or 1 set of isomorphic gauges (at most 3); trend bars number 8–10, each directly labeled; progress-bar pages cap at 3 bars; scorecards carry 3–4 KV rows per column. Titles 1 line, subtitles 1 line, bottom closing sentence 1–2 lines; left-column note blocks run 2–3 lines each, roughly 25–60 words/characters equivalent; status cards carry ~5–7 text blocks each. Whitespace concentrates between title and body, in inter-column gutters, in the dark field at right, and at the page edges; the body area holds no large empty block, nor may it be filled to overflow.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |