skills.rest
nguyenpv1980-wq
nguyenpv1980-wqCOMMUNITY
Explore all skills by this author →
GitHub

architecture-designer

Design software architecture from inspected codebase components and dependencies.

2|Updated Jul 6, 2026
Search Tags:#architecture#system design#adr#dependencies#migration plan#data ownership
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill architecture-designer-nguyenpv1980-wq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/architecture-designer
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill architecture-designer-nguyenpv1980-wq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design or redesign software architecture from the actual current codebase, so structural decisions are grounded in reality instead of documentation or guesswork. It is useful when you need to place a new feature, split a subsystem, define boundaries, or evaluate dependency direction with confidence.

Core Features & Use Cases

  • Current-state inspection: Maps real components, dependencies, deploy units, and data ownership before proposing changes.
  • Target architecture design: Produces a component map, boundary contracts, coupling risks, and an incremental migration plan.
  • Decision support: Compares viable options, drafts an ADR for the key architectural choice, and highlights tradeoffs and reversal conditions.
  • Use Case: A team wants to know whether a notification system should live inside an existing API service or become its own service, and how to move there safely.

Quick Start

Ask for an architecture design review of the current system and the change you want to make, and include any constraints such as scale, latency, team ownership, or compliance.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I design software architecture based on actual codebase structure instead of assumptions?▼

Architecture design grounded in real codebase inspection maps current components, dependencies, and data ownership before proposing structural changes, ensuring decisions reflect actual repository facts rather than outdated documentation.

How do I define service boundaries and integration placement for a new feature?▼

Defining service boundaries requires analyzing current dependencies and data ownership from the codebase, then producing a target component map with boundary contracts and coupling risks to guide integration placement decisions safely.

What's the best way to plan a subsystem redesign without breaking existing dependencies?▼

Subsystem redesign planning involves inspecting real component dependencies and deploy units, then generating an incremental migration plan with tradeoff analysis and reversal conditions to avoid breaking existing coupling.

How do I draft an Architecture Decision Record for a system design tradeoff?▼

Drafting an ADR for system design involves comparing viable architectural options, highlighting tradeoffs and reversal conditions, and documenting the key structural choice grounded in inspected repository facts and dependency directions.

Can I evaluate whether a notification system should be a standalone service or embedded in an existing API?▼

Evaluating service placement for a notification system involves inspecting current codebase dependencies, mapping data ownership, and producing a target component map with coupling risks and an incremental migration path to guide the decision.

What are the limitations of redesigning architecture without inspecting the current codebase?▼

Redesigning architecture without current-state codebase inspection risks grounding structural decisions in guesswork, missing hidden dependencies, and proposing migration paths that fail against actual component coupling and data ownership constraints.

Related Skills

Explore More Software Engineering Skills→
superdesigndevsuperdesigndev
43

archlet

Generate interactive architecture maps and PR diff overlays from import graphs.

Official
Advanced
petekppetekp
5

seam-ripper

Analyze architectural seams and map dependencies to surface coupling problems.

Community
Advanced
CANTAGESTUDIOCANTAGESTUDIO
3

refactor-arch-hotspots

Detect architectural hotspots by analyzing churn, coupling, and layer violations.

Community
Advanced
shalevaminshalevamin

legacy-modernizer

Design incremental migration strategies for legacy codebases with dependency maps.

Community
Advanced