feat: add pptify plugin

.github/plugin/marketplace.json

@@ -630,6 +630,12 @@
       "description": "Complete toolkit for developing Power Platform custom connectors with Model Context Protocol integration for Microsoft Copilot Studio",
       "version": "1.0.0"
     },
+    {
+      "name": "pptify",
+      "source": "pptify",
+      "description": "Generate production-ready PowerPoint decks with pptify skills, source ingestion, design-context selection, coordinate-explicit slide specs, visual assets, runtime tooling, and audit-driven quality gates.",
+      "version": "1.0.0"
+    },
     {
       "name": "project-documenter",
       "source": "project-documenter",

docs/README.plugins.md

@@ -72,6 +72,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-plugins) for guidelines on how t
 | [power-bi-development](../plugins/power-bi-development/README.md) | Comprehensive Power BI development resources including data modeling, DAX optimization, performance tuning, visualization design, security best practices, and DevOps/ALM guidance for building enterprise-grade Power BI solutions. | 8 items | power-bi, dax, data-modeling, performance, visualization, security, devops, business-intelligence |
 | [power-platform-architect](../plugins/power-platform-architect/README.md) | Solution Architect for the Microsoft Power Platform, turning business requirements into functioning Power Platform solution architectures. | 1 items | power-platform, power-platform-architect, power-apps, dataverse, power-automate, power-pages, power-bi |
 | [power-platform-mcp-connector-development](../plugins/power-platform-mcp-connector-development/README.md) | Complete toolkit for developing Power Platform custom connectors with Model Context Protocol integration for Microsoft Copilot Studio | 3 items | power-platform, mcp, copilot-studio, custom-connector, json-rpc |
+| [pptify](../plugins/pptify/README.md) | Generate production-ready PowerPoint decks with pptify skills, source ingestion, design-context selection, coordinate-explicit slide specs, visual assets, runtime tooling, and audit-driven quality gates. | 6 items | pptify, powerpoint, pptx, presentations, deck-generation, slides, design-context, visual-assets, quality-gates |
 | [project-documenter](../plugins/project-documenter/README.md) | Generate professional project documentation with draw.io architecture diagrams and Word (.docx) output with embedded images. Automatically discovers any project's technology stack and produces Markdown, diagrams, PNG exports, and a formatted Word document. | 3 items | documentation, architecture-diagrams, drawio, word-document, docx, png-images, c4-model, project-summary, auto-discovery |
 | [project-planning](../plugins/project-planning/README.md) | Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams. | 15 items | planning, project-management, epic, feature, implementation, task, architecture, technical-spike |
 | [python-mcp-development](../plugins/python-mcp-development/README.md) | Complete toolkit for building Model Context Protocol (MCP) servers in Python using the official SDK with FastMCP. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance. | 2 items | python, mcp, model-context-protocol, fastmcp, server-development |

docs/README.skills.md

@@ -272,6 +272,12 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [power-platform-architect](../skills/power-platform-architect/SKILL.md)<br />`gh skills install github/awesome-copilot power-platform-architect` | Use this skill when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including component selection and Mermaid.js diagrams. | None |
 | [power-platform-mcp-connector-suite](../skills/power-platform-mcp-connector-suite/SKILL.md)<br />`gh skills install github/awesome-copilot power-platform-mcp-connector-suite` | Generate complete Power Platform custom connector with MCP integration for Copilot Studio - includes schema generation, troubleshooting, and validation | None |
 | [powerbi-modeling](../skills/powerbi-modeling/SKILL.md)<br />`gh skills install github/awesome-copilot powerbi-modeling` | Power BI semantic modeling assistant for building optimized data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimizing model performance. Triggers on queries about DAX calculations, table relationships, dimension/fact table design, naming conventions, model documentation, cardinality, cross-filter direction, calculation groups, and data model best practices. Always connects to the active model first using power-bi-modeling MCP tools to understand the data structure before providing guidance. | `references/MEASURES-DAX.md`<br />`references/PERFORMANCE.md`<br />`references/RELATIONSHIPS.md`<br />`references/RLS.md`<br />`references/STAR-SCHEMA.md` |
+| [pptify-context-prep](../skills/pptify-context-prep/SKILL.md)<br />`gh skills install github/awesome-copilot pptify-context-prep` | Prepare source material and design context before authoring a pptify deck spec. Use when converting documents, building RAPTOR summaries, analyzing reference PPTX decks, or selecting and loading pptify-design profiles. | `references/design-profiles.md` |
+| [pptify-deck-generation](../skills/pptify-deck-generation/SKILL.md)<br />`gh skills install github/awesome-copilot pptify-deck-generation` | Generate PPTX decks end to end with pptify. Use when creating PowerPoint slides from prompts, source material, reference PPTX analysis, coordinate-explicit layout trees, or pptify JSON specs. | None |
+| [pptify-quality-gates](../skills/pptify-quality-gates/SKILL.md)<br />`gh skills install github/awesome-copilot pptify-quality-gates` | Validate and repair pptify PPTX artifacts. Use when checking deck specs, PPTX packages, audits, coordinate-explicit layout trees, collisions, text overflows, warnings, visual hierarchy, asset layering, or reference deck alignment. | `references/audit-checklist.md` |
+| [pptify-slide-spec](../skills/pptify-slide-spec/SKILL.md)<br />`gh skills install github/awesome-copilot pptify-slide-spec` | Author or repair coordinate-explicit pptify JSON deck specs. Use when writing layout_tree groups, objects, bboxes, tables, images, lines, shapes, type scale, or collision-safe content. | None |
+| [pptify-tooling](../skills/pptify-tooling/SKILL.md)<br />`gh skills install github/awesome-copilot pptify-tooling` | Command reference for pptify plugin tools. Use when looking up install commands, plugin script syntax, or the workspace reality check. | `references/toolkit-setup.md` |
+| [pptify-visual-assets](../skills/pptify-visual-assets/SKILL.md)<br />`gh skills install github/awesome-copilot pptify-visual-assets` | Find, generate, and place visual assets for pptify PPTX decks. Use when adding icons, images, SVGs, raster conversions, infographics, image placeholders, or asset-backed slide objects. | None |
 | [pr-dashboard](../skills/pr-dashboard/SKILL.md)<br />`gh skills install github/awesome-copilot pr-dashboard` | Open a GitHub PR dashboard in the browser. Use when the user asks to see their pull requests, open the PR dashboard, show PRs for a date range, or check PR status. Trigger phrases include "show my PRs", "open PR dashboard", "pull request dashboard". | `assets/dashboard.html`<br />`scripts/lib`<br />`scripts/pr-dashboard-cli.mjs` |
 | [pr-screenshots](../skills/pr-screenshots/SKILL.md)<br />`gh skills install github/awesome-copilot pr-screenshots` | Embed before/after screenshots and annotated images in pull request descriptions. Covers PR description patterns, image upload for Azure DevOps and GitHub, and sizing best practices. | None |
 | [prd](../skills/prd/SKILL.md)<br />`gh skills install github/awesome-copilot prd` | Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis. | None |

eng/update-readme.mjs

@@ -302,8 +302,8 @@ function generateInstructionsSection(instructionsDir) {
     return { file, filePath, title };
   });
 
-  // Sort by title alphabetically
-  instructionEntries.sort((a, b) => a.title.localeCompare(b.title));
+  // Sort by title alphabetically with a fixed locale so generated output is stable across OSes.
+  instructionEntries.sort((a, b) => a.title.localeCompare(b.title, "en"));
 
   console.log(`Found ${instructionEntries.length} instruction files`);
 

plugins/pptify/.github/plugin/plugin.json

@@ -0,0 +1,29 @@
+{
+  "name": "pptify",
+  "description": "Generate production-ready PowerPoint decks with pptify skills, source ingestion, design-context selection, coordinate-explicit slide specs, visual assets, runtime tooling, and audit-driven quality gates.",
+  "version": "1.0.0",
+  "author": {
+    "name": "PPTify maintainers"
+  },
+  "repository": "https://github.com/github/awesome-copilot",
+  "license": "MIT",
+  "keywords": [
+    "pptify",
+    "powerpoint",
+    "pptx",
+    "presentations",
+    "deck-generation",
+    "slides",
+    "design-context",
+    "visual-assets",
+    "quality-gates"
+  ],
+  "skills": [
+    "./skills/pptify-context-prep/",
+    "./skills/pptify-deck-generation/",
+    "./skills/pptify-quality-gates/",
+    "./skills/pptify-slide-spec/",
+    "./skills/pptify-tooling/",
+    "./skills/pptify-visual-assets/"
+  ]
+}

plugins/pptify/README.md

@@ -0,0 +1,47 @@
+# PPTify Plugin
+
+Generate production-ready PowerPoint decks with pptify skills, source ingestion, design context, coordinate-explicit slide specs, visual assets, runtime tooling, and audit-driven quality gates.
+
+## Installation
+
+```bash
+copilot plugin install pptify@awesome-copilot
+```
+
+## What's Included
+
+### Skills
+
+| Skill | Description |
+| --- | --- |
+| `pptify-context-prep` | Prepare source material and design context before authoring a pptify deck spec. |
+| `pptify-deck-generation` | Generate PPTX decks end to end from prompts, source material, reference PPTX analysis, coordinate-explicit layout trees, or pptify JSON specs. |
+| `pptify-quality-gates` | Validate and repair PPTX artifacts by checking specs, PPTX packages, audits, layout trees, collisions, text overflows, warnings, visual hierarchy, asset layering, and reference deck alignment. |
+| `pptify-slide-spec` | Author or repair coordinate-explicit pptify JSON deck specs with layout tree groups, objects, bounding boxes, tables, images, lines, shapes, type scale, and collision-safe content. |
+| `pptify-tooling` | Look up pptify install commands, plugin script syntax, and workspace reality checks. |
+| `pptify-visual-assets` | Find, generate, and place icons, images, SVGs, raster conversions, infographics, image placeholders, and asset-backed slide objects. |
+
+## Optional Toolkit
+
+The bundled skills include reference material for design profile selection and manual quality checks. To run helper scripts for source prep, design context, visual assets, extraction, or audits, users can optionally install the PPTify toolkit from its source repository. The current external toolkit does not provide an importable `pptify` renderer module.
+
+Do not clone or install the external toolkit automatically. Install it only when the user explicitly asks to use helper scripts:
+
+```powershell
+git clone https://github.com/kimtth/agent-pptify-kit
+cd agent-pptify-kit
+uv sync                   # base project
+uv sync --extra plugins   # add source ingestion and image helpers
+```
+
+## Usage
+
+Ask Copilot to create or repair a deck and mention `pptify`. The plugin guides the agent to collect required deck inputs, prepare source and reference context, select a design profile, author a coordinate-explicit JSON spec, build through the available PowerPoint path, and repair audit findings before reporting artifact paths.
+
+## Source
+
+Plugin skills are sourced from [kimtth/agent-pptify-kit](https://github.com/kimtth/agent-pptify-kit) for submission to [Awesome Copilot](https://github.com/github/awesome-copilot).
+
+## License
+
+MIT

skills/pptify-context-prep/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: pptify-context-prep
+description: "Prepare source material and design context before authoring a pptify deck spec. Use when converting documents, building RAPTOR summaries, analyzing reference PPTX decks, or selecting and loading pptify-design profiles."
+---
+
+# PPTify Context Prep
+
+> **Prerequisite:** Before running any plugin script in this skill, run the workspace detection check in `pptify-tooling`. If `pptify-plugin/` is absent, follow the install or graceful-degradation steps there before continuing.
+
+Use this skill before writing a deck spec. It covers two parallel preparation tracks: **source context** (documents, research, reference PPTX) and **design context** (predefined style profiles from `pptify-design`).
+
+## Source Documents
+
+- Convert long source documents to markdown before planning slides: `uv run python pptify-plugin/documents/document_to_markdown.py --source source.pdf --output-path source.md`.
+- Build a structured summary tree when a source is long or multi-topic: `uv run python pptify-plugin/documents/document_to_raptor_tree.py --markdown-path source.md --output-path source-summary.json --title "Source" --pretty`.
+- For URL-based, topic-plus-research, source-backed, or multi-source decks, combine converted/downloaded source markdown into a corpus and run the RAPTOR summary before slide planning, even when individual sources are short.
+- Record the corpus path, summary path, source count, and source URLs in `summary.source_enrichment` so enrichment evidence survives review.
+- Use the summary tree to identify audience, thesis, slide sequence, evidence, risks, and decision points.
+- Do not paste entire long documents into the deck spec; summarize into concise slide messages and cite sources in footers when needed.
+
+## Reference PPTX
+
+- Use the importable helpers in `pptify-plugin/extraction` or package inspection to inspect production complexity, slide text, style, brand, template, and layout-rhythm facts. The `python -m pptify --analyze-pptx` command is unavailable unless the core renderer package is restored.
+- Use the extracted facts as agent context when the new deck should follow a source deck's language, slide count, topic sequence, executive tone, colors, fonts, template conventions, and layout rhythm.
+- When authoring the new spec, translate `brands.primary_color`, `brands.accent_colors`, `brands.fonts`, `template.slide_size`, `template.layout_usage`, and `layout.slides[*].dominant_flow` into explicit `layout_tree` primitives, colors, typography, spacing, and coordinates.
+- Use extraction helpers when the goal is reconstructing or preserving an existing production deck rather than authoring a new editable deck.
+- For new editable decks, treat reference layout rhythm as prompt context; generated coordinates must be authored directly by the agent in `layout_tree`.
+- Never copy or mutate a referenced PPTX as the generation strategy. Use analysis as context and build a new PPTX artifact.
+
+## Design Profile Selection
+
+Load [`references/design-profiles.md`](references/design-profiles.md) for the full profile catalog with IDs, `best_for` guidance, key style signals, and license information. Use it whether or not the toolkit is installed — when the toolkit is present, it cross-checks the catalog with the live output of `design_context_catalog.py`.
+
+Use profiles from `pptify-design/sources.json`; do not invent a new design template when the user asks for predefined templates.
+
+- Use `fluent-ui-design-tokens` as the default for new decks, including Microsoft, M365, Teams, Power Platform, enterprise-aligned, general modern, stylish, product, app, pitch, or unspecified visual style requests.
+- Use `primer-primitives` for GitHub-style product, developer, or token-driven engineering decks.
+- Use `corazzon-pptx-design-styles` when a broader modern style catalog or multiple visual direction options are explicitly useful. Pick one style from the catalog and lock its palette, typography, spacing, and signature element before layout planning.
+- Use `likaku-mck-ppt-design-skill` for consulting, strategy, governance, or operations decks that need action-title discipline and structured native PPTX layouts.
+- Use `awesome-copilot-design-agents` when the agent prompt itself needs design review, UX discovery, visual hierarchy, or accessibility framing.
+- Keep source attribution and license metadata attached to the context used.
+- If no catalog profile fits, use reference PPTX analysis, search for another public source, or ask the user for a source template.
+- Record selected profile IDs, source URLs, and style lock details in `summary.design_context` before building the PPTX.
+
+Load profiles:
+
+```powershell
+uv run python pptify-plugin/design/design_context_catalog.py --list --pretty
+uv run python pptify-plugin/design/design_context_catalog.py --profile fluent-ui-design-tokens --include-context --pretty
+uv run python pptify-plugin/design/design_context_catalog.py --profile primer-primitives --include-context --pretty
+uv run python pptify-plugin/design/design_context_catalog.py --profile corazzon-pptx-design-styles --include-context --pretty
+```
+
+## Applying Context to Spec Authoring
+
+1. Put the selected profile payload into the agent context before writing `deck-spec.json`.
+2. Translate source signals into explicit `layout_tree` objects, colors, fills, lines, typography, spacing, bboxes, and z-order.
+3. Keep meaningful slide content as `classification: "content"` objects and decorative/background elements as `classification: "layout_design"` objects.
+4. Use source CSS or reference deck rhythm only as design evidence; final coordinates must be authored directly in inches.
+5. Add at least one style-derived visible design element to every normal content slide: accent band, rule, card shell, grid cell, diagram primitive, shape motif, image treatment, or pattern. A plain title-plus-bullets slide fails the design gate.
+6. Do not treat `pptify-design` profiles as content source material; they are design context only.
+
+## Source-to-Deck Planning
+
+- Convert source material into one message per slide before authoring visual structure.
+- Treat charts and dashboard-style slides as source-evidence-driven exhibits; do not create generic metric or dashboard slides when the source corpus does not provide relevant data.
+- Preserve important terminology, product names, metrics, dates, and user-provided wording.
+- Reduce dense narrative into executive slide titles plus short sections.
+- Track open assumptions in speaker notes or audit-facing summary fields instead of overcrowding slides.
+
+## Restrictions
+
+- Do not copy external fonts, icon packs, photos, or binary assets unless their license and source are explicitly added.
+- Do not claim the output is a Primer, Fluent UI, or Awesome Copilot artifact; these are context sources for a new `pptify` deck.
+- Do not let source CSS override pptify quality gates: built decks still need zero content collisions and zero text overflows.
+- Do not accept default PowerPoint theme colors, Calibri-only text boxes, plain white backgrounds, or placeholder-style bullet layouts as a finished design.