sfermanelli-architect

Design TypeScript system architecture decisions and ADRs for modular structure.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sebafermanelli/sfermanelli-skills --skill sfermanelli-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sfermanelli-architect
Source: https://github.com/sebafermanelli/sfermanelli-skills/tree/main/sfermanelli-architect
Command: npx skills add https://github.com/sebafermanelli/sfermanelli-skills --skill sfermanelli-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design system architecture decisions and ADRs for TypeScript projects to guide future changes, ensuring modularity and long-term maintainability.

Core Features & Use Cases

  • Guided architecture design for new projects and refactors.
  • Documentation of trade-offs via ADRs, patterns, and structure decisions.
  • Reusable blueprint for folder layouts, layer boundaries, and component boundaries.
  • Use case: when starting a new TS service, this Skill provides a structured architecture with ADRs and a modular layout.

Quick Start

Describe your system goals and I'll generate a modular TypeScript architecture with an ADR and a recommended folder layout.

Frequently Asked Questions about sfermanelli-architect

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

FAQPage Schema
How do I plan a scalable TypeScript architecture for a new project?

Generate a modular TypeScript architecture by describing your system goals to produce a structured folder layout, layer boundaries, and ADRs. This applies SOLID, DDD, and layered architecture patterns to ensure modularity and guide future codebase changes.

What is an ADR and when do I need it for TypeScript architecture?

An ADR documents architecture trade-offs and structure decisions for TypeScript projects. You need ADRs when starting a new service, refactoring a codebase, or evaluating layered patterns to ensure requirements for modular structure and scalable patterns are met.

How do I structure a TypeScript codebase using DDD and layered architecture?

Structure a TypeScript codebase using DDD and layered architecture by generating a reusable blueprint for folder layouts and component boundaries. This enforces clear layer boundaries and modular structure to satisfy requirements for scalable patterns.

Can I use this to reorganize an existing TypeScript codebase?

Yes, you can reorganize an existing TypeScript codebase by evaluating architecture patterns across layers. It provides guided architecture design for refactors, generating ADRs and a recommended modular layout to restructure code while documenting trade-offs.

What is the best way to document architecture trade-offs in TypeScript?

Document architecture trade-offs in TypeScript by generating ADRs alongside your structural decisions. This records patterns, component boundaries, and layer decisions to create a reusable blueprint that guides future changes and maintains long-term maintainability.

Does this architecture approach work for evaluating SOLID principles?

Yes, this architecture approach works for evaluating SOLID principles across your TypeScript project. It provides layered architecture guidance and evaluates component boundaries to ensure your modular structure satisfies scalable pattern requirements.