add=or-update-application

Add or update an application layer with command, dto, query, service, and usecase directories.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/GrowWeek/GrowWeek-Backend --skill add-or-update-application
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add=or-update-application
Source: https://github.com/GrowWeek/GrowWeek-Backend/tree/main/.claude/skills/application
Command: npx skills add https://github.com/GrowWeek/GrowWeek-Backend --skill add-or-update-application

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to introducing or modifying an application layer within a bounded context, reducing integration friction and ensuring consistent architecture.

Core Features & Use Cases

  • Directory conventions for application/{command, dto, query, service, usecase} that organize domain logic into clear boundaries.
  • Templates and examples for command, dto, query, and service implementations to accelerate development.
  • Use Case orchestration guidance for typical CRUD-like flows across the application layer, with guardrails for validation and repository interaction.

Quick Start

Create or update your application layer by organizing the directories under application/ as shown and implement the provided command, dto, query, service, and usecase patterns.

Frequently Asked Questions about add=or-update-application

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

FAQPage Schema
How do I structure an application layer within a bounded context?

Structure an application layer within a bounded context by organizing directories into application/{command, dto, query, service, usecase}. This enforces clear boundaries and consistent architecture for domain logic orchestration.

What is the best way to organize commands, queries, and DTOs in a usecase-driven architecture?

Organize commands, queries, and DTOs in a usecase-driven architecture by separating them into dedicated directories under the application layer. This provides templates for implementation and use case orchestration guidance.

How do I add validation and repository interaction guardrails for application layer use cases?

Add validation and repository interaction guardrails for application layer use cases by following the provided orchestration guidance for typical CRUD-like flows. This ensures consistent patterns across service implementations.

Does adding an application layer require a specific directory layout for discovery?

Adding an application layer requires a standard directory layout and a SKILL.md frontmatter with a name and description for discovery. This applies to projects structuring code into command, dto, query, service, and usecase folders.

Can I include on-demand scripts and references when updating an application layer?

You can include optional scripts/references/assets directories for on-demand tasks when updating an application layer. These sit alongside the core command, dto, query, service, and usecase structures.