generate-project-artifact
Creates an antifact following the project's patterns and methods. Use when you need to create a new artifact in a bounded context/module. Use to create new entities, services, repositories, or any other artifact in the application. It internally uses the /generate command.
When & Why to Use This Skill
This Claude skill streamlines software development by automatically generating project-specific artifacts such as entities, services, and repositories. By analyzing existing patterns and folder structures, it ensures that new code seamlessly integrates with the established architecture, maintaining consistency and reducing manual boilerplate effort.
Use Cases
- Scaffolding new domain entities and their corresponding repositories while strictly adhering to the project's architectural patterns.
- Accelerating the development of new modules or bounded contexts by generating standardized service layers and implementation files.
- Ensuring codebase consistency when multiple developers are adding new components, by enforcing the use of predefined templates and structural rules.
| name | Generate project artifact |
|---|---|
| description | Creates an antifact following the project's patterns and methods. Use when you need to create a new artifact in a bounded context/module. Use to create new entities, services, repositories, or any other artifact in the application. It internally uses the /generate command. |
Usage
/generate [artifact] [bounded-context] [name]
Instructions
- The
/generatecommand will tell you if you choose correctly an existent and valid artifact. Careful with this. - [MUST DO] You must call the
code_understanderskill if you didn't make it yet. This file contains the artifact implementation details and rules, and you MUST READ the respective artifact reference before calling the /generate command. - [MUST DO] Use the
structure_understanderskill, if you didn't make it yet, to read and understand the folder structure of the project, before starting implementing.