File contents name: architecture
description: System design patterns and architecture decisions
Architecture Patterns
System design for Vue3 + ASP.NET applications.
Layered Architecture
┌─────────────────────────────────────┐
│ Presentation (Vue3) │
├─────────────────────────────────────┤
│ API (Controllers) │
├─────────────────────────────────────┤
│ Business Logic (Services) │
├─────────────────────────────────────┤
│ Data Access (Repositories) │
├─────────────────────────────────────┤
│ Database (SQL Server) │
└─────────────────────────────────────┘
Frontend Architecture
src/
├── components/ # Reusable UI components
├── composables/ # Shared logic (useXxx)
├── views/ # Page components
├── stores/ # Pinia stores
├── api/ # API client
├── types/ # TypeScript types
└── router/ # Vue Router
Backend Architecture
src/
├── Controllers/ # HTTP endpoints
├── Services/ # Business logic
├── Repositories/ # Data access
├── Models/ # Domain models
├── DTOs/ # Data transfer objects
└── Infrastructure/ # Cross-cutting concerns
Communication Patterns
Pattern
Use Case
REST API
Standard CRUD operations
SignalR
Real-time updates
Background Jobs
Async processing
Message Queue
Event-driven systems
Decision Matrix
Decision
Option A
Option B
State management
Pinia
Composables
API calls
Axios
Fetch
Forms
VeeValidate
Native
Testing
Vitest
Jest
Scaling Considerations
Layer
Strategy
Frontend
CDN, code splitting
API
Horizontal scaling, load balancer
Database
Read replicas, caching
Background
Worker processes
DO / DON'T
✅ Do
❌ Don't
Clear layer separation
Mixed concerns
Dependency injection
Hard dependencies
Interface-based design
Concrete dependencies
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1 --- 2 name: tridentsof-antigravity-dev-kit-architecture 3 description: "---" 4 --- 5 --- 6 name: architecture 7 description: System design patterns and architecture decisions 8 --- 9 10 # Architecture Patterns 11 12 > System design for Vue3 + ASP.NET applications. 13 14 --- 15 16 ## Layered Architecture 17 18 ``` 19 ┌─────────────────────────────────────┐ 20 │ Presentation (Vue3) │ 21 ├─────────────────────────────────────┤ 22 │ API (Controllers) │ 23 ├─────────────────────────────────────┤ 24 │ Business Logic (Services) │ 25 ├─────────────────────────────────────┤ 26 │ Data Access (Repositories) │ 27 ├─────────────────────────────────────┤ 28 │ Database (SQL Server) │ 29 └─────────────────────────────────────┘ 30 ``` 31 32 --- 33 34 ## Frontend Architecture 35 36 ``` 37 src/ 38 ├── components/ # Reusable UI components 39 ├── composables/ # Shared logic (useXxx) 40 ├── views/ # Page components 41 ├── stores/ # Pinia stores 42 ├── api/ # API client 43 ├── types/ # TypeScript types 44 └── router/ # Vue Router 45 ``` 46 47 --- 48 49 ## Backend Architecture 50 51 ``` 52 src/ 53 ├── Controllers/ # HTTP endpoints 54 ├── Services/ # Business logic 55 ├── Repositories/ # Data access 56 ├── Models/ # Domain models 57 ├── DTOs/ # Data transfer objects 58 └── Infrastructure/ # Cross-cutting concerns 59 ``` 60 61 --- 62 63 ## Communication Patterns 64 65 | Pattern | Use Case | 66 |---------|----------| 67 | REST API | Standard CRUD operations | 68 | SignalR | Real-time updates | 69 | Background Jobs | Async processing | 70 | Message Queue | Event-driven systems | 71 72 --- 73 74 ## Decision Matrix 75 76 | Decision | Option A | Option B | 77 |----------|----------|----------| 78 | State management | Pinia | Composables | 79 | API calls | Axios | Fetch | 80 | Forms | VeeValidate | Native | 81 | Testing | Vitest | Jest | 82 83 --- 84 85 ## Scaling Considerations 86 87 | Layer | Strategy | 88 |-------|----------| 89 | Frontend | CDN, code splitting | 90 | API | Horizontal scaling, load balancer | 91 | Database | Read replicas, caching | 92 | Background | Worker processes | 93 94 --- 95 96 ## DO / DON'T 97 98 | ✅ Do | ❌ Don't | 99 |-------|---------| 100 | Clear layer separation | Mixed concerns | 101 | Dependency injection | Hard dependencies | 102 | Interface-based design | Concrete dependencies | 103 104 --- 105 > Converted and distributed by [TomeVault](https://tomevault.io/claim/tridentsof) — claim your Tome and manage your conversions. 106 <!-- tomevault:4.0:skill_md:2026-04-14 -->
tomevault-io/skills-registry/tree/main/tridentsof--antigravity-dev-kit--architecture commit 5ab7f292f4
Frequently asked questions How do I install the Tridentsof Antigravity Dev Kit Architecture skill? Run npx get-skill add tomevault-io/tridentsof-antigravity-dev-kit-architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Tridentsof Antigravity Dev Kit Architecture skill do? --- It is listed under Coding & Dev Tools on SkillMD.
Is Tridentsof Antigravity Dev Kit Architecture safe to use? This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Tridentsof Antigravity Dev Kit Architecture? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Tridentsof Antigravity Dev Kit Architecture free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Tridentsof Antigravity Dev Kit Architecture? tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
