Workflows

Provision Or Refresh Repo MCP Docs

1. Run python D:\github\workspace-mcp\scripts\mcp_provision.py oves-decks
2. Preserve existing repo-authored MCP docs unless an explicit overwrite is intended
3. Update docs/agent/ and docs/context/ so they match the repo's real workflows
4. Run python D:\github\workspace-mcp\scripts\inventory_workspace_mcp.py

Build Or Update A Deck

1. Create or refine the deck intent document in docs/decks/<deck-id>.md
2. Reuse an existing deck template from src/deck-templates/ when it fits
3. Compose slides with page templates from src/page-templates/ and blocks from src/blocks/
4. Generate or update the deck implementation in src/decks/
5. Run npm run build:update:deck -- <deck-id> when using the update pipeline
6. Preview with npm run serve:deck -- <deck-id> or npm run serve:local
7. Refine the intent and implementation until the rendered result is accepted

Work In Deck Demo Before Promotion

1. Use src/decks/deck-demo/ to prove new layout, interaction, or block ideas
2. Decide the right permanent layer for the proven pattern
3. Promote that pattern into src/shared/, src/deck-templates/, src/page-templates/, src/blocks/, or docs/ as appropriate
4. Remove the one-off ownership from deck-demo
5. Reapply the promoted standard from its new reusable home and verify the result

Update The Published Deck Inventory

1. Change the canonical catalog in content/catalog/decks.json
2. Reflect the current published and draft inventory in docs/deck-depot.md
3. Keep published entries and draft entries clearly separated
4. Verify access URLs, status, and asset type are still accurate

Common Commands

• npm run build
• npm run start
• npm run build:update:deck -- <deck-id>
• npm run serve:deck -- <deck-id>
• npm run serve:local
• npm run validate:deck-catalog