Organize project materials into a design proposal that is evidence-based, has spatial judgment, and is open for discussion. For a newly made visual proposal, by default first form a full-page visual draft to test the composition and image expression, then prepare text-free standalone assets and rebuild an editable PPT. Preserve the options of image-only version, hybrid version, and existing template according to the user's requirements.
The direction currently confirmed by the user is minimal, high-end brand layout, and the designer's reporting framework and derivation: establish direction through culture, concept, elements, design techniques, and atmosphere; after entering the spatial scheme stage, explain how the design works through plan, space, materials, and furnishings. The complete proposal includes a table of contents page in the layout specified by the user, and chapters are adjusted by stage; for details, see designer-report-framework.md。
First determine the task scope
- Follow the project, audience, reporting stage, ratio, page count, and visual direction already clarified in the conversation. When modifying an existing PPT, first check the original file, prioritize fixing the relevant pages, and do not reinvent the entire process.
- When the user limits it to "no renderings or plans for now, only consider textual concepts, design techniques, and design elements," adopt theconcept research stage, and subsequent tests at the same stage follow this scope. First explain the element basis, abstract characteristics, specific design actions, and the experience intended to be formed; do not generate project renderings, plans, or complete spatial partial renderings, and do not judge it incomplete based on the lack of these images. Culture, aesthetic atmosphere, material close-ups, and abstract element demonstrations can still serve the concept; if the user requests pure text or no images at all, then only write the concept and techniques. Resume plans and renderings only when the user requests advancing the spatial scheme.
- When the user requests "optimize and test" and does not specify a project, you may choose a clearly labeled fictional project to complete a small sample. Simulated materials are used to test judgment and expression, and do not fabricate actual plans, areas, costs, or operational conclusions.
- When the full set has been authorized for completion, the trial production is an internal quality check, not a permission gate that must be asked about again. Stop only at the agreed checkpoint when the user explicitly wants to "see a few pages first" or when a key choice truly cannot be reasonably determined.
- When outputting PPT, read and follow the current Presentations skill, including template routing, runtime, native editing, source notes, and page-by-page rendering requirements. When the user specifies HTML, use the available html-spatial-deck skill; do not use HTML to replace the required PPTX.
Workflow
1. Extract design judgments from the materials
Read project-truth.md, create project-truth.txtin the temporary project directory, distinguish FACT / JUDGMENT / PROPOSAL / UNKNOWN。
In analysis.txt write clearly: what this report should make whom understand or choose. Grasp the most influential project contradiction and form:
Known conditions or explicit assumptions → usage problems/opportunities → design actions → presentable spatial results
For example, "the entrance directly faces quiet seating" is a fact only if it can be verified in drawings or on site; "stagger the entrance sightline to reduce interference" can be a design suggestion. Each core concept should be implemented as organization, boundary, scale, light, material, or mode of use, and cannot be derived only through words such as "hidden, realm, elegant."
2. Organize the page outline and visual direction
Read outline-schema.md, establish outline.txt, and use five fields on each page to explain the viewpoint, text, visual evidence, layout, and material attributes. For the complete proposal, first read designer-report-framework.md, and organize chapters according to the specified table of contents master and design argumentation; the table of contents corresponds to actual content, and do not mechanically add chapter transitions. Local modifications, single-page templates, and limited trial pages comply with the task scope.
A complete proposal containing a spatial scheme includes by default local cultural analysis, location/geographic map, and the corresponding floor plans before the renderings. Read culture-site-plan.md: the cultural basis must support the subsequent elements and space; the location map explains the real position and surrounding relationships; the floor plan first explains the spatial organization before showing the corresponding renderings. In the concept research stage, retain cultural and location judgments related to the design; the table of contents uses the chapter names from the concept stage, and does not arrange floor plans, renderings, or blank placeholder chapters. Content requirements do not fix page count or layout; partial modifications and limited test pages stay within their scope, and when materials are lacking, project conditions are not fabricated.
First select the issues in this project that are worth explaining, then select the analytical expression. It is forbidden to arrange by default fixed experience flows such as "first glance, second glance" or "see—stop—try on"; functional relationship pages without basis or added judgment value should be deleted directly. Comparisons of elements, boundaries, light, or materials are merely optional expressions and are not replaced with another set of mandatory chapters.
Read visual-dna.md, in visual-dna.txt define fonts, colors, images, and layout. Templates are merely optional expression methods; reference files are below; the user's brand and references take priority. When no template fits, establish a direction on your own.
Read font-system.md and typography-lock.md, first define text roles for shared use by the visual draft and the PPT. Cover display text is determined by the composition, with no unified upper limit on font size; identical roles on inner pages remain stable, without shrinking text page by page to fit.
When the user requests a brand proposal feel, or gives feedback that inner-page text is too large or the layout is too full, read brand-proposal-layout.md, and redefine inner-page font levels, image sizes, and whitespace according to actual references and reading scenarios. Do not override this clear direction with generic presentation font sizes, and do not mistake "richer" for filling up the page.
When continuing from an existing reference or reworking, first restore the reference images and analysis that can be found, implement them as material roles, background texture, image proportions, and layering relationships, and then develop the representative page.
When creating anatmosphere pagefor culture, design elements, or design concepts, read culture-concept-mood-templates.md, view the original images specified by the user therein, and select from the five fixed composition types according to the content. Preserve the image combination, text anchors, and whitespace relationships, and replace them with project materials and copy; do not uniformly lay out atmosphere pages as a sidebar explanation with a single image, and do not require every set to use all five types. Here, priority is given to testing aesthetic materials and the joint composition of image and text, which differs from analytical presentation images that carry deduction.
When the user provides industry benchmark files, read benchmark-selection.md. First review the entire structure, then zoom in to screen specific pages, separately judging the argumentation method and visual quality; do not accept an entire set wholesale based on company name. Implement the practices to retain, rearrange, and exclude into this page outline, avoiding merely adding style adjectives.
For multi-image project concept pages, use short concept words corresponding to each image to jointly establish the theme, retain already-approved images, and organize hierarchy with editable text, see Concept Atmosphere Template. A complete proposal ends by default with a project-specific "Design Vision + Thank You / THANK YOU", using a recognizable atmospheric background image, and no longer defaults to ending with a development work checklist; for the specific editing scope, see Presentation Framework。
3. First use a full-page visual draft to test the direction
Based on the current task, select representative pages that can expose different layout risks, usually the cover, core analysis, and visual pages; for shorter tasks, all pages can be checked directly. When the user focuses on testing layout, use analysis diagrams, mood collages, or material pages to examine information hierarchy, image-text relationships, and rhythm; there is no need to first generate spatial renderings. When spatial expression is needed, then select key spatial pages and reference images, avoiding all three pages using the same large-image layout.
A concept manifesto or pause page should by default have a recognizable atmospheric background image under the current spatial proposal direction, with text and imagery composing together; a solid color or slight paper texture cannot replace the background image requested by the user. Use the solid-color version only when the user explicitly chooses a text-only transition.
For a new proposal or visual redo, read layered-editable-workflow.md, use image tools to first create a full-frame visual draft of the representative pages, directly testing the background texture, image hierarchy, overlays, analytical expression, and text placeholders. The full-page draft is the basis for composition and cannot be treated as an editable finished product; the text and precise relationships within it must be verified during reconstruction.
After the direction of the representative pages is established, first reconstruct them as a PPT and render it to confirm that the visual effect can be preserved, then complete the remaining pages in the same direction. Batch progress is allowed; it is not required to first generate the full set and then uniformly separate layers. When there is already a clear template or only a few pages are being changed, directly edit and check the relevant PPT pages. If production has been authorized, continue after checking, without adding a confirmation gate.
4. Select materials and native layout
Based on the determined project text roles, reconstruct the text using real fonts and pt values; do not treat the incidental glyph sizes in the image draft as font size specifications.
Based on the full-page visual drafts, prepare clean backgrounds, photography, mood references, and collage areas. For mood images of culture, elements, materials, and concepts, first search from Pinterest or other online sourcesand judge by aesthetics, mood, resolution, and composition when grouped; if a suitable image that expresses the concept is found, use it directly, do not default to generating an entire set, and do not set a generation ratio. Pinterest is used to discover materials, and the original page should be traced as much as possible; when search is restricted, switch to a public original source, and do not falsely claim it came from Pinterest. Distinguish the source attributes of real cultural evidence and associative mood references. When suitable images are lacking or specific image-text negative space is needed, then use Image Gen to supplement. For presentation images that carry element extraction, concept translation, and spatial strategy derivation, use Image Gen, showing relationships through material, volume, form, or light and shadow; text, captions, and a small number of dot/square anchors are laid out natively and independently. Do not downgrade concept demonstrations into assemblies of lines, boxes, arrows, and text because of editability or ease of implementation. Only make transparent PNGs for materials that need transparent edges; do not require every visual element to be cut out as a layer, and do not promise lossless automatic image separation.
For design methods, prioritizetraceable element evolution analysis: let the original clues, the extracted features, and the design changes correspond within the image; see element-evolution-analysis.mdfor details. Abstraction is used to summarize relationships; do not replace derivation with isolated stones, floating flakes, or artistic sculptures. Analysis can be before-and-after comparison, continuous evolution, or parallel comparison; the number of steps and composition are determined by the content; at the concept stage, keep it as a relational diagram and do not add a complete spatial rendering.
- Level A, default: titles, body text, annotations, and page numbers are editable; concept demonstration images, photography, and spatial drawings are independent images, and real drawings use original files or reliable vectors. Objects within images are not promised to be split into editable parts.
- Level B: complex collages are treated as images, and key text remains independently editable; specify which visual content has been composited.
- Level C: The user needs a full-page image version, explicitly not text-editable. Do not force a change to Level A because of this.
When the user is willing to do later manual adjustments, prioritize preserving image scale, cropping, whitespace, and layering; a Level B complex composite area with independent text may be used, and do not change it to equal-sized cards just because it is easy to implement programmatically. Preserve the editable parts the user requires, and fix visibly ugly pages before delivery; do not use the willingness to manually adjust as a reason to lower finished-product standards.
Subsequent spatial images inherit the material, construction, and furniture language; lock the positional relationships within the same space. Focal length, camera position, and shot scale are adjusted according to what each page needs to explain; do not use "same lens" as a substitute for consistency.
When producing the rendering chapter, first clarify the corresponding plan and its material attributes, then determine the camera position and spatial invariants; place the plan explanation before that group of renderings. Maps and plans should remain accurate according to real geography or original drawings, and native lines and vectors may be used; do not use the Image Gen route of abstract analysis to redraw accurate maps, dimensions, or unknown building layouts.
Spatial images and cultural intent images may use image tools. Real drawings, accurate data charts, and evidence-based engineering connection relationships are produced according to the rules of Presentations; do not use generated images to pass as precise evidence; unknown spaces are only conceptual intent, and should not be drawn to look like completed survey or construction results. All generated intermediate text, including prompts, design records, and QA, uses .txt；.md only for installed skill resources.
5. Check the finished product and deliver
Read quality-checklist.md. Check whether each page's point is supported, whether culture and materials are translated into spatial actions, and whether the conclusion responds to the opening. Review the rendered images of the final PPT page by page, and compare them with the corresponding full-page visual drafts, fixing lost hierarchy, text line breaks, overflow, cropping, and unintentional overlap; montage is only for checking the rhythm of the whole set.
Can be run in the skill directory:
python scripts/validate_project.py <project-dir> --stage final
python scripts/inspect_pptx.py <output.pptx>
Project validation can add --pilot-count N to check the number of representative pages selected this time; three pages are not a fixed requirement; for Level C add --mode image-only. These scripts only assist checking; they do not prove that the content is true, the design holds up, or the visuals pass. Deliver the final PPTX as the user needs; when the user requests a test presentation, a small number of final previews may be attached. Source files and asset packages are provided as needed. Save the final files according to the current environment; the skill's own maintenance files and project deliverables are handled separately.
Temporary project directory
image-ppt/{project-slug}/
source/
project-truth.txt
analysis.txt
visual-dna.txt
outline.txt
source-notes.txt
prompts/
visual-drafts/
pilot-preview/
assets-generated/
slides-preview/
exports/
{project-slug}-editable-cn.pptx
qa.txt
visual-drafts/ saves full-page visual exploration,pilot-preview/ saves representative-page PPT renders,slides-preview/ saves final PPT renders; do not use the former to pass as the latter two. Records for short tasks can be merged to avoid creating a documentation burden for simple modifications; when calling the project validation script, provide the corresponding files according to its conventions. External assets and non-trivial source facts are recorded in the PPT speaker notes [Sources], and generated images record their conceptual attributes.
Refer as needed
- Stage organization, insufficient materials, rework:workflow-rules.md
- Dark culture destination hotel:hotel-01
- Black-gold residence and model unit:residential-01
- Light-colored Eastern garden residence:residential-02
- Modern coastal minimalist residence:residential-03
- Eastern plants, objects, and commercial lifestyle:commercial-01
Only read references useful for the current task; the page count, colors, symbols, and example concepts of any template should not override project facts or user requirements.