メニュー
Plan the architecture, data model, APIs, storage, publishing, embedding, versioning, collaboration, and deployment of a production web-slide runtime without implementing it.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/tph-kds/deckforge --skill deckforge-runtime-plannerコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Create, redesign, or extend a professional browser-native slide deck or presentation webapp. Activate for end-user requests such as “create slides”, “make a presentation website”, pitch decks, lessons, seminars, technical talks, web slide editors, presenter mode, slide templates, animations, or presentation UI/UX. Unless the user explicitly requests presenter-only output, deliver an editable deck with a real editor workspace, persistent save, theme/layout controls, shortcut help, and a separate clean presenter surface. Do not use for PPTX-only requests.
Add or repair export capabilities for a DeckForge-compatible or custom web slide application without redesigning the entire product. Activate for requests to add PowerPoint download, fix export issues, add multiple export formats, audit export readiness, or add PPTX export with preflight checks.
Evaluate and improve DeckForge Agent Skills by comparing baseline, current, and candidate conditions on deterministic outcome tests, trigger precision, blind review, context cost, runtime, and cross-agent consistency. Use for skill development and release gates; do not use for end-user deck creation.
SOC 職業分類に基づく
SKILL.md を表示中
| name | deckforge-runtime-planner |
| description | Plan the architecture, data model, APIs, storage, publishing, embedding, versioning, collaboration, and deployment of a production web-slide runtime without implementing it. |
| version | 3.0.0 |
Read ../../docs/ARCHITECTURE.md, ../../docs/RUNTIME_CONTRACT.md, ../deckforge/assets/deck-project.schema.json, and the relevant editor, presenter, security, performance, and publishing workflows.
Inspect the target organization, repository, deployment platform, identity model, data boundaries, and expected scale. Produce a concrete architecture with component boundaries, request and event flows, state ownership, APIs, persistence models, asset storage, authorization checks, versioning, collaboration semantics, publishing and embed policy, observability, migrations, backup and recovery, tests, and rollout phases.
Keep the serializable deck domain separate from ephemeral editor state. Keep editor, presenter, rendering, delivery, and background-processing concerns independently testable. Make assumptions, trade-offs, failure modes, and rejected alternatives explicit. Include how schema evolution, concurrent edits, autosave, optimistic updates, offline recovery, CDN caching, rendering performance, and revocation are handled.
This skill plans rather than implements. It must not invent infrastructure that conflicts with an existing coherent platform, and it must not place secrets, authorization decisions, or untrusted HTML inside DeckProject content.
