define-architecture

Define TypeScript full-stack architecture defaults for folder layouts and module contracts.

Updated Sep 10, 2025
One-click install
npx skills add https://github.com/tillysoso/mv1 --skill define-architecture-tillysoso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define-architecture
Source: https://github.com/tillysoso/mv1/tree/main/.claude/skills/define-architecture
Command: npx skills add https://github.com/tillysoso/mv1 --skill define-architecture-tillysoso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates durable, easy-to-change architecture defaults for TypeScript full-stack apps, including folder structures, module contracts, middleware pipelines, and frontend/backend boundaries.

Core Features & Use Cases

  • Architecture setup workflow to define repo shape (apps/packages), module contracts (handler/service/dao/mapper), and middleware policies for new projects.
  • Adoption workflow guidance to migrate existing codebases with guardrails, enabling incremental changes without big-bang rewrites.
  • Clear frontend and backend boundaries, including guidance on server components, client components, and cross-cutting concerns, plus team convention enforcement.

Quick Start

Run the architecture setup workflow on a new or existing project to generate a coherent architecture brief, contracts, and templates to start coding.

Frequently Asked Questions about define-architecture

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

FAQPage Schema
How do I define a scalable TypeScript monorepo architecture for a full-stack project?

Backend module contracts structure code into handler, service, dao, mapper, constants, and types layers to enforce separation of concerns and clear data flow boundaries. This structure ensures durable, easy-to-change architecture defaults across your full-stack application.

How do I migrate an existing TypeScript codebase to a new architecture without a big-bang rewrite?

The architecture setup applies to starting new projects, monorepos, and re-architecture efforts to define folder layouts, module contracts, and middleware pipelines. It specifies backend module contracts, request context policies, frontend boundaries, and testing guardrails for coherent governance.

How do I structure frontend and backend boundaries in a TypeScript full-stack application?

Structure frontend and backend boundaries by defining clear conventions for server components, client components, and cross-cutting concerns. The architecture specifies frontend boundaries and backend module contracts to enforce team conventions across the full-stack application.

What is the best way to standardize request context and middleware pipelines in a TypeScript backend?

Testing and release guardrails are specified as part of the architecture defaults to ensure module contracts and frontend boundaries remain intact during incremental changes. These guardrails enable incremental adoption without breaking existing functionality during re-architecture efforts.