Game Design Novelty Spectrum Audit

SKILL.md

---
name: game-design-novelty-spectrum-audit
description: Evaluate a game design, feature proposal, system concept, pitch, or prototype on the novelty spectrum between too familiar and too novel. Use when assessing whether a concept has enough differentiation, whether it violates player expectations too strongly, how it balances familiarity and innovation, or whether its innovation pattern is best understood as incremental innovation, recombination, simplification, or a more radical break from established mental models.
---

# Game Design Novelty Spectrum Audit

Evaluate whether a design is innovating in the right way, at the right intensity, for the right audience.

Use this skill to assess how a proposal sits on the spectrum between overly familiar and overly novel. The goal is not to praise originality for its own sake. The goal is to judge whether the design balances novelty against player expectations strongly enough to feel fresh, but not so aggressively that it creates avoidable cognitive dissonance or adoption risk.

Read `references/mental-model-layers.md` when identifying which player expectations matter most.
Read `references/innovation-patterns.md` when classifying what kind of novelty the design is attempting.
Read `references/verdict-scale.md` when selecting a final novelty-spectrum judgment.

## What to produce

Produce:
1. **Concept read** - what the design is trying to be
2. **Familiarity anchors** - what players will immediately recognize
3. **Novel elements** - what is genuinely different
4. **Innovation pattern** - what kind of innovation is happening
5. **Novelty spectrum verdict** - where the design sits between too familiar and too novel
6. **Expectation clashes** - where player mental models may resist the design
7. **Adjustment recommendation** - what to increase, reduce, simplify, or communicate differently

## Process

### 1. Read the concept through the lens of player expectations
Clarify:
- what the proposal is trying to offer players
- what audience it seems to target
- what genre, fantasy, or product context frames player expectations
- whether the pitch is leaning on familiarity, novelty, or both

### 2. Identify the familiarity anchors
Look for the parts of the concept that already fit player mental models.
These may include:
- recognizable fantasy or setting
- familiar control patterns
- established genre loops
- common progression structures
- known PvP, PvE, crafting, deckbuilding, roguelite, or battle-pass conventions
- franchise or brand expectations

### 3. Identify the novelty sources
Ask what is actually new here.
Distinguish between:
- cosmetic novelty
- thematic novelty
- interaction novelty
- systemic novelty
- social/meta novelty
- packaging or framing novelty

Do not mistake polish, setting swap, or tone shift for deep innovation unless it really changes player experience.

### 4. Classify the innovation pattern
Use one or more of these patterns:
- **Incremental innovation** - improving an existing design lineage
- **Recombination** - combining established elements from different sources
- **Simplification** - removing complexity to create a more accessible or elegant version
- **Radical break** - departing sharply from established expectations

Prefer the dominant pattern rather than force every category at once.

### 5. Judge the novelty balance
Decide whether the design is:
- too derivative to stand out
- familiar but differentiated enough
- balanced well between old and new
- exciting but risky
- likely too novel for the target audience or context

### 6. Surface expectation collisions
Identify where mental models may reject the concept.
Common clashes include:
- genre expectations violated without support
- controls or interactions that feel wrong before they feel interesting
- fantasy promise undermined by unfamiliar systems
- too many unfamiliar layers stacked at once
- innovations that demand learning before the player cares enough to learn

### 7. Recommend adjustment
Suggest the strongest next move, such as:
- add one stronger novelty hook
- reduce novelty load in one layer
- anchor the idea harder in familiar structures
- simplify the innovation
- communicate the novelty better in onboarding or marketing
- prototype the riskiest novelty first

## Response structure

### Concept Read
- ...

### Familiarity Anchors
- ...

### Novel Elements
- ...

### Innovation Pattern
- ...

### Novelty Spectrum Verdict
- ...

### Where Player Expectations May Clash
- ...

### Recommended Adjustment
- ...

## Fast mode
- What will players instantly recognize?
- What is actually new here?
- Is the novelty mostly incremental, recombinational, simplifying, or radical?
- Is the design too safe, well balanced, or too dissonant?
- What one adjustment would improve its novelty balance most?

## Style rules
- Do not worship novelty.
- Do not assume familiarity is automatically safe.
- Distinguish clearly between deep innovation and surface differentiation.
- Tie judgments to player expectations, not abstract design taste.
- If the concept is strong but risky, say where the risk sits.
- If the concept is too derivative, say why players may not care enough.

## Working principle

Good innovation in games is rarely pure invention.
It usually succeeds by balancing what players already understand with what feels meaningfully fresh.