Receber por email
← Voltar para o catálogo

architecture-patterns

Document system design decisions with mapped user flows, coupling analysis, failure modes, and explicit non-goals, proving the architecture can survive under unexpected conditions. Use when designing systems, evaluating structural changes, or reviewing architecture decisions. Proactively suggest when coupling analysis reveals circular dependencies, god objects, or hidden shared state.

5estrelas
Atualizado há 5 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add synaptiai/synapti-marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/architecture-patterns-synaptiai/svg)](https://www.skillteca.com.br/skills/architecture-patterns-synaptiai)
#ai

Skills relacionadas

Ver todas de Pesquisa e Web →

Alerta por categoria

Receba novas skills de Pesquisa e Web toda segunda

1 email curto, só com as skills novas de Pesquisa e Web. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Architecture Patterns

Domain skill for system design, structural evaluation, and architecture decisions.

Iron Law

DESIGN ARCHITECTURE FROM FUNCTIONALITY, NOT TO FUNCTIONALITY. If you can't trace a component to a user flow, delete it.

Architecture serves user flows. Not the other way around.

Prerequisite: Map Flows First

Before designing ANYTHING, enumerate flows. Track each design activity as a task:

TaskCreate("Map user/admin/system flows", "Enumerate all flows before des

[Description truncada. Veja o README completo no GitHub.]
Compartilhar X LinkedIn