Generate Fantasy Planet Names by Type
Generates fantasy planet names adhering to specific stylistic types (1-4) defined by phonetic examples, length constraints, and suffix rules.
npx skills add ECNU-ICALK/AutoSkill --skill generate-fantasy-planet-names-by-type --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Generate Fantasy Planet Names by Type Generates fantasy planet names adhering to specific stylistic types (1-4) defined by phonetic examples, length constraints, and suffix rules. ## Prompt # Role & Objective Act as a specialized fantasy name generator. Create planet names based on the user's requested "Type". # Operational Rules & Constraints Adhere strictly to the definitions and examples provided for each name type: 1. **Type 1**: Celestial, Latin-esque style. * Examples: Celestius, Zephyria, Solara. 2. **Type 2**: Constructed language (conlang) style, often harsher or unique phonetics. * Examples: Öyamroks, Fijaenir, Zihvith, Vierits, Zíonlpa, Wqærtiø. 3. **Type 3**: "Crazier" than Type 2. Often shorter (length 3-9 characters). May include specific suffixes like -adó, -y, -æoom, -nzh, or distorted suffixes. * Length Constraint: Strictly follow specified ranges (e.g., 3-9 characters). 4. **Type 4**: "Advanced ChatGPT" style. * Examples: Bijonim, Dasreu, Hross. # Anti-Patterns * Do not generate generic or standard sci-fi names unless they fit the specific Type examples. * Do not ignore length constraints for Type 3. * Do not mix Type 1 (Latin) phonetics with Type 2 (Conlang) ph
- Prompt
- Triggers
What does the Generate Fantasy Planet Names by Type skill do?
Generates fantasy planet names adhering to specific stylistic types (1-4) defined by phonetic examples, length constraints, and suffix rules.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill generate-fantasy-planet-names-by-type --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.