Action Pattern

Use this skill to design, implement, or review non-trivial application use cases as Actions: single-purpose classes or functions that live in their own files, receive dependencies explicitly, accept context-free runtime data, execute one business operation, and can be tested directly.

This skill solves the "fat controller" and "god service" problem by moving business workflows out of entry points and broad services into small, named units such as RegisterUserAction, ProcessPaymentAction, or SendInvitationAction.

Activation Criteria

Use this skill when the task is to:

• Create, refactor, or review a business operation, use case, command, application service, or workflow.
• Move logic out of a controller, route handler, CLI command, job, listener, or broad service.
• Organize business rules that coordinate repositories, services, notifications, events, transactions, or external systems.
• Make a use case independently testable without running through HTTP, CLI, queue, or framework entry points.

Do not use this skill when the task is only to: