project-name-gen

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# project-name-gen

Generate project codenames with a distinct aesthetic: **technofuturism meets
mysticism**. Think Myst, The Matrix, Battlestar Galactica, The Talos Principle —
names that feel like they belong to both an ancient cult and a starship.
The user is a technomancer; a name is an incantation bound to a machine, so
pick words that would work in both a ritual and a deploy log.

## Themes to draw from

Mix across these veins; the best names often sit at an intersection:

- **Cyberpunk**: Tyrell, Mercer, Cassan, Eridu, Wintermute
- **Clearly futuristic codenames**: Nexus, Razorcoil
- **Mythology** — prefer lesser-known figures over the Zeus/Thor tier
- **Philosophy**: Theseus (as in the ship), thought experiments, obscure concepts
- **Celestial**: Altair, Lyra, Polaris, Deneb — stars, constellations, deep-sky objects
- **Latin / Indo-European / Mesopotamian roots**: Zephyr, Paragon — words that
  sound rooted even when coined
- **Myst-style invented words**: Releeshan, Aspermere — plausible-sounding
  constructions that don't exist but feel like they should
- **Occult & esoteric**: Alkahest, Sator, Lamassu — alchemy, hermeticism,
  Mithras, gnosticism; the more obscure, the better
- **Lost / Dharma Initiative station names**: The Lamp Post, The Tempest —
  mundane words made numinous by context; with a Buddhist undertone where it
  fits (Bardo, Kalpa, Sunyata)

## Rules

1. **Fit the project.** Ground names in what the project actually is or does —
   pull from the conversation context. A name should resonate with the thing's
   purpose (a metaphor, a function, a mythological parallel), not just sound cool.
2. **Prefer obscure over famous.** Deep-cut references beat well-worn ones.
   Skip anything a casual reader would immediately place.
3. **No unintended real-world associations.** Before proposing a name, sanity-check
   it: existing well-known products, companies, or brands; awkward meanings in
   major languages; loaded political/religious connotations. Reject collisions.
   (Obscure shared roots are fine — total uniqueness isn't required.)
4. **Codename shape.** Single word, easy to say and type, works as a repo name.
   Two-part names only if the user asks.

## Output

Propose ~6–10 candidates as a list: **Name** — one line on origin and why it
fits this project. Order by how well they fit, best first. If the user's context
is thin, ask one short question about the project's nature before generating.

From cschomburg/dotfiles, MIT.

More from cschomburg/dotfiles