agentleFS
Sign inStart free
vvs1offvvs1off/fabric-skills/skills/new/SKILL.md

new

Skill4 starsChanged 12 days agoMITView on GitHub

Scaffold a new Minecraft Fabric mod project (asks for name, mod id, Minecraft version and whether it is client-only, then generates a project that builds).

  • Reads credentials

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use upgrade, gate and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • agenticnotetakingSkill

    upgrade

    Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

    Also in 4 projects that use this

  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    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. Very specific:

    Create a new, buildable Fabric mod.

    line 10
  2. Very specific:

    Ask the user for (use $ARGUMENTS as the mod name if it was given):

    line 15
  3. Distinctive:

    Minecraft version: - default to the latest stable release (see step 2).

    line 22
  4. Very specific:

    Target directory: - default ./<modid>; refuse to write into a non-empty directory without explicit confirmation.

    line 26
  5. Distinctive:

    If the network is unavailable, stop and tell the user.

    line 38
  6. Very specific:

    Prefer copying the Gradle wrapper (gradlew, gradlew.bat, gradle/wrapper/*) from the official fabric-example-mod (or running gradle wrapper …

    line 42
  7. Very specific:

    Use YOUR_NAME placeholders for authors/URLs unless the user gives real values.

    line 64
  8. Distinctive:

    No hardcoded versions came from memory.

    line 79

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “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

/fabric-skills:new - scaffold a new Fabric mod

Create a new, buildable Fabric mod. Follow the fabric-project-setup skill for every file you write; this command only decides the order and asks the questions.

1. Ask, then confirm

Ask the user for (use $ARGUMENTS as the mod name if it was given):

  1. Mod name (display name, e.g. "Better Pings").
  2. Mod id - propose one derived from the name (lowercase, a-z0-9_-, starts with a letter, 2-64 chars, e.g. betterpings) and let the user accept or change it.
  3. Java package - propose com.example.<modid> (strip -/_); remind them to use a domain or io.github.<username> they actually control.
  4. Minecraft version - default to the latest stable release (see step 2). Mention if the chosen version is before 26.1 (Yarn/remapping era) and what that implies.
  5. Client-only? (HUD/minimap/QoL mods: yes; anything adding blocks, items, entities or gameplay rules: no).
  6. Target directory - default ./<modid>; refuse to write into a non-empty directory without explicit confirmation.

Show a one-screen summary and wait for confirmation before writing files.

2. Look up versions (do not use remembered numbers)

If the network is unavailable, stop and tell the user; do not invent versions.

3. Generate

Prefer copying the Gradle wrapper (gradlew, gradlew.bat, gradle/wrapper/*) from the official fabric-example-mod (or running gradle wrapper --gradle-version <v> if Gradle is installed). Never write gradle-wrapper.jar by hand.

Then write, per fabric-project-setup:

  • settings.gradle, gradle.properties, build.gradle for the right era (26.1+: net.fabricmc.fabric-loom, no mappings; older: net.fabricmc.fabric-loom-remap + loom.officialMojangMappings()).
  • splitEnvironmentSourceSets() always.
  • src/main/resources/fabric.mod.json with "environment": "client" for client-only mods.
  • Entrypoints: a main ModInitializer for normal mods; client-only mods may have only the client entrypoint.
  • Mixin config(s) with no mixins yet ("mixins": []), defaultRequire: 1, and the right compatibilityLevel. Do not add example mixins the user did not ask for.
  • assets/<modid>/lang/en_us.json. Only add "icon" to fabric.mod.json if you actually create assets/<modid>/icon.png (e.g. the user provides one); otherwise omit the field and tell the user how to add an icon later. Never reference files that do not exist.
  • .gitignore (at least .gradle/ build/ run/ out/ .idea/ *.iml .vscode/ logs/ crash-reports/ .env *.key *.jks) and .gitattributes (gradlew text eol=lf, *.bat text eol=crlf).
  • A short README.md and, if the user wants, a LICENSE (ask which one; do not assume).

Use YOUR_NAME placeholders for authors/URLs unless the user gives real values.

4. Verify

./gradlew build

Fix every error until it passes. Report the build result honestly. Offer (do not auto-run) ./gradlew runClient as the next step, and git init if the directory is not a repository.

Done when

  • ./gradlew build succeeds.
  • fabric.mod.json id == loom.mods key == MOD_ID == assets/<modid>.
  • No hardcoded versions came from memory; no credentials or personal paths in any file.

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