cloud-minestom: Skill for Claude Code

Scaffold an ArgumentMapper

Adds a new built-in Cloud-parser → native-Minestom-Argument mapping, following the exact pattern every existing mapper in StandardArgumentMappers already uses (see mapUuid/mapEnum/mapPlayer for reference before writing the new one - don't invent a different shape).

Before you start

1. Confirm there's a real, unambiguous native Minestom Argument type for this parser. If there isn't a sane one, the parser should stay on the Word/String/StringArray fallback (CommandTreeTranslator's own logic already does this automatically for anything with no registered mapper) - do not force a mapping that doesn't actually correspond to the parser's semantics. CLAUDE.md's anti-patterns section calls this out explicitly: a mapping that looks right but silently mismatches the parser's actual grammar is worse than the honest fallback.
2. If the native shape only approximates the parser's grammar (the way DurationParser/Time does), that's fine — but it must be called out in a comment on the mapper method and in docs/argument-mapping.md's "Known mismatches" section, not silently coerced.

Steps

1. The mapper method — in cloud-minestom/src/main/java/gg/cubix/cloudminestom/argument/StandardArgumentMappers.java:
   • Add a private static Argument<?> mapXxx(final CommandComponent<?> component, final ArgumentParser<?, T> parser) method, T being the parser's actual value type.
   • Cast parser to the concrete parser class if you need its configuration (bounds, mode, ...) — every existing mapper does this (see mapInteger's (IntegerParser<?>) parser cast).
   • Return the native Argument<?>, built via ArgumentType.Xxx(component.name()).
   • Add a one-line // comment only if there's a non-obvious why (a grammar mismatch, a Minestom-native quirk) — not a comment that just restates what the code does (CLAUDE.md).
2. Registration — add registry.register(XxxParser.class, StandardArgumentMappers::mapXxx); to registerAll(...), in the same class.
3. Unit test stub — in cloud-minestom/src/test/java/gg/cubix/cloudminestom/argument/StandardArgumentMappersTest.java:
   • Add a @Test method asserting the produced Argument is the expected type (and, if the parser has options like bounds, that they made it onto the native argument) — follow the existing integerParserMapsToIntegerHonoringBounds-style pattern.
4. Update docs/argument-mapping.md's table in the same commit — it's meant to be kept in sync with StandardArgumentMappers's actual registered set, not left to drift.
5. Update docs/spec.md §5.2's table too, with a short note in docs/roadmap.md if this reveals a gap the spec didn't originally anticipate (see the PlayerParser mapper's own roadmap entry, P8, for the precedent on how that correction was written up).