endpoint-implementation
Use this skill to implement endpoints in the API
Security Assessment
About endpoint-implementation
The 'endpoint-implementation' skill provides a framework for implementing API endpoints in a structured and standardized manner. It aims to streamline the process of endpoint development by enforcing consistent coding practices and offering clear guidelines on how to structure endpoint features within the system. This skill allows developers to implement endpoints in a way that aligns with the architectural patterns used across the system, particularly focusing on maintaining clean and maintainable code. By using predefined structures and conventions, this skill helps reduce development time and improve collaboration among teams working on different parts of the API.
FAQ
How should I structure my endpoint code using this skill?
You should use record classes to model the command, response, and events for your endpoint. The business logic should be implemented in a class postfixed with 'Endpoint', and the endpoint method should be called 'Handle'. Use the appropriate Wolverine attributes like '[WolverinePost]', '[WolverineGet]', '[WolverinePut]', or '[WolverineDelete]' for HTTP access.
What kind of validation is required for custom logic?
For custom validations that cannot be modeled with FluentValidation, you should use a 'Validate' method to handle these validations explicitly within your endpoint.
Are there any specific file structures I need to follow?
Yes, the skill recommends organizing your code into feature groups and slices. For example, 'Users', 'Prompts', 'Repositories', and 'Skills' should be separate feature groups, with each endpoint represented as a feature slice inside the corresponding group.
Install endpoint-implementation
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
wmeints/promptyard