Cursor rule

1# Java Coding Standards for Minecraft Fabric Mod
2 
3## General Standards
4- Use Java 21 features and syntax
5- Follow Minecraft/Fabric naming conventions
6- Use proper package structure: `com.example.modid` or `org.yourorg.mods.modname`
7- Implement `ModInitializer` interface for main mod class
8 
9## Fabric-Specific Guidelines
10- Use `net.fabricmc.api.ModInitializer` for mod entry point
11- Use `org.slf4j.Logger` for logging (not `System.out.println`)
12- Use `net.minecraft.util.Identifier` for resource locations
13- Use `net.minecraft.recipe.Ingredient` for recipe ingredients
14- Register items, blocks, and entities properly with registries
15 
16## Code Organization
17- Keep mod logic simple and focused
18- Use JSON recipes when possible instead of custom Java classes
19- Log initialization and important events
20- Follow Minecraft's existing code patterns
21- Separate client and server code appropriately
22- Use interfaces for API exposure
23 
24## Package Structure
25```
26com.example.mymod/
27├── MyMod.java              // Main mod class
28├── init/                   // Initialization classes
29│   ├── ModItems.java
30│   ├── ModBlocks.java
31│   └── ModRecipes.java
32├── items/                  // Custom item classes
33├── blocks/                 // Custom block classes
34├── client/                 // Client-only code
35└── util/                   // Utility classes
36```
37 
38## Example Structure
39```java
40package com.example.mymod;
41 
42import net.fabricmc.api.ModInitializer;
43import org.slf4j.Logger;
44import org.slf4j.LoggerFactory;
45 
46public class MyMod implements ModInitializer {
47    public static final String MOD_ID = "mymod";
48    public static final Logger LOGGER = LoggerFactory.getLogger(MOD_ID);
49 
50    @Override
51    public void onInitialize() {
52        LOGGER.info("Initializing {} mod", MOD_ID);
53        
54        // Initialize items, blocks, etc.
55        ModItems.register();
56        ModBlocks.register();
57        ModRecipes.register();
58    }
59}
60```
61 
62## Best Practices
63- Use constants for mod ID and other repeated strings
64- Handle null checks and edge cases
65- Document public APIs with Javadoc
66- Use meaningful variable and method names
67- Follow single responsibility principle
68- Minimize mixin usage when possible
69description:
70globs:
71alwaysApply: false
72---
73