java

Generate Java project specifications with Spring Boot, JPA, and security constraints.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill java-pyl-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/java
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill java-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents fragile Java code and security regressions by forcing your project specification to include non-negotiable conventions for formatting, immutability, modern language features, Spring/JPA architecture, testing, and code-review security checks.

Core Features & Use Cases

  • Java documentation constraints: ensures your spec explicitly states required formatting, member ordering, and immutability rules (records, final-by-default, defensive copies).
  • Modern Java feature minimums: forces the minimum Java version and mandates how to use key features like records, sealed types, pattern matching, and switch expressions.
  • Spring Boot + JPA guardrails: requires constructor injection, correct transactional boundaries, DTO/record responses, and database performance constraints like preventing N+1 queries.
  • Security-focused review checklist: makes the spec explicitly cover injection/path traversal/PII logging/CSRF justification and error-handling rules.

Quick Start

Ask an AI to generate or review a Java project spec that conforms to this Skill for a Spring Boot service using JPA and includes the required security and architecture constraints.

Frequently Asked Questions about java

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

FAQPage Schema
How do I enforce modern Java conventions and prevent security regressions in Spring Boot?

To enforce modern Java conventions, generate a project specification that mandates constructor injection, records for DTOs, strict transactional boundaries, and a security checklist covering injection and PII logging for Spring Boot.

What is the best way to prevent N+1 queries and enforce immutability in JPA repositories?

Prevent N+1 queries and enforce immutability by applying a project spec that requires final-by-default fields, defensive copying, correct transactional boundaries, and explicit database performance constraints for JPA repositories.

How do I set up a security-focused code review checklist for Java projects?

Set up a security-focused code review checklist by generating a Java project specification that explicitly covers injection prevention, path traversal checks, CSRF justification, PII logging rules, and strict error handling requirements.

Can I use Java records and sealed types for DTO design in Spring Boot?

Yes, you can use Java records and sealed types for DTO design by enforcing a modern Java minimum version in your project spec, which mandates how to implement records, pattern matching, and switch expressions for Spring Boot responses.

Does generating a Java project specification require explicit testing thresholds?

Generating a Java project specification requires explicit testing thresholds and pagination constraints to act as code-review gating for common failure modes, ensuring consistent conventions during implementation.

When should I mandate constructor injection and strict error handling in Java applications?

Mandate constructor injection and strict error handling whenever generating a Java project specification to prevent fragile code, enforce Spring Boot architecture guardrails, and stop hidden security issues during implementation.