Convert architecture documents (blueprints, stakeholder presentations) from Markdown to professionally formatted Word (.docx) files. Applies corporate styling, embeds PNG diagrams, and creates presentation-ready documents.
Converts Markdown architecture documents into professionally formatted Word (.docx) files with corporate styling and embedded diagrams.
npx claudepluginhub navraj007in/architecture-cowork-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Convert architecture documents to professionally formatted Word documents (.docx) ready for stakeholder presentations, board meetings, and executive approvals.
Perfect for: Executive presentations, board decks, budget approvals, RFPs, investor updates, compliance documentation
Use this skill when you need to:
Input: Markdown file (blueprint or stakeholder presentation) Output: Professionally formatted .docx file
Input: stakeholder-presentation.md (from /architect:stakeholder-doc)
Output: stakeholder-presentation.docx
Formatting:
diagrams/ folder)Input: blueprint.md (from /architect:blueprint)
Output: architecture-blueprint.docx
Formatting:
Input: Sprint backlog section or standalone sprint doc
Output: sprint-backlog.docx
Formatting:
Analyze markdown to determine document type:
Use Pandoc (preferred) or markdown-to-docx library:
pandoc stakeholder-presentation.md \
-o stakeholder-presentation.docx \
--reference-doc=template.docx \
--toc \
--toc-depth=3 \
--number-sections \
--highlight-style=tango
Pandoc features:
If Pandoc not available, use Node.js library:
npm install markdown-to-docx
# Convert with basic styling
markdown-to-docx --input stakeholder-presentation.md \
--output stakeholder-presentation.docx \
--style professional
Use reference template (template.docx) with:
Replace markdown image references with embedded PNGs:
Markdown:
*System components and how they connect*
DOCX conversion:
diagrams/architecture-container.png as inline imageAuto-numbering: Figures numbered sequentially (Figure 1, Figure 2, etc.)
Markdown:
- [ ] Budget approved
- [x] Timeline approved
DOCX:
Markdown:
| Component | Cost |
|-----------|------|
| Frontend | $20 |
DOCX:
Markdown:
```bash
npm install
```
DOCX:
Markdown:
> **Note**: Start with managed platforms, upgrade to AWS when >100K users.
DOCX:
For stakeholder presentations, generate professional cover page:
═══════════════════════════════════════════════════════
[PROJECT NAME]
Architecture & Implementation Plan
───────────────────────────────────────────────────────
Prepared for: [Stakeholder Name/Team]
Prepared by: Architect AI
Date: [Generation Date]
Version: 1.0
[Optional: Company Logo]
═══════════════════════════════════════════════════════
Styling:
Generate TOC with:
Example:
Table of Contents
Executive Summary................................................1
Solution Overview................................................3
High-Level Architecture Diagram................................3
Solution Components............................................4
Key Capabilities...............................................5
Technology Stack & Decisions.....................................6
Decision 1: Database - PostgreSQL..............................6
Decision 2: Hosting - Managed Platforms........................7
Cost Breakdown...................................................9
Infrastructure Costs..........................................9
Development Costs.............................................10
[...]
For stakeholder presentations, format approval section as form:
═══════════════════════════════════════════════════════
APPROVAL SECTION
═══════════════════════════════════════════════════════
Budget Approved: ☐ Yes ☐ No
Timeline Approved: ☐ Yes ☐ No
Technical Approach: ☐ Yes ☐ No
Risk Mitigation: ☐ Yes ☐ No
───────────────────────────────────────────────────────
Decision Required By: ____________________
Approved By: __________________________ Date: _________
Title: _________________________________________________
Signature: ____________________________________________
───────────────────────────────────────────────────────
When invoked, generate:
📄 Converting markdown to Word document...
✅ Detected document type: Stakeholder Presentation
✅ Parsed markdown structure (11 sections, 47 pages)
✅ Embedded 6 PNG diagrams from diagrams/ folder
✅ Applied corporate styling (Calibri, professional theme)
✅ Generated table of contents (3 levels, 28 entries)
✅ Formatted 8 tables with headers and alternating rows
✅ Added cover page with metadata
✅ Added approval section with signature fields
📄 stakeholder-presentation.docx created (2.4 MB, 47 pages)
Ready for stakeholder review!
Next steps:
- Review document in Microsoft Word or Google Docs
- Customize cover page with company logo
- Adjust approval checklist if needed
- Export to PDF for distribution: File → Export → PDF
Optional parameters (ask user if they want to customize):
Default behavior: Blue color scheme, Letter size, Calibri font, "Confidential" footer, version 1.0.
/architect:export-docx
# → stakeholder-presentation.docx
/architect:export-docx --pdf
# → stakeholder-presentation.docx
# → stakeholder-presentation.pdf
/architect:export-docx --logo=logo.png --color=corporate --size=a4
# → stakeholder-presentation.docx (A4, corporate colors, with logo)
#!/bin/bash
# Convert markdown to DOCX with full styling
INPUT="stakeholder-presentation.md"
OUTPUT="stakeholder-presentation.docx"
TEMPLATE="template.docx" # Reference template with corporate styling
# Create reference template if it doesn't exist
if [ ! -f "$TEMPLATE" ]; then
pandoc --print-default-data-file reference.docx > "$TEMPLATE"
# Customize template.docx with corporate styling
fi
# Convert with Pandoc
pandoc "$INPUT" \
-o "$OUTPUT" \
--reference-doc="$TEMPLATE" \
--toc \
--toc-depth=3 \
--number-sections \
--highlight-style=tango \
--resource-path=".:diagrams" \
--metadata title="Architecture & Implementation Plan" \
--metadata author="Architect AI" \
--metadata date="$(date +%Y-%m-%d)"
echo "✅ Created $OUTPUT"
# Generate default template
pandoc --print-default-data-file reference.docx > template.docx
# Customize template.docx:
# 1. Open in Microsoft Word
# 2. Modify styles (Heading 1, Heading 2, Normal, etc.)
# 3. Set page layout (margins, headers, footers)
# 4. Configure table styles
# 5. Save and close
# Template is now ready for repeated use
# Option A: Use LibreOffice (headless)
libreoffice --headless \
--convert-to pdf \
stakeholder-presentation.docx \
--outdir .
# Option B: Use Pandoc with LaTeX
pandoc stakeholder-presentation.md \
-o stakeholder-presentation.pdf \
--pdf-engine=xelatex \
--toc \
--number-sections
/architect:export-diagrams first for embedded images."/architect:stakeholder-doc first."# 1. Generate blueprint
/architect:blueprint
# 2. Create stakeholder presentation
/architect:stakeholder-doc
# 3. Export diagrams to PNG
/architect:export-diagrams
# 4. Convert to Word document
/architect:export-docx
# Result: stakeholder-presentation.docx ready for executives!
A successful DOCX export should:
stakeholder-presentation.docx # Main output (2-5 MB)
stakeholder-presentation.pdf # Optional PDF export
template.docx # Reference template (reusable)
File sizes:
Replace default template with corporate template:
# 1. Create corporate template
# - Open template.docx in Word
# - Apply corporate fonts, colors, logo
# - Save as corporate-template.docx
# 2. Use custom template
/architect:export-docx --template=corporate-template.docx
Export multiple documents at once:
# Export all markdown files in current directory
/architect:export-docx --batch *.md
# Output:
# ✅ blueprint.docx
# ✅ stakeholder-presentation.docx
# ✅ sprint-backlog.docx
Automatically version documents:
/architect:export-docx --version=2.1
# Output: stakeholder-presentation-v2.1.docx
# Footer: "Version 2.1 - Generated 2026-02-07"
/architect:export-docx
# Output:
# ✅ stakeholder-presentation.docx created (47 pages, 2.4 MB)
/architect:export-docx --logo=acme-logo.png --pdf
# Output:
# ✅ stakeholder-presentation.docx (with Acme logo)
# ✅ stakeholder-presentation.pdf
/architect:export-docx blueprint.md --output=architecture-blueprint.docx
# Output:
# ✅ architecture-blueprint.docx (19 sections, 87 pages)
Before considering export complete, verify:
Solution: Adjust max-width in Pandoc:
pandoc ... --metadata max-width=6in
Solution: Ensure --toc flag is used and H2/H3 headings exist
Solution: Use --highlight-style=tango and monospace font in template
Solution: Install required LaTeX packages or use LibreOffice conversion
Solution: Ensure UTF-8 encoding:
pandoc ... --metadata charset=utf-8
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.