pptx-deck-context

어떤 스킬인가요?

Use when preparing the narrative, sources, and design context for a new editable PPTX deck.

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

# Design Profile Guidance

Use a profile as design evidence, then lock its palette, typography, spacing, and signature element in `summary.design_context` before coordinate authoring.

| Profile | Best for | Signals |
| --- | --- | --- |
| `fluent-ui-design-tokens` | enterprise and Microsoft-aligned decks | restrained neutrals, clear hierarchy, token-based spacing, modest radii |
| `primer-primitives` | GitHub and developer-focused decks | crisp surfaces, strong text contrast, functional accents, compact labels |
| `editorial-minimal` | executive narrative and research decks | generous whitespace, high-contrast type, limited palette, one visual motif |

## Rules

- Prefer an explicit user brand guide. Otherwise use read-only reference-deck evidence, then a documented profile.
- Record profile ID, source URL when applicable, license information when known, and the resulting style lock.
- Use public design signals for inspiration only. Do not copy proprietary images, logos, fonts, screenshots, or slide content.
- Translate the lock into explicit `layout_tree` colors, fills, typography, rules, card shells, and bboxes.

---
name: pptx-deck-context
description: "Use when preparing the narrative, sources, and design context for a new editable PPTX deck."
---

# PPTX Deck Context

Prepare the deck before coordinates or PPTX objects are authored. This skill owns the business narrative, source lineage, and design lock.

## Decision sequence

1. Confirm audience, decision, slide count, language, sources, and brand requirements.
2. Use the user-selected narrative framework. If none is specified, offer `mckinsey`, `scqa`, `pyramid`, `mece`, `action-title`, `assertion-evidence`, `exec-summary-first`, or `custom`; do not choose silently.
3. Assign stable source IDs and plan a `source_ref` for every metric, quotation, chart value, and factual claim.
4. Choose a documented design direction. Prefer a user brand guide, then read-only reference-deck evidence, then a reusable profile from `references/design-profiles.md`.
5. Record the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in `summary` before authoring slides.

## Rules

- One slide should communicate one message, with an action-style title where the framework calls for it.
- Treat design references as design evidence, not content or asset sources.
- Do not copy external fonts, images, icons, or logos without recorded licensing evidence.
- Translate design signals into explicit fills, typography, spacing, and bboxes; do not rely on an automatic layout engine.
- Keep long source material concise. Ask for a summary or decision-relevant excerpt instead of turning a deck spec into a document dump.

See `references/design-profiles.md` for reusable profile guidance.