Awesome-omni-skill triatu-architecture

Name: triatu-architecture
Author: diegosouzapw

Clean Architecture guidance for Triatu: layering, dependencies, and where code belongs. Use when adding new modules, moving code across layers, or updating architecture decisions and docs.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/devops/triatu-architecture" ~/.claude/skills/diegosouzapw-awesome-omni-skill-triatu-architecture && rm -rf "$T"

manifest: skills/devops/triatu-architecture/SKILL.md

source content

Triatu Architecture

Quick start

Follow dependency direction: UI -> Application -> Domain <- Infrastructure.
Keep use cases framework-agnostic (no Next.js or Supabase types in core use cases).
Validate inputs with Zod before touching infrastructure.
Update architecture docs on any structural change.

Workflow

Read
```
arquitectura_triatu.md
```
for the current model.
Identify the layer for new logic (Domain, Application, Infrastructure, UI).
Add interfaces/ports in Domain when infrastructure is involved.
Implement adapters in Infrastructure and wire them in Application.
Keep UI thin: call Application use cases and map view models.
Add tests first (TDD), then code.

Update docs:

guia.md

arquitectura_triatu.md

docs/PROJECT_AUDIT.md

Guardrails

No direct infrastructure access from Domain.
Avoid global state unless justified (Zustand only for ephemeral UI).
Avoid logs with PII; use
```
lib/logger
```
and
```
debug
```
in dev only.

References

```
arquitectura_triatu.md
```
```
docs/CORE.md
```
```
guia.md
```
```
docs/DEVELOPMENT.md
```
```
docs/PROJECT_AUDIT.md
```