skills.rest
mblode
mblodeCOMMUNITY
Explore all skills by this author →
Website𝕏@mattblodeGitHub

define-architecture

Define architecture defaults for TypeScript projects during initiation or migrations.

75|6|Updated Jan 12, 2026
Search Tags:#typescript#architecture#frontend#backend#governance#module-contracts
One-click install
npx skills add https://github.com/mblode/agent-skills --skill define-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: define-architecture
Source: https://github.com/mblode/agent-skills/tree/main/skills/define-architecture
Command: npx skills add https://github.com/mblode/agent-skills --skill define-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architecture is often inconsistent across projects, leading to onboarding friction, misaligned module boundaries, and unscalable codebases. This skill provides a framework to define repo layout, workflows, and frontend/backend boundaries for TypeScript apps.

Core Features & Use Cases

  • Architecture setup workflow: define constraints, repo shape, and backend module contracts.
  • Adoption workflow: map current architecture, migrate incrementally, and enforce guardrails.
  • Validation loop and reference templates: default stack defaults and evaluation steps.

Quick Start

Define constraints, repo shape, and module contracts for a new TypeScript project using Architecture setup workflow.

Frequently Asked Questions about define-architecture

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

FAQPage Schema
How do I define consistent TypeScript architecture for a new project?▼

Define consistent TypeScript architecture by establishing repo layout, backend module contracts, and frontend boundaries using a structured setup workflow that enforces conventions and validation checks.

What is the best way to establish frontend and backend boundaries in a TypeScript app?▼

Establish frontend and backend boundaries by defining architecture defaults that separate frontend UI layers from backend module contracts, enforcing guardrails to prevent boundary violations during development.

How do I migrate an existing TypeScript codebase to a new architecture?▼

Migrate an existing TypeScript codebase using an adoption workflow that maps your current architecture, migrates incrementally, and enforces architecture conventions through validation checks.

Can I enforce architecture conventions and guardrails in a TypeScript monorepo?▼

Yes, you can enforce architecture conventions by defining module contracts and applying validation loops that check repo layout and frontend/backend boundaries against your established guardrails.

When do I need to define architecture defaults for a TypeScript application?▼

Define architecture defaults during project initiation or migrations when you need to establish repo layout, workflow steps, and backend contracts to prevent onboarding friction and unscalable codebases.

What's the difference between architecture setup and adoption workflows for TypeScript projects?▼

Architecture setup defines initial constraints, repo shape, and module contracts for new projects, while the adoption workflow maps existing architecture and migrates incrementally with enforced guardrails.

Related Skills

Explore More Software Engineering Skills→
nsalvacaonsalvacao

Architecture Coherence

Detect architecture drift by comparing declared architecture with actual code structure and dependencies.

Community
Advanced
saranskumarsaranskumar

frontend-scaffold-planner

Plan frontend routes, modules, state boundaries, and delivery sequencing.

Community
Intermediate
AcczdyAcczdy
2

implementing-api-schema-validation-security

Enforce OpenAPI v3.x request and response schema validation against JSON Schema contracts.

Community
Advanced
nuclianuclia
56

nx-monorepo

Guide Nx monorepo commands and module boundaries in Nuclia frontend.

Official
Intermediate