development

Implement type-safe business logic with clean architecture and domain-driven design.

4|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/hiimtrung/coder --skill development-hiimtrung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development
Source: https://github.com/hiimtrung/coder/tree/main/.agents/skills/development
Command: npx skills add https://github.com/hiimtrung/coder --skill development-hiimtrung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams implement robust business logic with clean architecture, ensuring strong typing, solid error handling, and reliable external API integration.

Core Features & Use Cases

  • Use Case Execution: Standardized flows for context extraction, authorization checks, input validation, data retrieval, business rule validation, execution, persistence, and event publishing.
  • Type Safety & Validation: Enforces explicit typing, avoids runtime type hacks, and promotes domain-driven design.
  • External API Integration: Centralizes external calls and maps results to domain entities with proper error handling.
  • Guidance: Directs agents to consult the internal rules directory for consistency.

Real-world example: Implement a multi-tenant use case with proper isolation and domain-driven design.

Quick Start

Create a new use-case implementation following the standardized pipeline: context extraction, authorization, input validation, data retrieval, business rule validation, execution, persistence, and event publishing.

Frequently Asked Questions about development

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

FAQPage Schema
How do I implement type-safe business logic with clean architecture?

Implement type-safe business logic by following a standardized use-case pipeline: context extraction, authorization, input validation, data retrieval, business rule validation, execution, persistence, and event publishing, while enforcing explicit typing and domain-driven design principles.

What is the pipeline for executing use cases in domain-driven design?

Use-case execution in domain-driven design follows a standardized flow: context extraction, authorization checks, input validation, data retrieval, business rule validation, execution, persistence, and event publishing to ensure robust business logic.

How do I handle external API integration in a multi-layer architecture?

Handle external API integration by centralizing external calls and mapping their results to domain entities with proper error handling, maintaining clean architecture boundaries across multi-layer architectures.

How do I ensure multi-tenant isolation when applying SOLID principles?

Ensure multi-tenant isolation by applying domain-driven design constraints during the context extraction and authorization phases of the use-case execution pipeline, maintaining strict separation across tenant contexts.

When should I use clean architecture for use-case development?

Use clean architecture for use-case development when you need strong typing, solid error handling, reliable external API integration, and domain-driven design across multi-layer architectures and multi-tenant contexts.

Why avoid runtime type hacks in domain-driven design?

Avoid runtime type hacks in domain-driven design because enforcing explicit typing prevents runtime errors and ensures robust, type-safe business logic execution throughout the multi-layer architecture.