customer-card-render — скилл для Claude Code
Скилл customer-card-render превращает канонические markdown-артефакты Design Thinking в YAML-определения слайдов PowerPoint. Дальше их собирает в готовую презентацию общий пайплайн скилла powerpoint.
MIT ★ 1 627 обновлён 2026-10-25
npx skills add microsoft/hve-core --skill customer-card-render -a claude-codeЧто делает customer-card-render
Скилл берёт артефакты Design Thinking — Vision Statement, Problem Statement, Scenario, Use Case, Persona — и раскладывает их по шаблонам content.yaml. Скрипт generate_cards.py читает markdown-файлы из каталога .copilot-tracking/dt/<project-slug>/canonical, определяет тип артефакта по frontmatter и вытаскивает нужные секции.
Use Case раскрывается в 4 слайда подряд: описание и ценность, предусловия и шаги, критерии успеха и болевые точки, расширения и доказательства. Карточки сортируются по типу артефакта, внутри типа — по алфавиту названий.
Сборку PPTX скилл не делает сам. Её выполняет Invoke-PptxPipeline.ps1 из скилла powerpoint — нужно активировать его по имени и передать три пути: контент, стиль и выходной файл. Если powerpoint не резолвится, сборка не запустится.
Для работы нужны Python 3.11+, пакетный менеджер uv и сам экспериментальный скилл powerpoint. uv стоит ставить через менеджер пакетов с проверкой хеша загрузки.
Какие задачи решает
- Собрать слайды из канонических markdown-артефактов
- Разложить Use Case на 4 последовательных слайда
- Отделить маппинг карточек от рендеринга PowerPoint
- Сгенерировать
content.yamlдля пайплайна powerpoint - Упорядочить карточки по типу и алфавиту
Примеры запросов агенту
- Сгенерируй YAML карточек из
.copilot-tracking/dt/<project-slug>/canonicalв каталог.copilot-tracking/dt/<project-slug>/render/content - Запусти
generate_cards.pyс--canonical-dirна каталоге артефактов и собери PPTX через скилл powerpoint
Как установить customer-card-render
1Через Skills CLI (Vercel)
npx skills add microsoft/hve-core --skill customer-card-render -a claude-code2Вручную: положить файлы
~/.claude/skills/customer-card-render/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/customer-card-render/
1Через Skills CLI (Vercel)
npx skills add microsoft/hve-core --skill customer-card-render -a codex2Вручную: положить файлы
.agents/skills/customer-card-render/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add microsoft/hve-core --skill customer-card-render -a cursor2Вручную: положить файлы
.cursor/skills/customer-card-render/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install microsoft/hve-core .github/skills/experimental/customer-card-render2Вручную: положить файлы
.github/skills/customer-card-render/SKILL.md1Через Skills CLI (Vercel)
npx skills add microsoft/hve-core --skill customer-card-render -a gemini-cli2Командой платформы
gemini skills install https://github.com/microsoft/hve-core --path .github/skills/experimental/customer-card-renderВручную: положить файлы
.devin/skills/customer-card-render/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Claude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о customer-card-render
Как установить customer-card-render в Claude Code?
Выполни npx skills add microsoft/hve-core --skill customer-card-render -a claude-code. Скилл появится в ~/.claude/skills/customer-card-render/SKILL.md.
Что делает customer-card-render?
Читает канонические markdown-артефакты Design Thinking и генерирует content.yaml для скилла powerpoint. Рендерингом, темами и экспортом занимается сам powerpoint.
Что нужно для работы скилла?
Python 3.11+, пакетный менеджер uv и экспериментальный скилл powerpoint. Без powerpoint сборка PPTX не запустится — скилл предупредит и остановится.
Исходный текст
SKILL.md · MIT
---
name: customer-card-render
description: 'Generate customer-card PowerPoint content YAML from Design Thinking canonical artifacts and build using the shared PowerPoint skill pipeline'
license: MIT
compatibility: 'Requires Python 3.11+, uv, and the experimental powerpoint skill'
metadata:
authors: "microsoft/hve-core"
spec_version: "1.0"
last_updated: "2026-10-02"
---
# 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 packages independently.
* Layout primitives, `Invoke-PptxPipeline.ps1`, theming, and validation behavior are not reimplemented here.
For full PowerPoint pipeline documentation, activate the `powerpoint` skill by name. When it does not resolve, warn the user that the pipeline documentation and build behavior are unavailable and stop rather than reimplementing them here.
## Prerequisites
* Python 3.11+
* `uv` package manager, installed with a package manager that verifies the download against a published hash:
```bash
# Windows
winget install --id astral-sh.uv -e
# macOS / Linux (Homebrew)
brew install uv
```
To install from a release archive instead, download it from the [uv releases page](https://github.com/astral-sh/uv/releases) and check it against its `.sha256` file before extracting.
* The experimental `powerpoint` skill, activated by name, for the `Invoke-PptxPipeline.ps1` build step. When it does not resolve, warn the user that the build step is unavailable and stop.
## Directory Structure
```text
.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 4-Slide Layout
Each Use Case expands into 4 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 |
| **Slide 4** | Extensions, 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
```bash
python "<customer-card-render-skill-root>/scripts/generate_cards.py" \
--canonical-dir .copilot-tracking/dt/<project-slug>/canonical \
--output-dir .copilot-tracking/dt/<project-slug>/render/content
```
Resolve `<customer-card-render-skill-root>` from the loaded skill location before running the command.
#### 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 4 consecutive slides per use case.
For the section-to-field mapping contract and Use Case 4-slide layout details, see [references/mapping-spec.md](references/mapping-spec.md).
### Step 2: Build PPTX using the PowerPoint skill pipeline
Activate the `powerpoint` skill by name and hand it the build, supplying these three inputs:
* Content directory: `.copilot-tracking/dt/<project-slug>/render/content`
* Style path: `.copilot-tracking/dt/<project-slug>/render/content/global/style.yaml`
* Output path: `.copilot-tracking/dt/<project-slug>/render/output/customer-cards.pptx`
The `powerpoint` skill owns the `Invoke-PptxPipeline.ps1` orchestrator, its parameter reference, template usage, validation, and export options, and it manages virtual environment setup and dependency installation automatically via `uv sync`. When that skill is unavailable, warn the user that the build step cannot run and stop rather than invoking the pipeline from a guessed location.
## DT Coach Integration
The `dt-coaching-foundation` skill's `canonical-deck` reference provides 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/`.
## Running Tests
```bash
cd "<customer-card-render-skill-root>"
uv sync --group dev
uv run pytest tests/
```
Tests cover parsing, template selection, YAML emission, and regressions. The `tests/fuzz_harness.py` file is an Atheris polyglot fuzz harness for OSSF Scorecard compliance.
## 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](references/mapping-spec.md).
## Troubleshooting
| Issue | Cause | Solution |
|---------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|
| `uv` not found | uv not installed | Run `winget install --id astral-sh.uv -e` (Windows) or `brew install uv` (macOS/Linux) |
| Python not found by uv | No Python 3.11+ on PATH | Run `uv python install 3.11` |
| Template not found | `--canonical-dir` contains unknown type | Check frontmatter `type:` field against supported artifact types |
| Empty output directory | No canonical markdown files found | Confirm `--canonical-dir` path and that files have `---` frontmatter |
| PPTX build fails after generate | PowerPoint skill missing or not activated | Activate the `powerpoint` skill by name. When its content does not arrive, stop and report the build step as unavailable |
© microsoft · MIT · microsoft/hve-core