Shrutam CCA-F Crash › Domain 3 › d3-l06-slash-commands Hinglish English →

Custom Slash Commands — Your Team's Vocabulary

Domain 3 · 20% ~12 min Hinglish narration

Audio-only (commute / mobile data)

Same Saavi narration, smaller file. Opus 48k preferred — auto-selected by your browser.

Scenario anchor

Aap Aaranya IT BFSI ke ek 200-developer program mein lead architect hain — har team apne alag tarike se Claude ko prompt kar rahi hai, aur code reviews inconsistent hain, compliance checks miss ho rahe hain. Ek senior developer ne /review likha, dusre ne "please do a security review", teesre ne kuch aur — same intent, wildly different outputs. Custom slash commands exactly iss problem ko solve karte hain: aap ek canonical "vocabulary" define karte hain jo har invocation pe consistent context, constraints, aur instructions inject karta hai — bilkul usi tarah jaise ek API gateway ek single route contract enforce karta hai across all upstream consumers.

Key Takeaways

Custom slash commands live in .claude/commands/ as Markdown files — the filename becomes the command token, and the file body is the full prompt template injected at invocation, giving teams a versioned, repo-committed prompt contract.
Use $ARGUMENTS as a typed placeholder inside the command file to pass dynamic values at call time, enabling parameterized workflows (e.g., /security-review src/payments) without rebuilding prompt logic per invocation.
Scope discipline is non-negotiable in enterprise settings: project-level commands (.claude/commands/) carry the repo's compliance context; reserve global commands only for personal productivity shortcuts that carry zero production risk.
Memory anchor — treat slash commands as your API gateway route contract: one canonical definition, consistent enforcement, all consumers routed through the same policy layer.

← Previous lesson Same lesson in English Next lesson → Back to overview