AI Agent Hub
Back to skills
Boss Fight Planner Assistant icon

Boss Fight Planner Assistant

Professional Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_15292d5a/yjkj-boss-fight-planner-skill into your AI assistant.

About this skill

Problem

When delegating Boss Fight design to an LLM, the output often lacks structure, reusability, or safe review points. It may mix in irreversible actions, ask for secrets, or rely on improvised commands and external scraping. boss-fight-planner-skill targets Game Design by turning the Boss Fight Planner approach into a copy-safe prompt structure built on clear templates, checks, and safe defaults.

How It Works

The input is a one-paragraph goal that excludes secrets. Optional constraints include audience, tone, length, and deadline. You may also paste notes that you own rights to while keeping PII minimal. The skill shapes the response into:
- Concise plan: a high-level direction for quick alignment
- Numbered checklist: actionable Boss Fight steps that can be reviewed item by item
- Short next actions: a compact list to continue work without additional prompts
- Editable draft blocks: copyable wording that can be revised instead of executing unknown code

The safety boundary is explicit: it does not collect passwords, OTPs, private keys, wallets, seeds, or session secrets; it does not recommend running unseen remote installers or chained download-and-run snippets; and it favors factual, reversible outputs such as checklists. It fits engineers or designers who need stable prompts, draft review, and repeatable planning; it is not intended for auto-scraping external data, destructive execution, or high-sensitivity credential handling.

Use Cases

  • When designing a Boss Fight, turn scattered ideas into a reviewable concise plan, numbered checklist, and next actions.
  • When reviewing a Boss Fight draft, request clearer and safer wording plus editable draft copy blocks.
  • When setting up a weekly Boss Fight check, produce a reusable checklist without asking for passwords, keys, wallets, or session secrets.
  • When writing player-facing combat notes, constrain audience, tone, and length to generate editable draft copy.

Best For

  • Game designers: need to break Boss Fight mechanics into executable, checkable, reversible design steps.
  • Gameplay copywriters: need to revise rough drafts into clearer and safer player-facing explanations.
  • Project leads: need a reusable weekly checklist to avoid ad-hoc prompt drift.
  • Design-assistance engineers: need copy-safe structured output without collecting private keys, wallets, or other secrets.