oc-dash-forge

Topics in the source

• Dash Forge
• /oc-data-forge — Command Reference
• /oc-df-full behavior
• /oc-df-spec-only behavior
• Parent Skill Integration (Checkpoints)
• Checkpoint coordination
• Context inheritance
• Token handoff out

On first invocation, read references/orchestrator.md and follow its welcome protocol. Dashboard and dense-information UI designer. Takes data (from oc-data-ops mart contracts, an oc-signal-forge signal, an upstream spec, or direct input) and produces: 1. Design spec — layout, density, component choices, interaction model, design tokens 2. Working React prototype — renderable artifact with mock data, archetype-appropriate viz stack 3. Handoff packet — spec + prototype + integration notes for oc-app-architect Phase 6 build Scope: Design and prototype. Not production data wiring, not backend. Prototype uses mock data that looks realistic. -- Entry command: /oc-data-forge (or alias /oc-dash-forge). Sub-commands (the oc-df- family below) are reached from this menu. To restart from scratch, archive .checkpoints/oc-dash-forge.checkpoint.json (rename it) and run /oc-df-intake; there is no reset command. Runs all phases with one gate: 1. Intake (adaptive — skim upstream context first) 2. Archetype pick (auto-proceed if clear) 3. Layout + tokens (show, proceed) 4. Gate: "Layout look right? (Y/n or describe changes)" 5. Prototype build, run /oc-df-audit silently 6. Report prototype artifact p

This is an excerpt. Refer to the complete source and its current requirements.