3232373074/Codex-skill

Create Location Analysis PPT

Produce a presentation-ready location-analysis slide with a generated map image beneath an editable annotation layer.

Required companion skills

• Use imagegen for the planning-map bitmap.
• Use presentations:Presentations for template inspection, PPTX authoring, rendering, and QA.
• Read both companion skills completely before acting.

Workflow

1. Collect the source PPTX, boundary description, narrative copy, symbol references, output path, required fonts, and exact sizes.
2. Inspect every source slide and follow the presentation template workflow. Preserve the selected slide's canvas, title hierarchy, margins, map frame, spacing, palette, and inherited chrome.
3. Render and inspect all supplied map and symbol references. Assign roles explicitly: template reference, basemap/edit reference, metro symbol, rail-line style, commercial marker, community marker, and road-line style.
4. Define the map composition before generation: geographic extent, full-frame coverage, boundary policy, water, road hierarchy, metro, railway, site parcel, POI classification, and label zones. Default to an approximately 2 km context, then adjust the extent for the actual address, parcel size, selection boundary, urban density, and required transport/resource coverage.
5. Generate the map with image2/imagegen. Keep text, pins, station symbols, legends, and SITE out of the generated map whenever they must remain accurate or editable. Use references/image2-prompt.md.
6. Inspect the generated map at full resolution. Regenerate with one targeted correction if roads are straight, water resembles roads, railway segments are missing, the boundary is open, or the image contains text/icons.
7. Build the PPT from the copied template slide. Place the generated map inside the inherited image frame. Add exact text, road names, station symbols, POI markers, any explicitly requested boundary, the SITE parcel line, and SITE on the top layer.
8. Apply the user's specified font and size exactly. Convert point sizes to the authoring API's 96-DPI pixel units when required: px = pt × 96 / 72.
9. Position road names close to and parallel with their corresponding route. Avoid labels that float between roads or cross stations, pins, railway, or SITE.
10. Render the final slide, inspect it at full size, run overflow QA, and correct every unintended overlap or clipping issue. Use references/qa-checklist.md.
11. Export a new PPTX; never overwrite the supplied template unless explicitly requested.

Layer contract

Keep layers ordered from bottom to top:

1. Muted grayscale satellite/aerial basemap
2. Water system
3. Hierarchical road network
4. Metro and railway
5. Translucent jurisdiction fill and dashed boundary
6. Editable station/POI symbols
7. Editable SITE parcel line and marker
8. Editable road, facility, and station labels

Treat the generated map as raster. Do not claim it is fully vector-editable. State that top-layer symbols and text are editable. If the user explicitly requires every road and railway segment to be editable, recreate those lines as native paths only when geometry can be traced accurately.

Map rules

• Fill the map frame edge to edge; do not leave blank bands.
• Default to an approximately 2 km map extent for dense urban projects so individual building footprints remain recognizable.
• Treat 2 km as a starting point, not a fixed rule. Change the extent whenever the project address, parcel, selection boundary, or analysis purpose changes.
• Use roughly 1.5–2.5 km for a small urban parcel or neighborhood-scale analysis; 3–5 km for a large campus, industrial park, or district-scale site; and 5–10 km only when regional access is the main message.
• Keep the project and its selection boundary fully visible with a useful surrounding buffer. Do not crop boundary corners, adjoining blocks, or the nearest relevant transport nodes.
• Inspect the generated image at full size. Zoom in when building outlines merge into texture or labels cannot be anchored to identifiable blocks. Zoom out only when essential roads, stations, waterways, or resource nodes are clipped.
• Balance context and clarity: show the smallest geographic extent that still contains the evidence needed for the slide's claim.
• Do not draw a large jurisdiction or study-area frame unless the user explicitly requests one. A textual boundary description does not automatically authorize a visible boundary polygon.
• Make water a broad muted cyan/gray-blue filled channel with natural banks.
• Make roads a deeper navy stroke and visibly different from water.
• Distinguish expressway, arterial, secondary road, and branch by line width.
• Follow the visible basemap geometry with natural bends, junctions, and continuity. Reject arbitrary straight lines.
• Use a continuous black/white alternating segmented metro line with no missing pieces.
• Use a separate darker, complete, evenly dashed railway line.
• When a jurisdiction boundary is requested, use a closed magenta dashed outline with subtle light-pink fill; otherwise omit it entirely.
• Distinguish the core parcel from a jurisdiction boundary. When requested, show the project parcel as a small red dash-dot closed line with no interior fill, then place the magenta SITE label and locator at its center.
• Do not add a core-parcel outline when the brief asks for only a SITE pin.
• Do not invent geographic labels. Use only names supplied by the user or verified from an authoritative source.

Transit and POI selection

• Include every materially relevant metro route and station that lies inside or immediately adjacent to the chosen map extent; do not add distant stations merely to fill space.
• Verify current station names, operating lines, planned lines, and construction status from authoritative or current sources when the distinction matters.
• Draw each metro route as a complete continuous black/white segmented curve across the visible frame. Do not show isolated fragments near station icons.
• Classify POIs by relationship to the project program, not by arbitrary color balance.
• Use orange markers for buildings or destinations with the same or a closely related function as the project, such as comparable commercial, industrial, office, cultural, or service uses.
• Use dark markers for different-function urban support facilities, especially hospitals, schools, parks, civic facilities, and residential/community resources.
• Select only decision-relevant POIs within the displayed extent. Prefer fewer readable labels over an exhaustive but crowded inventory.
• Keep marker meaning consistent across the slide and explain it in visible copy only when the template or user requests a legend.

Copy and symbol rules

• Preserve exact user copy unless shortening is explicitly permitted.
• Prefer user-supplied symbols over lookalikes.
• Use the requested orange and dark marker assets without redrawing unofficial lookalikes.
• Use a magenta SITE label and locator; add a small red dash-dot parcel line only when requested.
• Do not add cardinal-direction callouts unless requested.

Deliverables

• Final .pptx in a distinct output path.
• Project-bound final generated map asset saved outside temporary/model-cache directories.
• Full-slide PNG used for QA in scratch space.
• Brief handoff summarizing editable versus raster elements and validation result.