skills.rest
duongtdn
duongtdnCOMMUNITY
Explore all skills by this author →
GitHub

architect

Analyze repository code paths and git history to resolve architectural questions and record ADRs.

Updated Jul 6, 2026
Search Tags:#design#architecture#refactoring#codebase#adr#engineering
One-click install
npx skills add https://github.com/duongtdn/devloop --skill architect-duongtdn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/duongtdn/devloop/tree/main/skills/architect
Command: npx skills add https://github.com/duongtdn/devloop --skill architect-duongtdn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides expert-level guidance on complex software design trade-offs, module boundaries, and architectural decisions, ensuring your codebase remains maintainable and well-structured.

Core Features & Use Cases

  • Design Trade-off Analysis: Evaluates architectural decisions like refactoring, module splitting, or dependency management using a rigorous evidence-based method.
  • Decision Recording: Formalizes settled architectural decisions into ADRs (Architecture Decision Records) that serve as binding constraints for future development.
  • Use Case: When deciding whether to extract a shared service into a separate module or keep it coupled for simplicity, this Skill analyzes git history and call patterns to provide a concrete, justified recommendation.

Quick Start

Invoke the architect skill to evaluate the design trade-offs for the current module structure in src/core.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I analyze design trade-offs for refactoring a shared service into a separate module?▼

To analyze refactoring trade-offs, evaluate architectural decisions by examining repository code paths, git history, and call patterns to justify whether to extract or couple modules for maintainability.

What is an Architecture Decision Record and when do I need one for my codebase?▼

An Architecture Decision Record (ADR) formalizes settled design trade-offs into binding constraints for future development. You need ADR documentation when resolving structural questions to ensure consistent, evidence-based decision-making.

How do I manage module boundaries and dependency management in a growing codebase?▼

Manage module boundaries by using a structured, conversational interface to evaluate structural questions, analyzing git history and issue references to provide concrete recommendations for decoupling dependencies.

Does this architectural guidance method work with existing git history and issue references?▼

Yes, the architectural guidance method operates by analyzing existing repository code paths, git history, and issue references to resolve structural questions and enforce evidence-based design decisions.

What's the best way to document binding architectural decisions for future development?▼

The best way to document binding architectural decisions is to formalize them into Architecture Decision Records (ADRs) through a structured interface, serving as binding constraints for future engineering work.

When should I not extract a shared service into its own module?▼

You should not extract a shared service when design trade-off analysis of git history and call patterns reveals that keeping it coupled provides better simplicity and maintainability for the codebase.

Related Skills

Explore More Software Engineering Skills→
zhu327zhu327
2

code-review-expert

Review Git diffs for structural regressions, security risks, and maintainability issues.

Community
Advanced
CygnusfearCygnusfear
5

the-archivist

Document engineering decisions as ADRs with rationale and decision logs.

Community
Advanced
gekko68gekko68

bash-executor

Execute Bash commands with validation, dry-run previews, and timeout protection.

Community
Advanced
simonheimlichersimonheimlicher
1

reviewing-python

Enforce adversarial Python code review that rejects mocking and generates a formal report.

Community
Advanced