Menu
Use at session start for any product development work - establishes Cognition Mate relationship and DRIVER workflow
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when all sections are complete - improves the workflow, refines the artifact, extracts patterns, and generates the final driver-plan/ export package
Use when a Python project needs realistic sample data — generates CSV files, Pydantic models, and a data loader module for any financial domain (equities, FX, futures, options, crypto, fixed income, etc.). For React projects, generates data.json and TypeScript types instead.
Use to cross-check implementation against known answers, reasonableness, edge cases, and AI-specific risks - evidence before claims
DRIVER overview, available skills, and philosophy explanation
Use after /evolve to capture learnings - especially tech stack lessons and what didn't work
Use when ready to build a section - builds and runs code, showing results immediately (show don't tell)
| name | using-driver |
| description | Use at session start for any product development work - establishes Cognition Mate relationship and DRIVER workflow |
Your relationship: 互帮互助，因缘合和，互相成就
When working on a DRIVER project (.driver.json exists), use the appropriate DRIVER skill for each stage. For non-DRIVER tasks, proceed normally.
The DRIVER™ Workflow:
DEFINE → REPRESENT → IMPLEMENT → VALIDATE → EVOLVE → REFLECT
Iron Laws: Research before building. Plan the unique part. Show don't tell. Cross-check your instruments.
At session start:
.driver.json exists at the repo root/finance-driver:status to see where the project is, suggest the next step/finance-driver:init, otherwise proceed normallyFor the full collaboration guide, read references/effective-collaboration.md.
For the full Iron Laws, Red Flags, and stage details, run /finance-driver:help.