quest-design-patterns
A specialized skill for the quest-designer agent covering quest design patterns. Provides quest archetypes, reward psychology, difficulty curves, and player motivation frameworks. Use for 'quest design,' 'reward systems,' 'mission structure,' 'quest patterns,' and similar topics.
Best use case
quest-design-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
A specialized skill for the quest-designer agent covering quest design patterns. Provides quest archetypes, reward psychology, difficulty curves, and player motivation frameworks. Use for 'quest design,' 'reward systems,' 'mission structure,' 'quest patterns,' and similar topics.
Teams using quest-design-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/quest-design-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How quest-design-patterns Compares
| Feature / Agent | quest-design-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
A specialized skill for the quest-designer agent covering quest design patterns. Provides quest archetypes, reward psychology, difficulty curves, and player motivation frameworks. Use for 'quest design,' 'reward systems,' 'mission structure,' 'quest patterns,' and similar topics.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Quest Design Patterns — Quest Design Pattern Methodology Specialized game design knowledge used by the quest-designer agent when designing main/side quests. ## Why Patterns Are Needed Quests are the **glue connecting narrative and gameplay**. If the game just repeats "go kill 10 of these," players will disengage. Combining diverse structural patterns is what keeps players saying "just one more quest." ## 12 Quest Archetypes ### Combat/Action Category | # | Archetype | Core Loop | Narrative Function | Risk Factor | |---|-----------|-----------|-------------------|-------------| | 1 | **Hunt** | Eliminate a specific target | Threat removal, proving heroism | Can become repetitive -> Give the target a story | | 2 | **Defense** | Protect a base/NPC | Sense of responsibility, time pressure | Frustration on failure -> Provide partial success options | | 3 | **Pursuit** | Track a fleeing target | Tension, spatial utilization | Repeated failure -> Adjust difficulty with staged clues | ### Exploration/Discovery Category | # | Archetype | Core Loop | Narrative Function | Risk Factor | |---|-----------|-----------|-------------------|-------------| | 4 | **Exploration** | Discover unknown regions | World-building expansion, curiosity | Loss of direction -> Guide with environmental storytelling | | 5 | **Collection** | Gather items/information | Deepening world understanding | Tedious errands -> Add mini-narrative to each item | | 6 | **Puzzle** | Solve puzzles/ciphers | Intellectual achievement, learning world rules | Getting stuck -> Provide tiered hint system | ### Social/Relationship Category | # | Archetype | Core Loop | Narrative Function | Risk Factor | |---|-----------|-----------|-------------------|-------------| | 7 | **Escort** | Accompany an NPC | Relationship building, character development | Slow NPC -> Ensure AI behavior quality | | 8 | **Negotiation** | Resolve through dialogue | Exploring faction relations, role-playing | Obvious answer -> Assign a cost to every choice | | 9 | **Delivery** | Carry goods/information | World traversal, NPC network | Simple travel -> Insert events during travel | ### Variant/Composite Category | # | Archetype | Core Loop | Narrative Function | Risk Factor | |---|-----------|-----------|-------------------|-------------| | 10 | **Infiltration** | Achieve objective undetected | Tension, alternative play style | Detection=failure prohibited -> Switch to combat on detection | | 11 | **Competition** | Compete against NPCs/players | Achievement, social comparison | Unfairness -> Visual progress indicators | | 12 | **Dilemma** | Irreconcilable choices | Moral weight, player identity | Correct answer exists -> Ensure every choice has pros and cons | ## Quest Structure Design: 3-Layer Architecture ``` [Surface Layer] What the player sees: "The village elder asks you to find herbs" [Mechanical Layer] What the game tracks: Travel -> Collect -> Combat -> Return + Flag changes [Narrative Layer] What the story conveys: The elder's hidden past, the true purpose of the herbs ``` ### Surface Layer Design Rules - The objective must be **immediately understandable** — "What do I need to do?" is grasped within 3 seconds - There must be **2 or more paths** to the objective — combat/stealth/persuasion - **Progress** must be visible — 0/5 -> 3/5 -> Complete ### Mechanical Layer Design Rules - Quest steps should be **3-7 stages** (under 3: too simple, over 7: fatigue) - Each step should utilize **different game mechanics** — combat -> dialogue -> exploration variations - Define **failure states** — What happens on failure? (Retry/Branch/Permanent consequence) ### Narrative Layer Design Rules - After completing a quest, the player should learn **at least 1 new thing** about the world - NPC requests have **hidden motivations** — the surface reason and the real reason - Quest outcomes should **affect subsequent quests** — no isolated quests ## Reward Psychology: DRIP Model | Element | Description | Application | |---------|-------------|-------------| | **D**elayed | Delayed rewards — non-immediate rewards | Main quest rewards come at chapter end | | **R**andom | Random rewards — variable ratio reinforcement | Loot probability systems | | **I**ntrinsic | Intrinsic rewards — story, character growth | Emotional cutscenes, relationship changes | | **P**rogressive | Progressive rewards — cumulative achievement | Achievements, titles, skill trees | ### Reward Balance Formula ``` Quest Reward Value = (Time Required x Base Reward Rate) x Difficulty Coefficient x Choice Bonus - Base Reward Rate: Baseline experience/gold per minute - Difficulty Coefficient: Easy(0.8), Normal(1.0), Hard(1.5), Hidden(2.0) - Choice Bonus: 1.2x-1.5x for completing bonus objectives/moral choices ``` ## Difficulty Curve Design ### Ideal Difficulty Curve: Sawtooth Pattern ``` Difficulty ^ | /\ /\ /\ | / \ / \ / \ | / \ / \ / \ <- Each tooth = quest chain | / \/ \ / \ |/ \/ \ +----------------------------> Progress ``` - Each tooth's **peak**: Boss battle or key branching point - Each tooth's **valley**: Recovery quests, story development, exploration - **Overall slope**: Gradual increase — Chapter 1's highest difficulty < Chapter 3's lowest difficulty ### Main vs. Side Quest Placement | Progress | Main Quest | Side Quest Role | |----------|-----------|-----------------| | 0-20% | Tutorial + World introduction | Basic mechanics learning | | 20-40% | First crisis | Adding depth to factions/characters | | 40-60% | Twist + New objective | Discovering hidden narratives | | 60-80% | Final preparation | Securing key items/alliances | | 80-100% | Climax + Ending | Epilogue, hidden content | ## Quest Document Template ``` ### Quest: [Title] - **ID**: Q_[Chapter]_[Number] - **Type**: Main / Side / Hidden - **Archetype**: [Choose from the 12 archetypes] - **Prerequisite Quest**: Q_XX_XX - **Recommended Level**: Lv.XX #### Overview [1-2 sentence summary] #### Trigger Conditions [Quest start conditions] #### Steps 1. [Action] — [Game Mechanic] — [Narrative Function] 2. ... #### Branches - Choice A: [Result] -> [Subsequent impact] - Choice B: [Result] -> [Subsequent impact] #### Rewards - Experience: X / Gold: X / Item: [Name] - Narrative Reward: [Relationship changes, new information] #### Flag Changes - SET: [flag_name] = [value] ```
Related Skills
knowledge-base-design
Knowledge base design guide. Referenced by faq-builder and manual-writer agents when systematically organizing FAQs and troubleshooting guides. Used for 'FAQ design', 'knowledge management', 'troubleshooting guide' requests. Note: wiki system implementation is out of scope.
learning-path-design
Learning path design framework. Referenced by training-builder and onboarding-architect agents when designing new hire learning curricula. Used for 'learning path', 'curriculum design', 'training program' requests. Note: LMS system development and e-learning content production are out of scope.
risk-response-patterns
risk response strategy pattern library. response-strategist and monitoring-planner agent risk response plan establishto do when reference. 'risk response', 'mitigation strategy', 'response plan' request when usage. However, insurance design legal risk specialistdocument scope outside.
rhetoric-patterns
numbercompany pattern library. speech-writer and debate-preparer agent persuasioncapability speech and buildingto do when reference. 'numbercompany', ' structure', 'persuasion technique' request when usage. However, actual presentation nature training scope outside.
checklist-design
checklist design principle. checklist-designer agent execution inspectiontable and quality designto do when reference. 'checklist design', 'quality ', 'inspectiontable writing' request when usage. However, checklist development specialist whensystem building scope outside.
kpi-dashboard-patterns
KPI dashboard design pattern. analyst agent core indicator analysisand executive-summarizer management reporting dashboard compositionto do when reference. 'KPI analysis', 'dashboard design', ' indicator' request when usage. However, actualtime BI whensystem building scope outside.
diagram-patterns
Mermaid diagram pattern library. diagram-maker agent technical document diagram writingto do when reference verifydone pattern . 'diagram pattern', 'Mermaid template', ' diagram pattern' request when usage. However, actual un-degree specialistperson tool work scope outside.
code-example-patterns
technical document code example pattern library. doc-writer agent code example, writingto do when reference. 'code example pattern', ' code writing' request when usage. However, actual code file test execution scope outside.
claim-drafting-patterns
Strategic drafting patterns and claim scope design guide for patent claims. The 'claim-drafter' and 'patent-reviewer' agents must use this skill's drafting patterns, terminology rules, and dependent claim strategies when writing or verifying claims. Used for 'claim drafting', 'claim scope design', 'dependent claim strategy', etc. Note: Overall patent orchestration or prior art search is outside the scope of this skill.
design-system
Full pipeline for systematically building a UI design system. An agent team collaborates to create design tokens, React/Vue component libraries, Storybook, WCAG accessibility verification, and documentation. Use this skill for requests like 'build a design system', 'component library', 'UI kit', 'design tokens', 'Storybook setup', 'accessibility verification', 'WCAG verification', 'UI components', 'create a button component', etc. Note: Figma plugin development, design system SaaS construction, and native app components (SwiftUI/Jetpack Compose) are outside the scope of this skill.
sdk-design-patterns
SDK/API client design patterns: builder pattern, interceptor chain, retry strategy, type-safe design, error handling, and pagination wrapper guide. Use this skill for requests involving 'SDK design', 'client patterns', 'retry strategy', 'interceptor', 'builder pattern', 'SDK error handling', 'type safety', 'SDK architecture', etc. Enhances sdk-developer's SDK design capabilities. Note: API spec parsing, test authoring, and documentation are outside the scope of this skill.
openapi-spec-patterns
OpenAPI 3.x spec analysis patterns, schema normalization, authentication method mapping, pagination/error pattern extraction, and GraphQL/gRPC spec interpretation guide. Use this skill for requests involving 'OpenAPI', 'Swagger', 'spec analysis', 'schema normalization', 'API authentication', 'pagination patterns', 'GraphQL schema', 'gRPC proto', etc. Enhances spec-parser's spec analysis capabilities. Note: SDK code generation and test authoring are outside the scope of this skill.