apply-attribute-driven-design

Execute the Attribute-Driven Design 3.0 methodology for architectural designs.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill apply-attribute-driven-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply-attribute-driven-design
Source: https://github.com/EnigmaWU/MyCodeAgentSkills/tree/main/apply-attribute-driven-design
Command: npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill apply-attribute-driven-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses the challenge of creating comprehensive and robust architectural designs by guiding the agent through the Attribute-Driven Design (ADD) 3.0 methodology.

Core Features & Use Cases

  • Iterative Process: Guides through an iterative 7-step process for architectural decision-making.
  • Quality Attribute Focus: Ensures non-functional requirements are considered alongside functional ones.
  • Documentation: Generates documentation for technical design documents and ADRs.
  • Use Case: When designing a new payment gateway, this skill helps in drafting the architecture considering all quality attributes and constraints.

Quick Start

Apply the apply-attribute-driven-design skill to create a system design for the new payment gateway.

Frequently Asked Questions about apply-attribute-driven-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is Attribute-Driven Design 3.0 for system architecture?

Attribute-Driven Design (ADD) 3.0 is an iterative methodology for creating architectural designs that systematically maps quality attributes and constraints to design patterns, ensuring robust system architecture.

How do I design a system architecture that meets quality attributes?

To design a system architecture that meets quality attributes, apply the ADD 3.0 methodology through its iterative 7-step process, systematically mapping non-functional requirements and functional drivers to appropriate design patterns.

How do I create technical design documents and ADRs for a new payment gateway?

Create technical design documents and ADRs for a new payment gateway by applying the ADD 3.0 methodology, which guides iterative architectural decision-making while considering all quality attributes and constraints.

Can I use ADD 3.0 for iterative architecture design?

Yes, you can use ADD 3.0 for iterative architecture design as it provides a systematic 7-step process that guides architectural decision-making and maps design drivers to patterns across multiple iterations.

What's the best way to map non-functional requirements to design patterns?

The best way to map non-functional requirements to design patterns is using the ADD 3.0 methodology, which ensures quality attributes are considered alongside functional ones through a systematic mapping process during architectural design.