# Create Black White Red PPTX

> Create, edit, or restyle editable PowerPoint-based A4 flyers, 16:9 event banners and thumbnails, 1200x630 social graphics, and presentation slides in a strict white, black, and red editorial system. Use when Codex must turn source text, reports, images, or an existing PPTX into restrained Japanese or bilingual creative with hard corners, strong type and unfiltered photography, fixed layout and export rules, minimal divider lines, no decorative effects, and a red accent limited to 3% of each page.

- Skill: `webfreakjp/create-black-white-red-pptx` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add webfreakjp/create-black-white-red-pptx`
- Raw SKILL.md: https://api.skillmd.com/api/skills/webfreakjp/create-black-white-red-pptx/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: webfreakjp (https://skillmd.com/u/webfreakjp)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/webfreakjp/create-black-white-red-pptx

---


# Create Black White Red PPTX

Create editable PowerPoint artwork whose hierarchy comes from typography, scale, photography, and whitespace rather than decoration.

## Load the binding references

1. Load [references/design-spec.json](references/design-spec.json) before generating or validating artwork. Treat it as the sole source of truth for design principles, content rules, colors, typography, profiles, dimensions, limits, and export settings.
2. Read [references/pptx-implementation.md](references/pptx-implementation.md) before generating, editing, or exporting a PPTX. Use it only to translate the structured rules into PowerPoint practice.
3. Import `scripts/design_spec.py` from Python generation or validation code. Do not duplicate design tokens as new constants in another script.
4. When the user corrects a rule, update the corresponding JSON field and its tests together.
5. Do not invent rules for source sections listed as missing in the JSON provenance.

## Execute the workflow

1. Establish the source boundary.
   - If no content or file is supplied, ask for the material and intended output: A4 flyer, 16:9 banner or thumbnail, 1200x630 social image, or presentation.
   - Record available copy, facts, numbers, dates, units, photos, image captions, sources, official logos, and QR destinations.
   - Preserve qualifiers and uncertainty. Do not invent claims, data, chronology, priority, or causality.
2. Define the communication job.
   - Identify the one message each page must communicate.
   - Choose a structure that matches the evidence: statement, comparison, process, timeline, table, chart, photo-led composition, or section divider.
   - Use sequence, causality, or quantitative encodings only when the source supports them.
3. Reduce before decorating.
   - Remove redundant labels, atmospheric English, filler captions, and repeated statements.
   - Retain source-critical notes even when they require another page or a compact source line.
   - Prefer fewer, larger elements over many small boxes.
4. Build the editable source.
   - Set the canvas to the requested format rather than forcing every output into 16:9.
   - Use native PowerPoint text, shapes, tables, charts, and lines. Keep meaningful units independently editable.
   - Use photographs only when they carry meaning. Keep them unfiltered, use them decisively, and do not cut faces.
   - Use only official logo data from a supplied `logo/` location. Do not synthesize or redraw a missing logo.
   - Keep graphic colors within the source palette. Avoid introducing a fourth color through charts, icons, SVGs, or imported assets.
   - Use hard corners everywhere. Use divider rules only for the two allowed purposes and stay within the four-rule limit.
5. Control typography and alignment.
   - Apply the output-specific size hierarchy from `design-spec.json`.
   - Keep the main-heading-to-body size ratio at four or more.
   - Set headline and catch-copy line breaks explicitly. Do not rely on automatic wrapping.
   - Fix equal-row column heights and align their bottom edges.
6. Validate and export.
   - Resolve the active tokens with `python3 <skill-directory>/scripts/design_spec.py --profile <profile> --slide-width-pt <width>` when implementing a PowerPoint canvas.
   - Run `python3 <skill-directory>/scripts/validate_pptx.py <output.pptx> --profile <a4|banner|social|presentation> --strict`.
   - Fix every error. Review every warning and retain one only for an intentional, documented exception.
   - Render the editable source and export the requested PDF or PNG at the exact dimensions in `design-spec.json`.
   - Inspect every page for overflow, clipping, collisions, orphaned one- or two-character line endings, weak hierarchy, accidental decoration, color drift, excessive red area, unaligned columns, and inappropriate rules.
   - Test every exported QR code with a real decoder or device. Do not treat visual inspection as a scan test.
   - Reopen the PPTX and confirm that text remains text and important elements remain editable.

## Handle existing decks

- Preserve the user's wording, facts, speaker notes, hyperlinks, charts, and media unless the request explicitly authorizes content edits.
- Inventory masters, layouts, fonts, colors, rounded shapes, effects, photos, logos, QR codes, and repeated furniture before restyling.
- Rebuild violations at their source. Do not cover old objects with new rectangles or hide them outside the canvas.
- Keep useful semantic structures such as native tables and charts when they can be restyled safely.

## Report completion

State the editable source path, exported deliverable path, selected profile, validation performed, and QR test result when applicable. Mention any intentional exception or PowerPoint limitation that remains.