victorzhuk/go-ent/architecture-design

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Practical architecture design workflow with templates for component diagrams, layer documentation, data flow, and schema design.

Install

npx vskill@latest install victorzhuk/go-ent/architecture-design

SKILL.md

Role

System architect focused on practical design outputs. Creates architecture documents with diagrams, layer decisions, and data flow documentation.

This skill covers the design workflow (how to produce architecture artifacts). For architecture principles (Clean Architecture, DDD, SOLID), see arch-core.

Design Template

markdown
# Architecture: {feature}
## Overview
{High-level description}
## Components

graph TB A[Transport] --> B[UseCase] B --> C[Domain] B --> D[Repository]

## Layers
- **Domain**: {entities, contracts}
- **UseCase**: {business logic}
- **Repository**: {data access}
- **Transport**: {HTTP/gRPC handlers}
## Data Flow
1. Request -> Transport (validation)
2. Transport -> UseCase (DTO)
3. UseCase -> Repository (entity)
4. Repository -> DB (model)
## Database Schema
{Tables, indexes, constraints}
## API Contract
{Endpoints or RPC methods}
## Decisions
| Decision | Rationale |
|----------|-----------|
| {choice} | {why} |

Design Outputs

Create in project documentation or openspec/changes/{id}/:

  • Architecture decisions document
  • Component diagram (Mermaid)
  • Data flow documentation

Design Principles

  • Domain has ZERO external dependencies
  • Interfaces defined at consumer side
  • One responsibility per component
  • Prefer composition over inheritance
  • Design for testability
  • Consider failure modes
  • Document trade-offs

Design Process

1. Understand Scope
  • What problem are we solving?
  • What are the constraints?
  • What existing patterns should we follow?
2. Component Design
  • Identify bounded contexts
  • Define layer responsibilities
  • Plan API contracts (OpenAPI, Proto)
  • Design database schema
3. Evaluate Trade-offs

For each technology choice:

Option A:
+ Pros: {advantages}
- Cons: {limitations}
Option B:
+ Pros: {advantages}
- Cons: {limitations}
Recommendation: {choice with rationale}
4. Document Decisions

Use ADR (Architectural Decision Record) format:

  • Context: What's the situation?
  • Decision: What did we choose?
  • Consequences: What are the trade-offs?

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/victorzhuk/go-ent/architecture-design/badge)](https://verified-skill.com/skills/victorzhuk/go-ent/architecture-design)

Something wrong with this skill or its page? Tell us.