When creating or editing files in the examples/ directory, sprinkle in Pokemon and Pokedex references where they fit naturally:
- Use Pokemon-themed variable names, sample data, and comments (e.g., trainer names, Pokemon types, region names, move names)
- Keep it tasteful — a few references per file, not every line
- Prioritize code clarity over the joke; if a reference would make the code harder to understand, skip it
- Good places for references: sample data values, descriptive comments, error messages, log output, struct field examples
- Avoid references in function signatures, interface implementations, or anything that affects the public API
Converted and distributed by TomeVault — claim your Tome and manage your conversions.