mode-design-discipline Skill
Authoring discipline for Amplifier modes. Covers anti-bloat patterns, naming hygiene, when advertised:false is right, how the body must narrate contributions, and how to test the four overlap scenarios (S1–S4) before committing a mode. Published by microsoft in amplifier-bundle-modes.
What is mode-design-discipline Skill?
Authoring discipline for Amplifier modes. Covers anti-bloat patterns, naming hygiene, when advertised:false is right, how the body must narrate contributions, and how to test the four overlap scenarios (S1–S4) before committing a mode. Published by microsoft in amplifier-bundle-modes. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Design and media
- Testing use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use mode-design-discipline Skill
- Use it for testing.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-bundle-modes
- Skill file: skills/mode-design-discipline/SKILL.md
What it does
Authoring discipline for Amplifier modes. Covers anti-bloat patterns, naming hygiene, when advertised:false is right, how the body must narrate contributions, and how to test the four overlap scenarios (S1–S4) before committing a mode.
Skill instructions
Mode Design Discipline This skill captures the judgment calls that separate well-crafted modes from ones that confuse the LLM, bloat context, or break silently on deactivation. --- 1. Most Modes Don't Need Contributions — And Most Behaviors Shouldn't Have Heavy context.include Either This rule has a sibling that lives one layer up in the bundle structure. The discipline described in this section is half the picture; the other half is: Most bundle behaviors should NOT have heavy entries in their context.include list. A behavior YAML's context.include lands in the always-on system prompt for every session that composes the behavior. The reflex to "just include the methodology file so it's always available" creates exactly the same bloat as the contributions reflex in modes — different mechanism, same pathology. The bar is symmetric: - Mode contributes: only add when the item is specialist-domain and only relevant during the mode's workflow. Otherwise put it in the bundle (always-on) or s
Explore related resources
Frequently asked questions
What is mode-design-discipline?
mode-design-discipline is a open-source AI agent skill with Copy skill directory. Authoring discipline for Amplifier modes. Covers anti-bloat patterns, naming hygiene, when advertised:false is right, how the body must narrate contributions, and how to test the four overlap.
Who is mode-design-discipline best for?
mode-design-discipline is best for reusing agent instructions, scripts, and references, testing workflows, design and media workflows.
How do I install mode-design-discipline?
Install or run mode-design-discipline using Copy skill directory. Check mode-design-discipline for the latest setup command.
Is mode-design-discipline actively maintained?
mode-design-discipline may need a closer maintenance check before production use.
Auto-fetched from GitHub.
