Shrutam CCA-F Crash › Domain 3 › d3-l10-subagent-frontmatter Hinglish English →

Subagent Definitions — Custom Roles via Frontmatter

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

Aaranya IT ke ek large BFSI engagement mein aap ne dekha hoga — ek monolithic codebase hai, 40+ microservices, aur har service ka code-review agent alag context expect karta hai. Security auditor ko compliance rules chahiye, refactoring agent ko architecture constraints chahiye, aur test-generator ko coverage targets chahiye. Ek hi system prompt se yeh sab handle karna — woh approach production mein fail hoti hai. Is lesson mein aap dekhenge ki CLAUDE.md frontmatter blocks ke through custom subagent roles kaise define karte hain — har agent ko precisely scoped context, tools, aur behavioral constraints ke saath — bilkul waise jaise aap ek service mesh mein per-service traffic policy inject karte hain.

Key Takeaways

Subagent frontmatter in CLAUDE.md is the canonical mechanism to inject role identity, tool permissions, and behavioral constraints at agent-spawn time — not at runtime via prompts or tool arguments.
Each subagent block scopes context precisely: think per-service sidecar policy in a service mesh, not a global ingress rule — overly broad definitions cause cross-role contamination in multi-agent pipelines.
Frontmatter fields (role, tools, context_files, constraints) form a schema-validated config contract; missing or malformed fields silently degrade agent behavior in ways that surface only under load or edge-case inputs.
Memory anchor: config-cascade — subagent frontmatter is your per-node config layer; global system prompts are your cluster-level defaults; never flatten both into one layer.

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