ワンクリックでManusで任意のスキルを実行

deck-validate-project

スター24

フォーク8

更新日2026年4月29日 15:58

Validate and audit a deck project for correctness. Use this when asked to validate, audit, polish, review, check, or verify slides.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

deckio-art

deckio-art/deck-engine

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

グラフィックデザイナー芸術・デザイン・エンタメ・スポーツ・メディア職·SOC 27-1024

SKILL.md

readonly

このリポジトリの他の Skills

同じリポジトリ

deck-add-disclosure

deckio-art/deck-engine

Guide for adding progressive disclosure (step-by-step / click-to-reveal builds) to a slide. Use this when asked to make a slide reveal content one step at a time, add build steps, or fix a disclosure slide that exports blank.

2026-06-1324

deck-add-slide

deckio-art/deck-engine

Guide for adding a new slide to a deck project. Use this when asked to create, add, or build a new slide component.

2026-05-1824

deck-optimize-space

deckio-art/deck-engine

Find recoverable disk space in a deck project (unused media, stale exports, generated caches) without ever silently deleting user work. Use this when asked to optimize, slim down, clean up, free space, prune, or shrink a deck.

2026-05-0224

deck-inspect

deckio-art/deck-engine

Capture a screenshot of the deck app to visually inspect slides. Use this when asked to look at, see, view, inspect, check visually, or preview a slide. Works in VS Code, Copilot CLI, deck-launcher, and containers.

2026-03-2224

deck-port-powerpoint

deckio-art/deck-engine

Port a PowerPoint, PPTX, PDF export, or slide-image deck into native DECKIO slides. Use this when asked to convert, map, rebuild, port, digitize, or translate presentation slides into DeckIO. Includes source extraction, slide classification, amplification-first redesign, data extraction, native slide rebuilding, and validation.

2026-03-2124

deck-sketch

deckio-art/deck-engine

Sketch a slide on Whiteboard, capture the sketch, and use it as inspiration to create a new slide. Use this when the user wants to draw, sketch, or wireframe a slide before building it.

2026-03-1324

name	deck-validate-project
description	Validate and audit a deck project for correctness. Use this when asked to validate, audit, polish, review, check, or verify slides.

Validate & Audit a Deck Project

Step 0 — Read `deck.config.js`

Open deck.config.js and read:

theme
designSystem
slides

Then resolve the active theme descriptor using the same rules as deck-add-slide:

Built-ins: read dark.md, light.md, or shadcn.md from the engine package descriptors folder
Custom themes: read the project's custom descriptor.md or *.descriptor.md
If no custom descriptor exists, fall back to the built-in descriptor implied by designSystem

Use the descriptor as the source of truth for required structure, required tokens, allowed components, decorative elements, and anti-patterns.

Step 1: Audit `deck.config.js`

Verify:

Every imported slide resolves to an existing file in src/slides/
Every imported slide appears in the slides array
There are no unused imports or undefined slide entries
slides is non-empty
theme and designSystem were not changed accidentally during unrelated work

Step 2: Validate slide structure against the descriptor

For each slide .jsx file in src/slides/, check:

Common checks (all themes)

Imports { Slide, BottomBar } from '@deckio/deck-engine'
Imports Editable from '@deckio/deck-engine' when the slide contains user-facing text
Uses <Slide index={index} className={styles.xxx}>
Uses a wrapper that includes content-frame content-gutter
Places <BottomBar /> as the last child inside <Slide>
Uses consistent BottomBar text across slides
Wraps titles, subtitles, body copy, captions, semantic labels, metrics, badges, list items, quotes, and editable footer text in <Editable> with unique semantic IDs
Leaves decorative glyphs, icons, fixed counters, and watermarks outside <Editable>
Does not nest <Editable> elements

Descriptor-driven checks

Read the descriptor and verify the slide matches:

its Exact JSX skeleton
its Decorative elements available section
its Available components section
its Anti-patterns section

Examples:

If the descriptor requires accent-bar and orbs, those must be present
If the descriptor forbids accent-bar, orb, or deep-space ornament, they must be absent
If the descriptor allows shadcn / ReactBits imports, imports must stay inside that ecosystem

Step 3: Validate CSS against the descriptor

For each .module.css file, check:

Common checks (all themes)

Root class includes padding: 0 0 44px 0
No flex: 1 on the body wrapper
No redundant flex-direction: column on the slide root
No obvious overflow-causing patterns

Descriptor-driven checks

Read the descriptor and verify the CSS matches:

its Exact CSS skeleton
its Token table
its Anti-patterns

Examples:

If the descriptor requires var(--background), var(--card), var(--border), or other semantic tokens, use those exact names
If the descriptor forbids var(--bg-deep), var(--surface), var(--text), or var(--text-muted), flag them
If the descriptor forbids orb positioning classes or card ::before bars, flag them

Step 4: Check companion files

Every .jsx slide in src/slides/ should have a matching .module.css
No orphaned .module.css files without a matching .jsx

Step 5: Validate theme/design-system alignment

Check whether the project configuration and descriptor agree:

If designSystem === 'shadcn', the project should visually and structurally follow the shadcn descriptor rules
If designSystem is not 'shadcn', the project should follow a default DECKIO descriptor such as dark or light
If the descriptor and designSystem disagree, report an architecture mismatch even if individual slides render

When `designSystem === 'shadcn'`: validate preinstalled components

Verify the preinstalled component set is intact:

If any preinstalled file is missing, report it as a scaffold integrity issue — the file may have been accidentally deleted.

Validate MCP integration

.vscode/mcp.json exists and contains a shadcn server entry
components.json has registries with @react-bits configured
components.json has correct aliases (@/components, @/lib/utils, @/components/ui)

If MCP config is missing, the author loses the primary component expansion workflow.

Validate component usage patterns

For each slide in a shadcn deck, check:

Slides use real <Card>, <Badge>, <Button>, <Alert>, <Separator> imports instead of CSS-imitation divs where applicable
No hand-built card-like patterns when the Card component is available
No raw <button> or <span className={styles.badge}> when real components exist
CSS Modules focus on layout (grid, spacing, positioning) not component surface styling

Step 6: Report results

Summarize:

Active theme detected
Design system detected
Descriptor used
Number of slides validated
Descriptor mismatches found
Any issues found and fixed
Overall project health: pass or issues found

deck-validate-project

Validate & Audit a Deck Project

Step 0 — Read `deck.config.js`

Step 1: Audit `deck.config.js`

Step 2: Validate slide structure against the descriptor

Common checks (all themes)

Descriptor-driven checks

Step 3: Validate CSS against the descriptor

Common checks (all themes)

Descriptor-driven checks

Step 4: Check companion files

Step 5: Validate theme/design-system alignment

When `designSystem === 'shadcn'`: validate preinstalled components

Validate MCP integration

Validate component usage patterns

Step 6: Report results

Quick checklist

Validate & Audit a Deck Project

Step 0 — Read `deck.config.js`

Step 1: Audit `deck.config.js`

Step 2: Validate slide structure against the descriptor

Common checks (all themes)

Descriptor-driven checks

Step 3: Validate CSS against the descriptor

Common checks (all themes)

Descriptor-driven checks

Step 4: Check companion files

Step 5: Validate theme/design-system alignment

When `designSystem === 'shadcn'`: validate preinstalled components

Validate MCP integration

Validate component usage patterns

Step 6: Report results

Quick checklist

deck-validate-project

このリポジトリの他の Skills

このリポジトリの他の Skills

Validate & Audit a Deck Project

Step 0 — Read deck.config.js

Step 1: Audit deck.config.js

Step 2: Validate slide structure against the descriptor

Common checks (all themes)

Descriptor-driven checks

Step 3: Validate CSS against the descriptor

Common checks (all themes)

Descriptor-driven checks

Step 4: Check companion files

Step 5: Validate theme/design-system alignment

When designSystem === 'shadcn': validate preinstalled components

Validate MCP integration

Validate component usage patterns

Step 6: Report results

Quick checklist

Validate & Audit a Deck Project

Step 0 — Read deck.config.js

Step 1: Audit deck.config.js

Step 2: Validate slide structure against the descriptor

Common checks (all themes)

Descriptor-driven checks

Step 3: Validate CSS against the descriptor

Common checks (all themes)

Descriptor-driven checks

Step 4: Check companion files

Step 5: Validate theme/design-system alignment

When designSystem === 'shadcn': validate preinstalled components

Validate MCP integration

Validate component usage patterns

Step 6: Report results

Quick checklist

Step 0 — Read `deck.config.js`

Step 1: Audit `deck.config.js`

When `designSystem === 'shadcn'`: validate preinstalled components

Step 0 — Read `deck.config.js`

Step 1: Audit `deck.config.js`

When `designSystem === 'shadcn'`: validate preinstalled components