architect

Generate architecture blueprints with module boundaries, layer layouts, and integration points.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/aimskr/aims-claude-toolkit --skill architect-aimskr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/aimskr/aims-claude-toolkit/tree/main/skills/architect
Command: npx skills add https://github.com/aimskr/aims-claude-toolkit --skill architect-aimskr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineering teams struggle to align on system structure; this Skill translates abstract architecture ideas into concrete, shareable blueprints that define module boundaries, layers, and integration points, enabling faster planning and safer refactors.

Core Features & Use Cases

  • Actionable architecture blueprints with exact file paths for implementations and dependencies
  • Layered architecture guidance following Clean Architecture and DDD
  • Architecture decisions and mapping: patterns found, trade-offs, and implementation maps

Quick Start

Provide a complete architecture blueprint for a feature, including module boundaries, layer layout, dependencies, and a concrete implementation map with file paths.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I create an actionable architecture blueprint with specific file paths?

An architecture blueprint defines module boundaries, layer layouts, and integration points with exact file paths. It translates abstract design ideas into concrete implementation maps for planning and safer refactoring.

What is the best way to define module boundaries for a new software feature?

Defining module boundaries uses Clean Architecture and Domain-Driven Design principles to separate concerns. This approach yields an actionable map detailing dependencies and layers for the feature implementation.

How do I apply DDD and Clean Architecture when restructuring a system?

Applying DDD and Clean Architecture during system restructuring maps existing patterns and trade-offs to new layer layouts. It outputs architecture decisions and implementation maps to guide the refactor safely.

Can I generate Architecture Decision Records for integration points and trade-offs?

Yes, generating Architecture Decision Records captures patterns found, trade-offs, and integration points. These records document the rationale behind module boundaries and layer layouts in the blueprint.