architect

Design technical architecture for software features and production systems.

2|Updated Jun 13, 2025
One-click install
npx skills add https://github.com/mattszein/pro-rails --skill architect-mattszein
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/mattszein/pro-rails/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/mattszein/pro-rails --skill architect-mattszein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn product ideas into actionable technical architecture plans, reducing uncertainty before implementation begins.

Core Features & Use Cases

  • Layer Assignment: Identifies which parts of a feature belong in presentation, application, domain, or infrastructure layers.
  • Pattern Selection: Chooses the right approach for workflows, authorization, real-time updates, background jobs, and data modeling.
  • File Structure Planning: Maps new capabilities to the directories, models, controllers, interactors, policies, jobs, and tests they require.
  • Use Case: A product team can use this Skill to decide how to build a new admin workflow, including where logic should live and what tradeoffs to accept.

Quick Start

Use the architect skill to create a technical plan for a new feature, including layer responsibilities, file structure, and architectural tradeoffs.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I plan technical architecture for a new software feature?▼

Technical architecture planning assigns feature components to presentation, application, domain, and infrastructure layers. It produces implementation-ready guidance with explicit tradeoff analysis, covering file structure and pattern selection without writing code.

What is the best way to structure files and select patterns for a Rails feature?▼

File structure planning maps new capabilities to directories, models, controllers, interactors, policies, jobs, and tests. Pattern selection chooses the right approach for workflows, authorization, real-time updates, and background processing within the Rails architecture.

How do I decide where feature logic should live across application layers?▼

Layer assignment identifies which parts of a feature belong in presentation, application, domain, or infrastructure layers. This separation ensures logic is correctly distributed across controllers, interactors, and models before implementation.

Can I use this approach to design authorization and background job workflows?▼

Yes, pattern selection explicitly covers authorization decisions, background jobs, real-time updates, and data modeling. The architectural plan defines where these workflows live and what tradeoffs to accept for production systems.

Does the architectural plan include actual code implementation?▼

No, the architectural plan provides implementation-ready guidance without writing code. It focuses on layer responsibilities, file structure mapping, pattern selection, and explicit tradeoff analysis to reduce uncertainty before development.

When do I need to create a technical design plan for a production system?▼

You need a technical design plan when adding admin workflows, real-time behavior, background processing, or new data models to production systems. It reduces uncertainty by defining architecture, layer separation, and tradeoffs before implementation.