mirror of
https://github.com/domfelipe/pokebuddy.git
synced 2026-08-07 05:56:50 +00:00
69 lines
987 B
Markdown
69 lines
987 B
Markdown
# Creature Guidelines
|
|
|
|
PokeBuddy companions should feel original, developer-native and terminal-friendly.
|
|
|
|
## Design principles
|
|
|
|
A good companion is:
|
|
|
|
- memorable at small size;
|
|
- readable in terminal output;
|
|
- strongly associated with a dev concept;
|
|
- cute enough to like;
|
|
- weird enough to remember;
|
|
- original enough to publish safely.
|
|
|
|
## Companion anatomy
|
|
|
|
Each companion should define:
|
|
|
|
- `id`
|
|
- `name`
|
|
- `type`
|
|
- `rarity`
|
|
- `personality`
|
|
- `flavor`
|
|
- `quote`
|
|
- `likes`
|
|
- `dislikes`
|
|
- `stats`
|
|
- `reactions`
|
|
- `ascii`
|
|
|
|
## Types
|
|
|
|
Recommended types:
|
|
|
|
- Logic
|
|
- Spark
|
|
- Storage
|
|
- Memory
|
|
- Void
|
|
- Debug
|
|
- AI
|
|
- Prompt
|
|
- Cache
|
|
- Chaos
|
|
- Git
|
|
- Fire
|
|
- Infra
|
|
- Shell
|
|
- Network
|
|
- Data
|
|
- Security
|
|
- Build
|
|
- Test
|
|
- Docs
|
|
|
|
## Rarities
|
|
|
|
- Uncommon
|
|
- Rare
|
|
- Epic
|
|
- Mythic
|
|
|
|
## Avoid
|
|
|
|
Do not create companions that copy or closely resemble protected characters, recognizable franchise silhouettes, official sprites, official names or modified official names.
|
|
|
|
Keep it original. Keep it dev-flavored.
|