Establishes feature packages with domain, application, presentation, and infrastructure layers to maintain architectural boundaries and DDD principles.
Covers complete CRUD workflows: entity modeling with invariants, repository interfaces, JPA adapters, transactional services, DTO records, and REST controllers with proper HTTP status codes.
Includes validation patterns using jakarta.validat
Fetches spring-boot-crud-patterns from giuseppe-trisciuoglio/developer-kit and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/spring-boot-crud-patterns
Restart Cursor to activate spring-boot-crud-patterns. Access via /spring-boot-crud-patterns in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Provides complete CRUD workflows for Spring Boot 3.5+ services using feature-focused architecture. Creates and validates domain aggregates, JPA repositories, application services, and REST controllers with proper separation of concerns. Defer detailed code listings to reference files for progressive disclosure.
When to Use
Create REST endpoints for create/read/update/delete workflows backed by Spring Data JPA.
Implement feature packages following DDD-inspired architecture with aggregates, repositories, and application services.
Define DTO records, request validation, and controller mappings for external clients.
Diagnose CRUD regressions, repository contracts, or transaction boundaries in existing Spring Boot services.
Trigger phrases: "implement Spring CRUD controller", "create an endpoint", "add database entity", "refine feature-based repository", "map DTOs for JPA aggregate", "add pagination to REST list endpoint".
Instructions
Follow this streamlined workflow to deliver feature-aligned CRUD services with explicit validation gates:
1. Establish Feature Structure
Create feature/<name>/ directories with domain, application, presentation, and infrastructure subpackages.
Validate: Verify directory structure matches the feature boundary before proceeding.
2. Define Domain Model
Create entity classes with invariants enforced through factory methods (create, update). Keep domain logic framework-free.
Validate: Assert all invariants are covered by unit tests before advancing.
3. Expose Domain Ports
Declare repository interfaces in domain/repository describing persistence contracts without implementation details.
Validate: Confirm interface signatures match domain operations.
4. Provide Infrastructure Adapter
Create JPA entities in infrastructure/persistence that map to domain models. Implement Spring Data repositories.
Validate: Run @DataJpaTest to verify entity mapping and repository integration.
5. Implement Application Services
Create @Transactional service classes that orchestrate domain operations and DTO mapping.
Validate: Ensure transaction boundaries are correct and optimistic locking is applied where needed.
6. Define DTOs and Controllers
Use Java records for API contracts with jakarta.validation annotations. Map REST endpoints with proper status codes.
Validate: Test validation constraints and verify HTTP status codes (201 POST, 200 GET, 204 DELETE).
7. Validate and Deploy
Run integration tests with Testcontainers. Verify migrations (Liquibase/Flyway) mirror the aggregate schema.
Validate: Execute full test suite before deployment; confirm schema migration scripts are applied.
See references/examples-product-feature.md for complete code aligned with each step.
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
