domain-packages

Name: domain-packages
Availability: InStock
Author: aydadevelop

Scaffolds new domain packages with predefined architectural templates in monorepos.

Updated Aug 27, 2026

Search Tags:#package management #scaffolding #domain-driven design #monorepo #Drizzle #oRPC

Ready to run

npx skills add https://github.com/aydadevelop/turborepo-starter --skill domain-packages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-packages
Source: https://github.com/aydadevelop/turborepo-starter/tree/main/.agents/skills/domain-packages
Command: npx skills add https://github.com/aydadevelop/turborepo-starter --skill domain-packages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of new, self-contained domain packages within a monorepo, ensuring consistency and adherence to architectural patterns.

Core Features & Use Cases

Scaffolding: Generates the necessary directory structure, package.json, and tsconfig.json for a new domain package.
Architectural Guidance: Provides templates and rules for defining repositories, services, workflows, and oRPC contracts.
Use Case: When starting a new feature that requires a distinct business domain, like 'inventory' or 'user-profiles', use this Skill to quickly set up the foundational package structure and adhere to the project's established layering and dependency rules.

Quick Start

Use the domain-packages skill to scaffold a new package named 'catalog'.

Frequently Asked Questions about domain-packages

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

FAQPage Schema

How do I scaffold a new domain package in a monorepo?▼

Scaffolding a new domain package in a monorepo involves generating the directory structure, package.json, and tsconfig.json alongside templates for Drizzle repositories, domain services, and oRPC contracts to enforce dependency rules.

What is the best way to enforce architectural layering for domain-driven design packages?▼

Enforcing architectural layering for domain-driven design packages is achieved by defining strict boundaries between Drizzle repositories, domain services, and thin handlers, ensuring maintainable codebases through established dependency rules.

Can I use this scaffolding for contract-first and event-driven architectures?▼

Yes, this scaffolding supports contract-first, event-driven, and provider-based architectures by generating structural templates that define oRPC contracts and domain workflows within a self-contained monorepo package.

How do I set up Drizzle repositories and oRPC contracts for a new feature?▼

Setting up Drizzle repositories and oRPC contracts for a new feature requires scaffolding a dedicated domain package that templates the data access layer and API contract definitions while enforcing architectural dependency rules.

Does domain package scaffolding separate business logic from API handlers?▼

Yes, domain package scaffolding separates business logic from API interactions by defining thin handlers that route requests to self-contained domain services and Drizzle repositories without coupling logic to the transport layer.