Skip to content
Skills Library
Programming · Review & audit

cc-java-project-standard

/cc-java-project-standard

Use when Java package/module structure, build-tool conventions, application boundaries, exceptions, persistence ownership or repository-wide Java engineering needs design or review.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
9
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: examples/engineering/ResourceBoundary.java, examples/engineering/ResourceBoundaryTest.java

What it does and when to use it

Use when Java package/module structure, build-tool conventions, application boundaries, exceptions, persistence ownership or repository-wide Java engineering needs design or review.

Original author description

Use when Java package/module structure, build-tool conventions, application boundaries, exceptions, persistence ownership or repository-wide Java engineering needs design or review.

How it works

  1. Apply the workflow
  2. Task boundary
  3. Engineering practices
Original SKILL.md headings · 22 lines, 179 words
SKILL.md preview
---
name: cc-java-project-standard
description: "Use when Java package/module structure, build-tool conventions, application boundaries, exceptions, persistence ownership or repository-wide Java engineering needs design or review."
---

# Java project engineering

Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language.

Read the declared JDK, build descriptor, wrapper and existing package layering. Preserve the current language level and dependency platform.

## Apply the workflow

1. Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now.
2. Apply the [specialist checks](references/practice.md), establishing the input evidence before selecting the smallest change.
3. Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result.
4. Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only.

## Task boundary

JVM profiling and pool/GC incidents belong to the runtime specialty; do not impose a particular web framework.

## Engineering practices

Read the [local engineering decisions](references/engineering-practices.md) for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.
Files in this package (9)
  • SKILL.md 2 KB
  • examples/engineering/README.md 1 KB
  • examples/engineering/ResourceBoundary.java 1 KB
  • examples/engineering/ResourceBoundaryTest.java 2 KB
  • references/engineering-practices.md 4 KB
  • references/practice.md 2 KB
  • references/common/engineering-practices.md 12 KB
  • references/common/engineering-practices.rules.json 2 KB
  • references/common/engineering-practices.sources.json 16 KB

Versions

The database has no other skills named cc-java-project-standard.

Database snapshot: 13.11.2026 · package version 7008f09d7b64 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90cc-go-project-standard
    Use when Go module/workspace organization, package ownership, error and context conventions, dependency boundaries or engineering validation need design or review.
  • 90cc-rust-project-standard
    Use when Rust crate or workspace structure, module boundaries, ownership-facing APIs, Result conventions, Cargo dependencies or engineering checks need design or review.
  • 100architecture-review
    Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
  • 100200-agents-md
    Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs.…
  • 100java-package-structure
    Use when creating or extending a Java or Spring Boot project, adding a new entity, endpoint, controller, service or repository, deciding which package a Java class belongs in, or when a controller and service end up in the same file.
  • 100java-17-to-java-21-upgrade
    Comprehensive best practices for adopting new Java 21 features since the release of Java 17. Triggers on: ['*']

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.