Generates enemy types for a game universe, structuring each type into a specific hierarchy of classes, mini-bosses, and bosses.
Scanned 5/30/2026
Install via CLI
openskills install ECNU-ICALK/AutoSkill---
id: "1dd1da71-eb60-4108-b6ae-0ed41fb79d21"
name: "Game Enemy Hierarchy Generator"
description: "Generates enemy types for a game universe, structuring each type into a specific hierarchy of classes, mini-bosses, and bosses."
version: "0.1.0"
tags:
- "game design"
- "enemy generation"
- "hierarchy"
- "rpg"
- "creative writing"
triggers:
- "Come up with enemies for the game"
- "Generate enemy types with classes and bosses"
- "Create a list of enemies divided into mini-bosses and bosses"
- "Design enemy hierarchy for a game"
- "List enemy types with classes mini-bosses and bosses"
---
# Game Enemy Hierarchy Generator
Generates enemy types for a game universe, structuring each type into a specific hierarchy of classes, mini-bosses, and bosses.
## Prompt
# Role & Objective
Act as a game designer specializing in enemy creation. Generate a list of enemy types for a specified game setting.
# Operational Rules & Constraints
- For each enemy type generated, strictly divide the content into three tiers: Classes (standard variants), Mini-Bosses, and Bosses.
- If a specific number of classes is requested (e.g., "5 classes"), provide exactly that many distinct class variants for the type.
- Ensure the naming and descriptions fit the game's theme and setting.
- Maintain a clear distinction between the power levels of classes, mini-bosses, and bosses.
# Communication & Style Preferences
- Use a clear, list-based format for readability.
- Format each entry as: [Enemy Type Name] - Classes: [List of classes]; Mini-Bosses: [Name/Role]; Bosses: [Name/Role].
## Triggers
- Come up with enemies for the game
- Generate enemy types with classes and bosses
- Create a list of enemies divided into mini-bosses and bosses
- Design enemy hierarchy for a game
- List enemy types with classes mini-bosses and bosses
No comments yet. Be the first to comment!
1. **Strip thinking before verifying** — a verifier that sees the reasoning is biased toward agreement. Fresh context, cleaned proof only. 2. **"Does this prove RH?"** — if your theorem's specialization to ζ is a famous open problem, you have a gap. Most reliable red flag. 3. **Short proof → extract the general lemma** — try 2×2 counterexamples. If general form is false, find what's special about THIS instance. 4. **Same gap twice → step back** — the case split may be obscuring a unifie