add-or-update-presentation

Name: add-or-update-presentation
Availability: InStock
Author: GrowWeek

Create or update REST presentation layers with DTO-based request, response, and controller structures.

Updated Dec 11, 2025

Search Tags:#architecture #frontend-backend #dto #bounded-context #rest-api #presentation-layer

Ready to run

npx skills add https://github.com/GrowWeek/GrowWeek-Backend --skill add-or-update-presentation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-or-update-presentation
Source: https://github.com/GrowWeek/GrowWeek-Backend/tree/main/.claude/skills/presentaion
Command: npx skills add https://github.com/GrowWeek/GrowWeek-Backend --skill add-or-update-presentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bounded Context에 새로운 presentation 레이어를 추가하거나 수정할 때의 표준화된 가이드를 제공합니다. 이 스킬은 프레젠테이션 레이어의 구조를 일관되게 유지하고, 도메인 레이어와의 의존성 관리 및 DTO 기반 데이터 흐름 설계를 돕습니다.

Core Features & Use Cases

Presentation 레이어 구조를 표준화된 REST 계층(rest/request, rest/response, rest/controller 등)으로 구성합니다.
도메인 로직에서 VO를 직접 사용하지 않고 프레젠테이션에 맞는 DTO를 사용하도록 강제합니다.
Bounded Context 내 프레젠테이션 레이어의 확장이나 수정이 필요할 때 빠르고 안전하게 적용할 수 있습니다.

Quick Start

Create or update the presentation/rest structure and define DTOs, ensuring no direct VO usage.

Frequently Asked Questions about add-or-update-presentation

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

FAQPage Schema

How do I add a presentation layer to a bounded context using DTOs?▼

To add a presentation layer to a bounded context, create a standardized REST directory structure including request, response, and controller components, ensuring data flows through DTOs instead of domain VOs.

Why should I use DTOs instead of domain VOs in a REST API presentation layer?▼

Using DTOs instead of domain VOs in a REST API presentation layer enforces clean separation between the presentation and domain layers, maintaining consistent data flow and preventing domain logic from leaking into the API structure.

What is the standard directory structure for a RESTful presentation layer?▼

The standard RESTful presentation layer directory structure organizes code into specific subdirectories such as rest/request, rest/response, and rest/controller to maintain architectural consistency within a bounded context.

Can I update an existing presentation layer without breaking the bounded context architecture?▼

You can update an existing presentation layer safely by modifying the rest structures and DTOs, which constrains implementation to a DTO-based data flow and preserves the bounded context architecture.

When do I need to separate presentation DTOs from domain VOs?▼

You need to separate presentation DTOs from domain VOs when implementing a RESTful presentation layer, as it enforces a DTO-based data flow and standardizes the boundary between API endpoints and domain logic.

What's the best way to structure controllers and DTOs in a bounded context?▼

The best way to structure controllers and DTOs in a bounded context is to follow a standardized rest directory layout that separates request, response, and controller files while enforcing DTO-based data flow over domain VOs.