development

Name: development
Availability: InStock
Author: TAKAYA

Implement use-case pipelines with clean architecture and explicit typing.

Updated Feb 27, 2026

Search Tags:#tdd #solid #design-patterns #business-logic #domain-driven #external-api

Ready to run

npx skills add https://github.com/takayatomose/tas-agent-skills --skill development-takayatomose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: development
Source: https://github.com/takayatomose/tas-agent-skills/tree/main/.agents/skills/development
Command: npx skills add https://github.com/takayatomose/tas-agent-skills --skill development-takayatomose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The role provides a structured approach to implementing robust business logic using clean architecture, SOLID principles, and strong error handling to reduce bugs and maintenance costs.

Core Features & Use Cases

Explicit typing and domain-driven design to ensure correctness across boundaries.
Use-case pipeline guidance: context extraction, authorization, validation, persistence, and event publishing.
Multi-tenancy awareness and safe external API integration via dedicated clients.

Quick Start

Define a new feature by extracting context and tenant, validate inputs, implement use-case logic with clean architecture, handle errors, and publish domain events.

Frequently Asked Questions about development

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

FAQPage Schema

How do I implement clean architecture for business logic without creating a tangled codebase?▼

Structure business logic use-cases as a pipeline: extract context and tenant, authorize, validate inputs, execute core logic, handle errors, and publish domain events. This enforces clean architecture boundaries and reduces maintenance costs.

What is the best way to handle external API integration in a multi-tenant application?▼

Handle external API integration in a multi-tenant application by routing requests through dedicated clients in a centralized client layer, ensuring safe isolation, explicit typing, and domain-driven correctness across boundaries.

How does SOLID principles combined with TDD help enforce domain-driven design?▼

SOLID principles and TDD enforce domain-driven design by requiring explicit typing and strict isolation of external logic, ensuring correctness across boundaries and guiding use-case pipelines from validation to event publishing.

Can I use this approach for multi-tenant use-case execution and error handling?▼

Yes, this approach applies directly to multi-tenant use-case execution and error handling by enforcing explicit typing, domain-driven patterns, and safe external API integration through dedicated clients across the application.

When should I not use a centralized client layer for external API logic?▼

Avoid a centralized client layer for external API logic when your application lacks multi-tenancy requirements or complex domain boundaries, as the overhead of explicit typing and clean architecture may outweigh maintenance benefits.