agentleFS
Sign inStart free
AloisSeckarAloisSeckar/demos-java/.agents/skills/demo-create/SKILL.md

demo-create

Skill25 starsChanged 7 days agoUnlicenseView on GitHub

Create a standalone JEP demo in demos-java. Use when adding a final JEP with no preview/incubator predecessors.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. southliu/south-admin-react★ 582same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow CONTRIBUTING.md for templates, registration conventions, and generated files.

    line 12
  2. Very specific:

    Read https://openjdk.org/jeps/<jep-number> for the title, target JDK, status, history, and relevant APIs.

    line 19
  3. Very specific:

    Create a descriptively named IDemo implementation in org.javademos.java<jdk>.jep<jep-number>.

    line 22
  4. Very specific:

    Start demo() with info(<jep-number>).

    line 23
  5. Very specific:

    Add the entry to src/main/resources/JDK<jdk>Info.json with "link": false and "code": true (false for explanation-only demos).

    line 27
  6. Very specific:

    Run mvn clean install and the jar using the command in CONTRIBUTING.md.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create a JEP Demo

Input: one JEP number. Ask for it if missing. For a JEP with earlier preview/incubator iterations, use demo-update instead.

Follow CONTRIBUTING.md for templates, registration conventions, and generated files. Use LazyConstantsDemo.java as the style baseline for demos with executable code. For explanation-only demos (no code to show), use GenerationalZGC23Demo.java instead.

Workflow

  1. Read https://openjdk.org/jeps/<jep-number> for the title, target JDK, status, history, and relevant APIs. Confirm the target JDK package, JSON resource, and loader exist; report missing release infrastructure as out of scope.
  2. Create a descriptively named IDemo implementation in org.javademos.java<jdk>.jep<jep-number>. Start demo() with info(<jep-number>). Use a /// header with a single-entry JEP history and relevant reading links. Based on nature of the feature, consider whether it can have executable code demo or not. Some features only require an explanation via comments. If there is a code to be shown, keep the example small and runnable; accompany code with explanatory comments.
  3. Add the entry to src/main/resources/JDK<jdk>Info.json with "link": false and "code": true (false for explanation-only demos). Import and register the class in src/main/java/org/javademos/init/Java<jdk>DemoLoader.java. Keep both registrations in ascending JEP order.
  4. Run mvn clean install and the jar using the command in CONTRIBUTING.md. Inspect the new demo by appending --only=<jep-number> to the jar command (other demos print exceptions on purpose). Confirm the new JEP's header and expected output appear without exceptions, and review the diff for unrelated changes.
  5. Branch, commit, and open the PR by following pr-create for <jep-number>.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free