Help us improve
Share bugs, ideas, or general feedback.
From solution-factory
Stage 3 orchestrator for the Solution Factory — Polish. Generates visuals using the canonical toolchain (Napkin, Figma+Mermaid, PowerPoint native, higgsfield with nano banana / chatgpt 2 / Seedance, Flaticon). Formats markdown to output (16:9 PPTX via PowerPoint MCP, 8.5×11 PDF via Word MCP, optional Composable DXP microsite via Vercel). Applies brand (Slalom default vs. Composable DXP secondary). Output: PPTX/PDF/HTML files at the top level of WIP. Also known as: visual + format + brand stage, polish runner.
npx claudepluginhub bpainter/composable-dxp-claude-marketplace --plugin solution-factoryHow this skill is triggered — by the user, by Claude, or both
Slash command
/solution-factory:solution-factory-polishThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Take 8 markdown deliverables and convert them to formatted output (PPTX / PDF / HTML), with visuals generated and brand applied. Files sit at the top level of `WIP/[solution-name]/` alongside the markdown sources — *not* in a `final/` subfolder.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Take 8 markdown deliverables and convert them to formatted output (PPTX / PDF / HTML), with visuals generated and brand applied. Files sit at the top level of WIP/[solution-name]/ alongside the markdown sources — not in a final/ subfolder.
solution-factory-create-flow pipeline (auto-routed)/solution-polish directlyFor the canonical toolchain, see ../../references/solution-factory-toolchain.md — every visual decision routes through it. For brand assets, the canonical paths are:
70_Templates/Slalom_Brand_Assets/Slalom_PowerPoint_16x9_Aug2025.potx + Slalom_Brand_Guide_Feb2025.pdf + slalom-design-system/70_Templates/Composable_DXP_Brand_Assets/future-is-composable-design-system/ (CSS tokens, JSX, marks)[VISUAL: ...] tags)Walk every markdown deliverable in WIP. For each [VISUAL: ...] tag, route per the toolchain:
[VISUAL: Diagram — Napkin, ...] → call Napkin via web/MCP. Style: corporate for Slalom default, corporate or clean for Composable DXP. Save as PNG to assets/diagrams/.[VISUAL: Diagram — Figma, ...] → author Mermaid syntax → render via Figma → export. Save to assets/diagrams/.[VISUAL: Chart — PowerPoint, ...] → defer to Step 2. PowerPoint native charts are inserted at slide composition.[VISUAL: Image — higgsfield, nano banana] → call mcp__higgsfield__balance to confirm credits, then mcp__higgsfield__generate_image. If nano banana fails or output is off-brand, fall back to chatgpt image 2. Save to assets/images/.[VISUAL: Video — higgsfield, seedance] → call mcp__higgsfield__generate_video. Save to assets/videos/.[VISUAL: Icon — Flaticon, ...] → source from Flaticon. Constraint: lined OR colored, no hand-drawn. Same style across the kit. Save to assets/icons/.[VISUAL: Stock — placeholder] → check Slalom Creative Library first. Higgsfield only as fallback.Pre-check: before any heavy higgsfield session, call mcp__higgsfield__balance. If credits are low, AskUserQuestion: "Higgsfield credits at X. Proceed, top up first, or skip image generation?"
Visual review: before Step 2, walk the visual review checklist from the toolchain reference. Same icon style? Same chart style? Diagrams matching brand? No hand-drawn icons surviving?
For each deliverable, format to its output type using the right MCP:
| Deliverable | Output | MCP |
|---|---|---|
| 01 One-Pager | 16:9 PPTX (1 slide) + PDF export | PowerPoint MCP, then export_pdf |
| 02 Sales Enablement Kit | 16:9 PPTX (~30–40 slides) | PowerPoint MCP |
| 03 Discovery Workshop | 16:9 PPTX (4–6 slides) + 8.5×11 PDF facilitator guide | PowerPoint MCP + Word MCP |
| 04 First Call Deck | 16:9 PPTX (20–40 slides) + PDF for client share | PowerPoint MCP, then export_pdf |
| 05 Case Study | 16:9 PPTX (1–2 slides) + 8.5×11 PDF (long form) | PowerPoint MCP + Word MCP |
| 06 Email Templates | Markdown source + .txt export per template | Markdown |
| 07 Handoff Packet | Markdown only | Markdown |
| 08 Marketing Handoff | Markdown only | Markdown |
PowerPoint workflow:
Slalom_PowerPoint_16x9_Aug2025.potx as the base via mcp__PowerPoint__By_Anthropic___open_presentation.[deliverable-name].pptx in the WIP folder via save_presentation.add_slide + set_slide_title + add_text_to_slide + insert_image (for visuals from assets/).export_pdf.Word workflow:
mcp__Word__By_Anthropic___create_document with the deliverable name.insert_text + format_text.assets/ for visuals.export_pdf.Slalom default:
70_Templates/Slalom_Brand_Assets/slalom-design-system/project/assets/Slalom_Brand_Guide_Feb2025.pdf (or the framework distillation at 50_Knowledge/Frameworks/Slalom_Brand/Color_System)50_Knowledge/Frameworks/Slalom_Brand/Iconography practice overrideComposable DXP secondary:
70_Templates/Composable_DXP_Brand_Assets/future-is-composable-design-system/project/assets/project/colors_and_type.css (apply to PPTX theme)project/ui_kits/microsite/If the kit is Composable DXP secondary AND tier is Complex, AskUserQuestion:
Question: "This is a Complex Composable DXP solution. Want to generate an encapsulated microsite as an additional output?"
Options:
1. Yes, deploy to Vercel as password-protected static site (Recommended for Complex tier)
2. Yes, but generate for SharePoint deployment (less interactive)
3. No, PPT/PDF outputs are sufficient
If yes (Option 1):
70_Templates/Composable_DXP_Brand_Assets/future-is-composable-design-system/)/index, /pitch, /discovery, /case-studies, /pricing, /contact, /assets)mcp__vercel__deploy_to_vercel. Password protect.If yes (Option 2): generate static HTML; package for SharePoint upload. User uploads manually.
If no: skip.
For non-Complex tiers OR Slalom default brand: skip Step 4 entirely.
After Step 2, before Ship, AskUserQuestion:
Question: "Polish complete. Review the visual output?"
Options:
1. Yes, walk me through the visual review checklist
2. Yes, open the One-Pager + First Call Deck for direct visual review
3. Skip review and proceed to Ship
brand:brand-voice-tone or consulting:consulting-humanize.design:design-imagery (advice for image direction before higgsfield prompting)design:design-visualization (advice for diagram direction before Napkin/Figma)design:design-presentation (advice for slide composition)design:design-iconography (advice for icon family selection)brand:brand-voice-tone (advice for voice adherence)consulting:consulting-humanize (humanization pass)vercel:vercel-deploy-pipeline (microsite deployment)software-engineering:software-engineering-shadcn-component (microsite component composition for Composable DXP)anthropic-skills:pptx (PPTX authoring)anthropic-skills:docx (Word authoring)../../references/solution-factory-toolchain.md. Cite, don't repeat.composable-dxp-migration." → run all 4 steps.../../references/solution-factory-foundations.md../../references/solution-factory-toolchain.md — the canonical toolchain reference60_Digital_Manufacturing/Solution_Factory/Pipeline.md../solution-factory-create-flow/SKILL.md../solution-factory-ship/SKILL.md — next stage