| 1 | --- |
| 2 | description: Create Style child workflow for a reusable communication method and visual-default workspace without page prototypes. |
| 3 | --- |
| 4 | |
| 5 | # Create Style Workflow |
| 6 | |
| 7 | Enter this child workflow only after [`Create Template`](../create-template.md) dispatches `kind: style`. |
| 8 | |
| 9 | ## Responsibility Boundary |
| 10 | |
| 11 | | Owner | Responsibilities | |
| 12 | |---|---| |
| 13 | | Create Template | Child-workflow dispatch plus the shared `library` / `project` scope, confirmation gate, collision preflight, registration, completion, and Generate PPTX handoff contract | |
| 14 | | Create Style | Reusable communication method, page-role vocabulary, evidence discipline, visual-system defaults, image/icon direction, review focus, and the roster-free `design_spec.md` | |
| 15 | |
| 16 | **Hard rule — child workflow, not a top-level route**: Create Style executes only inside Create Template. It uses the parent workflow's single shared confirmation/preflight/registration contract and never creates a competing entry route or second confirmation gate. |
| 17 | |
| 18 | **Hard rule — method and defaults only**: A Style owns a reusable way to argue, express evidence, and coordinate non-binding design defaults. It owns no current-project communication contract, reusable brand identity, page geometry, canvas, SVG prototype, Master/Layout graph, placeholder contract, application contract, visible asset inventory, carrier eligibility, image source, or local authoring-capability whitelist. |
| 19 | |
| 20 | **Hard rule — no page prototypes**: Style contributes only its own Design Spec. Do not create page SVGs, a review PPTX, or empty `images/`, `icons/`, or `exports/` directories. In a project workspace shared with another kind, files that kind owns are not Style output and are left untouched. |
| 21 | |
| 22 | ## Invocation Points |
| 23 | |
| 24 | 1. Use §1–2 below for Style analysis and brief fields, then execute Create Template Steps 2–3 with those child-owned fields. |
| 25 | 2. After Create Template Step 4 resolves and preflights `<template_workspace>` and `<design_spec_path>`, use §3 to materialize the confirmed Style. |
| 26 | 3. Run §4, then return its evidence to Create Template Steps 5, 7, and 8. Create Style always skips the shared structured-preview step. |
| 27 | |
| 28 | ## 1. Style Input Interpretation |
| 29 | |
| 30 | Use every supplied reference only as evidence for reusable method and design defaults: |
| 31 | |
| 32 | | Evidence | May inform | Must not become | |
| 33 | |---|---|---| |
| 34 | | Direct brief, text, document, or website | Argument flow, claim discipline, page-role vocabulary, data-expression rules, and review focus | The current project's audience, objective, outline, page count, or source claims | |
| 35 | | PPTX, PDF, image, or SVG reference | Visual-system tendencies, density, decoration, image treatment, and icon treatment | A copied page roster, canvas contract, Master/Layout graph, or fixed geometry | |
| 36 | | Brand or organization material | A lower-priority fallback direction when the user explicitly wants it generalized | Official identity truth, logos, proprietary palettes, brand voice, or trademarked presentation rules | |
| 37 | | Existing mode, visual-style, or image-rendering catalog entry | A preferred catalog seed plus a concise Style-owned overlay | A duplicated copy of the catalog file | |
| 38 | |
| 39 | **Mandatory — series-aware PPTX analysis**: Before inferring cross-page cadence from a composite PPTX reference, distinguish coherent finished-deck series from page/layout libraries. Infer cadence only within each coherent series; treat library pages as independent composition evidence, never as one ordered narrative run. |
| 40 | |
| 41 | Preserve source provenance in `Style Overview`. Keep exact user-authored method decisions distinct from AI-derived defaults. Reject organization-confidential examples and do not generalize proprietary frameworks into a reusable Style. |
| 42 | |
| 43 | **Reference — not a constraint**: A Style may prefer a catalog mode, visual style, image rendering, fallback palette, or fallback font stack. These values seed the normal Stage-2 solution; they are not execution locks and never bypass user confirmation. |
| 44 | |
| 45 | ## 2. Style Brief and Schema |
| 46 | |
| 47 | Add these child-owned requirements to Create Template Step 2: |
| 48 | |
| 49 | | Field | Requirement | |
| 50 | |---|---| |
| 51 | | Style ID and display name | Required; `style_id` is a filesystem-safe portable slug (prefer ASCII for interoperability) | |
| 52 | | Best fit | Required; describe reusable decision, explanation, or expression situations without binding a target audience or outcome | |
| 53 | | Reusable intent | Required; state what the method and design defaults should consistently achieve | |
| 54 | | Communication method | Required; argument flow, page-message discipline, and claim/evidence treatment; a preferred mode is optional | |
| 55 | | Page-role vocabulary | Required; reusable semantic roles and their jobs, evidence obligations, and composition tendencies; no order or inclusion policy | |
| 56 | | Evidence and data expression | Required; chart, table, source, and editability guidance without numeric content quotas | |
| 57 | | Visual-system defaults | Required; composition, density, decoration, color behavior, and native-text character; catalog seeds and literal fallbacks are optional, while carrier and native-construction eligibility remain downstream | |
| 58 | | Image and icon direction | Required; rendering, centrality, recurrence, and treatment defaults without source restrictions, asset inventory, or page mapping | |
| 59 | | Review focus | Required; extra checks to apply only if the user explicitly activates visual review | |
| 60 | |
| 61 | Write this roster-free schema: |
| 62 | |
| 63 | ```markdown |
| 64 | --- |
| 65 | style_id: <confirmed slug> |
| 66 | kind: style |
| 67 | summary: <one-line reusable method and design-default fit> |
| 68 | keywords: [<three-to-five discovery tags>] |
| 69 | --- |
| 70 | |
| 71 | # <Style Name> — Style Specification |
| 72 | |
| 73 | > Method and design defaults only. No project communication contract, brand identity, page structure, or SVG prototypes. |
| 74 | |
| 75 | ## I. Style Overview |
| 76 | | Property | Value | |
| 77 | |---|---| |
| 78 | | Style Name | <display name> | |
| 79 | | Best Fit | <reusable selection context> | |
| 80 | | Reusable Intent | <stable method/design outcome> | |
| 81 | | Sources | <source URLs, bundled references, or user brief; include date/version when known> | |
| 82 | |
| 83 | ## II. Communication Method |
| 84 | - **Preferred Mode**: <catalog id or custom; omit when none> |
| 85 | - **Mode References**: <catalog ids actually used by a custom seed; omit when none> |
| 86 | - **Mode Behavior**: <required for custom; omit for a preset> |
| 87 | - **Argument Flow**: <reusable reasoning progression> |
| 88 | - **Page Message Discipline**: <relationship among question, title, message, and proof> |
| 89 | - **Claim Discipline**: <treatment of facts, assumptions, implications, and recommendations> |
| 90 | |
| 91 | ## III. Page Role Vocabulary |
| 92 | | Role | Communication Job | Evidence Obligation | Composition Tendency | |
| 93 | |---|---|---|---| |
| 94 | | <semantic role> | <job> | <proof requirement> | <non-geometric tendency> | |
| 95 | |
| 96 | ## IV. Evidence & Data Expression |
| 97 | - **Argument Trace**: <claim-to-evidence relationship> |
| 98 | - **Charts**: <selection, labeling, annotation, and decoration behavior> |
| 99 | - **Tables**: <comparison, hierarchy, and emphasis behavior> |
| 100 | - **Sources**: <citation and uncertainty treatment> |
| 101 | - **Native Editability**: <when editable data/native shapes are preferred> |
| 102 | |
| 103 | ## V. Visual System Defaults |
| 104 | - **Preferred Visual Style**: <catalog id or custom; omit when none> |
| 105 | - **Visual Style References**: <catalog ids actually used by a custom seed; omit when none> |
| 106 | - **Visual Style Behavior**: <required for custom; omit for a preset> |
| 107 | - **Composition**: <page-scale relationships without fixed geometry> |
| 108 | - **Density**: <information and whitespace rhythm> |
| 109 | - **Decoration**: <shape, rule, elevation, and ornament behavior> |
| 110 | - **Color Behavior**: <role and contrast behavior; no identity claim> |
| 111 | - **Typography Character**: <hierarchy and register; no identity claim> |
| 112 | |
| 113 | ### Fallback Color Scheme |
| 114 | | Role | HEX | Purpose | |
| 115 | |---|---|---| |
| 116 | | <role> | #RRGGBB | <fallback use> | |
| 117 | |
| 118 | ### Fallback Typography |
| 119 | | Role | Primary | Fallback Tail | Character | |
| 120 | |---|---|---|---| |
| 121 | | <role> | <family> | <ordered fallbacks> | <typographic job> | |
| 122 | |
| 123 | ## VI. Image & Icon Direction |
| 124 | - **Preferred Image Rendering**: <catalog id or custom; omit when none> |
| 125 | - **Image Rendering References**: <catalog ids actually used by a custom seed; omit when none> |
| 126 | - **Image Rendering Behavior**: <required for custom; omit for a preset> |
| 127 | - **Image Usage**: <semantic role and frequency tendency> |
| 128 | - **Image Treatment**: <crop, framing, overlay, and caption behavior> |
| 129 | - **Icon Treatment**: <shape/stroke/fill behavior; actual library and inventory remain Stage-2 decisions> |
| 130 | |
| 131 | ## VII. Review Focus |
| 132 | <!-- visual-review-trigger: explicit-user-only --> |
| 133 | > Apply this section only after the user explicitly activates visual review. It never triggers that stage. |
| 134 | |
| 135 | - <style-specific answer, evidence, hierarchy, legibility, or scan-path check> |
| 136 | ``` |
| 137 | |
| 138 | `Fallback Color Scheme` and `Fallback Typography` are conditional; omit either subsection when the Style has no literal fallback values. Exact fallback colors use `#RRGGBB`. A supplied Brand or Deck identity replaces overlapping fallback colors, font families, voice, and icon identity as one identity decision; it does not erase the Style's communication method or evidence discipline. |
| 139 | |
| 140 | `Preferred Mode`, `Preferred Visual Style`, and `Preferred Image Rendering` are recommendation seeds. The current project's confirmed Stage-2 values remain authoritative. A preset value must be a real ID in its matching catalog. For `custom`, retain only real catalog references actually used as a comma-separated ID list and include the matching behavior prose. |
| 141 | |
| 142 | **Hard rule — Style never becomes a capability policy**: Style prose may tune |
| 143 | treatment, visual weight, density, recurrence, and coherence. It never bans a |
| 144 | carrier or requires carrier coverage, never selects image source, and never |
| 145 | narrows primitives, Office presets, independent composition, Boolean, or |
| 146 | necessary freeform. Explicit current-project requirements remain upstream. |
| 147 | |
| 148 | `Page Role Vocabulary` is a semantic vocabulary, not a Page Roster. Do not assign order, required/optional/repeatable status, page count, filenames, Master/Layout identities, slots, or fixed/replaceable/example-only content policy. |
| 149 | |
| 150 | ## 3. Materialize the Confirmed Style |
| 151 | |
| 152 | Create Template supplies an already resolved and collision-checked `<template_workspace>` and `<design_spec_path>`. Write only: |
| 153 | |
| 154 | ```text |
| 155 | <template_workspace>/ |
| 156 | └── templates/ |
| 157 | └── design_spec.md # project scope: design_spec.style.<style_id>.md |
| 158 | ``` |
| 159 | |
| 160 | Do not create or adopt images, icons, SVGs, native payloads, or review exports. References remain textual provenance; they are not portable Style assets. |
| 161 | |
| 162 | ## 4. Style Validation |
| 163 | |
| 164 | Return these facts to Create Template: |
| 165 | |
| 166 | - The Design Spec contains non-empty `style_id`, `kind: style`, `summary`, and three-to-five `keywords`; no other frontmatter field exists. |
| 167 | - `style_id` matches the confirmed workspace ID in library scope. |
| 168 | - Required sections I–VII exist; preset seeds resolve to real catalog IDs, while custom seeds include behavior prose and only real comma-separated catalog references. |
| 169 | - No `*.svg`, optional asset directory, review export, or native payload was created. |
| 170 | - No `primary_color`, canvas, page-count, page-type, replication, native-structure, Master/Layout, placeholder, Page Roster, or Signature Design Elements field exists. |
| 171 | - No current-project target audience, communication objective/outcome, delivery context, artifact afterlife, content outline, page assignment, icon inventory, or image-resource mapping exists. |
| 172 | - Brand-only identity sections (`Brand Overview`, `Color Scheme`, `Typography`, `Logo`, `Voice & Tone`, and `Icon Style`) and Deck-only `Template Overview` are absent. Conditional fallback subsections remain explicitly named `Fallback Color Scheme` and `Fallback Typography`. |
| 173 | - `Review Focus` contains exactly one `<!-- visual-review-trigger: explicit-user-only -->` marker; its localized prose explains the same boundary, and the section cannot activate visual review by itself. |
| 174 | |
| 175 | For both scopes, Create Template Step 5 validates the portable Style contract without registration: |
| 176 | |
| 177 | ```bash |
| 178 | python3 skills/ppt-master/scripts/svg_quality_checker.py "<template_workspace>/templates" --template-mode |
| 179 | ``` |
| 180 | |
| 181 | For `library` scope, additionally validate the directory/index identity with: |
| 182 | |
| 183 | ```bash |
| 184 | python3 skills/ppt-master/scripts/register_template.py <style_id> --kind style --dry-run |
| 185 | ``` |
| 186 | |
| 187 | After that gate passes, Create Template Step 7 registers with: |
| 188 | |
| 189 | ```bash |
| 190 | python3 skills/ppt-master/scripts/register_template.py <style_id> --kind style |
| 191 | ``` |
| 192 | |
| 193 | For `project` scope, run only the shared validator, skip both registrar commands, and report `Not registered (project workspace)`. Downstream consumption always uses the explicit workspace root through Generate PPTX Step 3; a bare Style name or ordinary style description never activates it. |
| 194 |