architecture

Design high-level technical architecture for new product features from specifications.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MarioWinter/merch-miner --skill architecture-mariowinter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/MarioWinter/merch-miner/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/MarioWinter/merch-miner --skill architecture-mariowinter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates feature specifications into high-level technical architecture plans, making complex technical decisions understandable for non-technical stakeholders like Product Managers.

Core Features & Use Cases

  • High-Level Design: Creates visual component trees and plain-language data models.
  • Tech Decision Justification: Explains the "why" behind technology choices in an accessible manner.
  • Use Case: A Product Manager provides a feature spec for a new "Kanban board" feature. This Skill generates an architecture document outlining the UI components (columns, cards), the data structure (task ID, title, status), and justifies using local storage for simplicity, all presented in a way the PM can easily review and approve.

Quick Start

Use the architecture skill to design the technical architecture for the feature spec located at /features/PROJ-123-new-dashboard.md.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I design technical architecture for new product features?

To design technical architecture for new features, translate feature specifications into high-level plans covering component structure, data modeling, and technology choices presented in a PM-friendly format.

Can I generate a data model and component tree from a feature specification?

Yes, you can generate visual component trees and plain-language data models directly from a feature specification to outline UI structures and data attributes for non-technical stakeholder review.

Does this architecture design approach work with Django applications?

Yes, this approach works with Django applications by requiring an understanding of existing project components to accurately design the high-level technical architecture for new features.

How do I justify technology choices for non-technical stakeholders?

You can justify technology choices by generating architecture documents that explain the reasoning behind selections in accessible language, ensuring Product Managers understand the technical decisions.

What is the best way to create PM-friendly technical design documents?

The best way to create PM-friendly technical design documents is to focus on high-level component structures and plain-language data models that make complex technical decisions understandable for review and approval.

Do I need existing project component knowledge for system design?

Yes, you need existing project component knowledge for system design because the architecture generation requires understanding current Django applications to structure new features correctly.