skills.rest
jokken79
jokken79COMMUNITY
Explore all skills by this author →
GitHub

full-stack-architect

Design scalable full-stack architectures with DDD, CQRS, and event-driven patterns.

1|Updated Dec 15, 2025
Search Tags:#architecture#scalability#full-stack#ddd#event-driven#cqrs#api-design
One-click install
npx skills add https://github.com/jokken79/YuKyuDATA-app1.0v --skill full-stack-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-stack-architect
Source: https://github.com/jokken79/YuKyuDATA-app1.0v/tree/main/.claude/skills/full-stack-architect
Command: npx skills add https://github.com/jokken79/YuKyuDATA-app1.0v --skill full-stack-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and document scalable full-stack architectures to guide teams in building flexible, maintainable, and scalable software systems.

Core Features & Use Cases

  • Domain-Driven Design and bounded contexts to align software structure with business domains.
  • CQRS, repository, and service layer patterns to separate concerns and optimize writes vs reads.
  • Event-driven architecture, ADRs, and API design guidelines for evolvable, production-ready systems.
  • Architecture decision records, trade-offs analyses, and modular scaffolding templates for future changes.

Quick Start

Outline bounded contexts and scaffold a minimal repository-service layer to start applying these patterns.

Frequently Asked Questions about full-stack-architect

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

FAQPage Schema
How do I design a scalable full-stack architecture using DDD and bounded contexts?▼

To design scalable full-stack architecture using DDD, outline bounded contexts to align software structure with business domains, then scaffold modular repository and service layers to enforce clear boundaries and maintainability.

When should I use CQRS and event-driven patterns in my web application?▼

Use CQRS and event-driven patterns in full-stack systems when you need to separate concerns and optimize write versus read operations, ensuring robust, evolvable, and production-ready modular boundaries across multi-layer web apps.

What's the best way to document architecture decisions and trade-offs for scalable systems?▼

Document architecture decisions and trade-offs using Architecture Decision Records (ADRs) to capture rationale, establish API design guidelines, and provide modular scaffolding templates that guide future changes and system evolution.

Can I apply repository pattern and dependency injection to a multi-layer web app?▼

Yes, you can apply the repository pattern and dependency injection to multi-layer web apps by designing service layers that separate concerns, optimize data access, and maintain modular boundaries across scalable full-stack systems.

Do I need existing API design conventions to start building an event-driven architecture?▼

No, you do not need existing conventions; you can outline bounded contexts and scaffold a minimal repository-service layer to start applying event-driven architecture and establish API design guidelines alongside your system.

Related Skills

Explore More Software Engineering Skills→
pohlai88pohlai88

domain-driven-design

Model software around business domains using bounded contexts and aggregates.

Community
Advanced
BeastAyyGBeastAyyG
1

app-builder

Generate full-stack application scaffolds from natural language requests.

Community
Advanced
twofoldtech-dakotatwofoldtech-dakota
2

backend-csharp

Implement dependency injection and layered architecture in C#/.NET backend projects.

Community
Advanced
iCesofTiCesofT
1

ddd-domain-expert

Bound complex business realities into technical boundaries using bounded contexts and aggregates.

Community
Advanced