frontend-ddd

Organize frontend monorepos with domain-driven design boundaries and dependency rules.

4|Updated Jun 12, 2024
One-click install
npx skills add https://github.com/Nathan3303/nao-todo --skill frontend-ddd-nathan3303
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-ddd
Source: https://github.com/Nathan3303/nao-todo/tree/main/.opencode/skills/frontend-ddd
Command: npx skills add https://github.com/Nathan3303/nao-todo --skill frontend-ddd-nathan3303

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize frontend codebase using domain-driven design principles.

Core Features & Use Cases

  • Defines domain, application, and infrastructure boundaries (entities, repositories, services, use cases, adapters) for scalable frontend architectures.
  • Provides naming conventions, index exports, and dependency rules to maintain a clean monorepo structure.
  • Encourages consistent UI-layer integration while preserving domain purity across modules.

Quick Start

Create a small frontend module and apply domain boundaries to separate UI, application, and domain concerns.

Frequently Asked Questions about frontend-ddd

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

FAQPage Schema
How do I structure a frontend monorepo using domain-driven design?

Structure a frontend monorepo using domain-driven design by separating code into domain, application, and infrastructure layers. This approach defines clear boundaries for entities, repositories, services, use cases, and adapters to ensure scalable architecture.

What's the best way to enforce dependency rules in a Vue and TypeScript project?

Enforce dependency rules in a Vue and TypeScript project by applying domain-driven design boundaries. This method prescribes strict naming conventions and index exporting to maintain a clean, maintainable monorepo structure across modules.

Can I keep my UI layer clean while applying DDD architecture in frontend apps?

Yes, you can keep your UI layer clean while applying DDD architecture in frontend apps. This approach encourages consistent UI-layer integration while preserving domain purity across all application modules.

When do I need domain-driven design boundaries for my frontend codebase?

You need domain-driven design boundaries for your frontend codebase when organizing a scalable monorepo project. It becomes necessary to separate domain concerns from application and infrastructure logic to maintain long-term maintainability.

How do I separate entities, repositories, and services in a TypeScript frontend?

Separate entities, repositories, and services in a TypeScript frontend by establishing distinct domain, application, and infrastructure boundaries. This enforces specific dependency rules and naming conventions for scalable architecture.