Getting Started by Task¶
Six common developer tasks, each with the handful of skills that matter and where to
start. This is the persistent form of the map that /vt-c-dev-start
prints interactively — run that skill with a task type (e.g. /vt-c-dev-start bug)
to get the same list in-session.
For a role-level overview, see Getting Started by Role.
Build a feature¶
End-to-end feature work, spec-driven with quality gates.
/vt-c-activate— load a spec (or generate one from a PRD) and start the cycle/vt-c-2-plan— research + architecture + task breakdown before you code/vt-c-3-build— implement against the plan with decision journaling/vt-c-4-review— mandatory multi-agent quality + security review/vt-c-test-driven-development— RED → GREEN → refactor for the code you write
Start with /vt-c-activate.
Fix a bug¶
From a report to a verified, learning-captured fix.
/vt-c-bug-report— file a tracked BUG-NNN intake so the fix is spec-backed/vt-c-triage-bugs— promote / defer / dedupe pending bug reports/vt-c-systematic-debugging— structured, hypothesis-driven debugging/vt-c-root-cause-tracing— trace an error backward through the call stack/vt-c-continuous-learning— feed the fix back so the mistake is not repeated
Start with /vt-c-bug-report (or /vt-c-systematic-debugging if you are already mid-investigation).
Build UI¶
Frontend work aligned to VisiTrans Corporate Design.
/vt-c-frontend-design— distinctive, production-grade frontend code/vt-c-visitrans-design-system— apply VisiTrans Corporate Design tokens/vt-c-pd-3-prototype— generate a deployable Angular + PrimeNG prototype/vt-c-c4-diagram— C4 context/container diagrams for the system view/vt-c-mermaid-diagrams-branded— branded Mermaid diagrams for flows and screens
Start with /vt-c-frontend-design.
Spin up a prototype¶
A throwaway or proof-of-concept, fast.
/vt-c-scaffold— universal folder structure + CLAUDE.md + vision/PRD stubs/vt-c-bootstrap— best-practice project structure, CI, docs folders/vt-c-kw-prototype— deployable Angular prototype with mock data/vt-c-frontend-design— quick, polished UI when the POC is frontend-facing/vt-c-pd-3-prototype— CD-compliant prototype when it will inform a handoff
Start with /vt-c-scaffold.
Build a skill, agent, or MCP server¶
Extend the toolkit itself.
/vt-c-skill-creator— guided creation of a new skill/vt-c-create-agent-skills— author and refine Claude Code skills (SKILL.md)/vt-c-mcp-builder— build a Model Context Protocol server/vt-c-agent-native-architecture— prompt-native agent design patterns/vt-c-skill-eval— run eval cases against a skill before you ship it
Start with /vt-c-skill-creator.
Debug something deep¶
Systematic debugging when the cause is not obvious.
/vt-c-systematic-debugging— structured root-cause workflow/vt-c-root-cause-tracing— backward trace from a deep failure/vt-c-defense-in-depth— validate at every layer so the bug becomes impossible/vt-c-verification-before-completion— prove it works before claiming done/vt-c-recursive-criticism— self-review pass that catches ~40% more issues
Start with /vt-c-systematic-debugging.
Kept in sync: these lists mirror
/vt-c-dev-start, whose skill metadata is read fromdocs/skill-orchestration-map.json(regenerated byscripts/generate-skill-map.sh) so it tracks the deployed skills.