architecture-primitives Skill
Catalog of reusable architectural primitives — boundaries, contracts, state machines, queues, caches, consistency models, and more. For each: what it is, when it's right, when it's WRONG. Use when selecting patterns for a design or evaluating whether a pattern fits. Published by microsoft in amplifier-bundle-systems-design.
What is architecture-primitives Skill?
Catalog of reusable architectural primitives — boundaries, contracts, state machines, queues, caches, consistency models, and more. For each: what it is, when it's right, when it's WRONG. Use when selecting patterns for a design or evaluating whether a pattern fits. Published by microsoft in amplifier-bundle-systems-design. 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
- Deployment
- Data analysis
- Design and media
- Deployment use cases
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use architecture-primitives Skill
- Use it for deployment.
- Use it for data analysis.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-bundle-systems-design
- Skill file: skills/architecture-primitives/SKILL.md
What it does
Catalog of reusable architectural primitives — boundaries, contracts, state machines, queues, caches, consistency models, and more. For each: what it is, when it's right, when it's WRONG. Use when selecting patterns for a design or evaluating whether a pattern fits.
Skill instructions
Architecture Primitives An architect who knows many patterns is less useful than one who knows when each pattern is wrong. For each primitive: what it is, when to use it, and when it will hurt you. --- Boundaries and Ownership What it is. Drawing lines between components so each has a clear owner, clear interface, and can evolve independently. When it's right. When different teams own different parts. When components have different scaling, deployment, or reliability requirements. When you need to limit blast radius. When it's wrong. When the "boundary" creates more cross-boundary coordination than it prevents. When data that changes together is split across boundaries. When the team is small enough that communication overhead exceeds boundary value. Contracts and Interfaces What it is. Explicit agreements between components about what they provide and expect — API schemas, message formats, SLAs, error codes. When it's right. At every boundary. Between any components that evolve indepe
Explore related resources
Frequently asked questions
What is architecture-primitives?
architecture-primitives is a open-source AI agent skill with Copy skill directory. Catalog of reusable architectural primitives — boundaries, contracts, state machines, queues, caches, consistency models, and more. For each: what it is, when it's right, when it's WRONG.
Who is architecture-primitives best for?
architecture-primitives is best for reusing agent instructions, scripts, and references, deployment workflows, data analysis workflows, design and media workflows.
How do I install architecture-primitives?
Install or run architecture-primitives using Copy skill directory. Check architecture-primitives for the latest setup command.
Is architecture-primitives actively maintained?
architecture-primitives may need a closer maintenance check before production use.
Auto-fetched from GitHub.
