ddd-structure-flow

Organizes Ledger Wallet code placement across DDD monorepo layers and packages.

615|491|Updated Jan 4, 2022

Search Tags:#DDD #code organization #package structure #Monorepo #dependency boundaries #Code review #ledger wallet

One-click install

npx skills add https://github.com/LedgerHQ/ledger-live --skill ddd-structure-flow

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ddd-structure-flow
Source: https://github.com/LedgerHQ/ledger-live/tree/main/.cursor/skills/ddd-structure-flow
Command: npx skills add https://github.com/LedgerHQ/ledger-live --skill ddd-structure-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers working in the Ledger Wallet monorepo often struggle to decide where new code belongs, which layer should own a concern, and how to respect dependency boundaries across apps, features, domain, shared, and support layers.

Core Features & Use Cases

Code Placement Guidance: Determines the correct layer (apps, features, domain, shared, support) for new or moved code in the DDD monorepo.
Boundary Enforcement: Checks package names, dependency boundaries, platform variants, and legacy imports during code review.
Use Case: When creating a new feature package for Ledger Wallet Desktop, use this Skill to decide its layer ownership, structure its flow steps, and verify it does not violate cross-layer dependency rules.

Quick Start

Ask the assistant to review where a new Ledger Wallet feature should live in the DDD monorepo and validate its package structure and dependency boundaries.

Frequently Asked Questions about ddd-structure-flow

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

FAQPage Schema

How do I decide which layer owns new code in a DDD monorepo?▼

Evaluate the concern's scope: feature-specific logic goes in features, reusable business rules in domain, cross-cutting utilities in shared, and infrastructure concerns in support. This Skill applies those rules to the Ledger Wallet monorepo layout.

How to structure packages and flow steps in Ledger Wallet?▼

Follow the canonical ddd-structure-flow rules referenced by this Skill, which define package naming, flow step organization, and platform variant handling for apps, features, domain, shared, and support layers.

Does this Skill check dependency boundaries between layers?▼

Yes, it reviews dependency boundaries, package names, platform variants, and legacy imports when creating, moving, or reviewing code in the monorepo.

When should I use this Skill during code review?▼

Use it whenever a pull request adds, moves, or reorganizes code under apps, features, domain, shared, or support, to confirm the change respects layer ownership and dependency rules.