customer-card-render

by microsoft

Generate customer-card PowerPoint content YAML from Design Thinking canonical artifacts and build using the shared PowerPoint skill pipeline - Brought to you… npx skills add https://github.com/microsoft/hve-core --skill customer-card-render Download ZIPGitHub1.2k

Customer Card Render Skill

Converts canonical Design Thinking markdown artifacts into PowerPoint skill content.yaml slide definitions and builds the final deck through the shared PowerPoint build pipeline.

Overview

This skill is a sibling to the experimental powerpoint skill. It handles the Design Thinking-specific mapping layer: extracting sections from canonical markdown artifacts and filling template-driven content.yaml files. The PowerPoint skill then owns layout rendering, theming, export, and validation.

Keeping these concerns separate means:

• Customer-card mapping logic stays independent from general PowerPoint capabilities.

• The skill can be included in collections independently.

• Layout primitives, Invoke-PptxPipeline.ps1, theming, and validation behavior are not reimplemented here.

For full PowerPoint pipeline documentation, see powerpoint/SKILL.md.

Directory Structure

.github/skills/experimental/customer-card-render/
├── SKILL.md
├── pyproject.toml
├── references/
│ └── mapping-spec.md
├── scripts/
│ └── generate_cards.py
├── templates/
│ ├── global-style.yaml
│ ├── persona.content.yaml
│ ├── problem.content.yaml
│ ├── scenario.content.yaml
│ ├── use-case-slide1.content.yaml
│ ├── use-case-slide2.content.yaml
│ ├── use-case-slide3.content.yaml
│ └── vision.content.yaml
└── tests/
 ├── fuzz_harness.py
 └── test_generate_cards.py

Supported Artifact Types

Artifact Type Slide Layout Vision Statement Single slide Problem Statement Single slide Scenario Single slide Use Case 4 slides (see below) Persona Single slide

Use Case 3-Slide Layout

Each Use Case expands into 3 consecutive slides with distinct sections:

Slide Content Slide 1 Use Case Description, Use Case Overview, Business Value, Primary User Slide 2 Secondary User, Preconditions, Steps, Data Requirements Slide 3 Equipment Requirements, Operating Environment, Success Criteria, Pain Points, Evidence

Cards are ordered by artifact type (Vision → Problem → Scenario → Use Case → Persona), then alphabetically by title within each type. Use Cases appear with all 4 slides consecutive (Slide N, N+1, N+2, N+3).

Two-Command Flow

Step 1: Generate slide YAML from canonical markdown

python .github/skills/experimental/customer-card-render/scripts/generate_cards.py \
 --canonical-dir .copilot-tracking/dt/ /canonical \
 --output-dir .copilot-tracking/dt/ /render/content

generate_cards.py CLI Reference

Flag Required Default Description --canonical-dir No <skill-root>/canonical Directory containing canonical DT markdown files --output-dir No <skill-root>/scripts/content Directory to write generated content.yaml files -v, --verbose No — Enable debug-level logging

The script reads each markdown file in --canonical-dir, detects the artifact type from frontmatter, extracts required sections, and generates content.yaml files. Vision, Problem, Scenario, and Persona artifacts produce one slide each. Use Case artifacts produce 3 consecutive slides per use case.

For the section-to-field mapping contract and Use Case 3-slide layout details, see references/mapping-spec.md.

Step 2: Build PPTX using the PowerPoint skill pipeline

./.github/skills/experimental/powerpoint/scripts/Invoke-PptxPipeline.ps1 -Action Build `
 -ContentDir .copilot-tracking/dt/ /render/content `
 -StylePath .copilot-tracking/dt/ /render/content/global/style.yaml `
 -OutputPath .copilot-tracking/dt/ /render/output/customer-cards.pptx

The PowerShell orchestrator manages virtual environment setup and dependency installation automatically via uv sync. See powerpoint/SKILL.md for the full Invoke-PptxPipeline.ps1 parameter reference, template usage, validation, and export options.

DT Coach Integration

The dt-canonical-deck prompt and the dt-coaching-foundation skill's canonical-deck reference provide opt-in workflow integration for the Design Thinking coaching agent. When a user opts in, the coaching agent offers to build customer cards at method exit points. The two-command flow above runs as part of that workflow with --canonical-dir and --output-dir resolved from the active DT project slug in .copilot-tracking/dt/.

Canonical artifacts are produced by the DT coach and live under .copilot-tracking/dt/<project-slug>/canonical/.

Content Fidelity Note: Use Case Cards

Use Case cards are split across 3 opinionated slides, each with dedicated sections:

• Slide 1: Introduces the use case with Description, Overview, Business Value, and Primary User

• Slide 2: Details execution with Secondary User, Preconditions, Steps, and Data Requirements

• Slide 3: Captures quality criteria with Equipment Requirements, Operating Environment, Success Criteria, Pain Points, and Evidence

This structure ensures all 16 Use Case sections fit legibly across 4 slides without compression. Each section appears in its own textbox with appropriate styling and heading.

For complete mapping details, see references/mapping-spec.md.