Panel Patterns

Panel Patterns Skill

Pre-defined panel patterns and best practices for creating atmospheric info panels in adventures. Panels are markdown files with YAML frontmatter.

Panel File Format

Panels are stored at {playerRef}/panels/{id}.md:

---
title: Weather Status    # Display header (1-64 chars)
position: sidebar        # sidebar | header | overlay
priority: medium         # low | medium | high (default: medium)
---
Panel content in markdown...

Operations: Create = Write file. Update = Overwrite file. Delete = rm file. Limits: 2 sidebar, 2 header, 1 overlay. Higher priority displays first.

Quick Reference

Universal Patterns

These patterns work across all genres and RPG systems.

Weather & Environment (sidebar)

When to create: Weather becomes mechanically relevant (affects visibility, movement, damage, or skill checks)

File: panels/weather.md

---
title: Current Conditions
position: sidebar
priority: medium
---
**Heavy Rain**
- Visibility: 60ft
- Ranged attacks: Disadvantage
- Perception (sight): -5 penalty

Update triggers: Weather worsens/improves, mechanical effects change Dismiss trigger: Weather becomes narratively irrelevant - delete the file

Status Alerts (header)

When to create: Character enters dangerous state (HP < 25%, death saves, critical conditions)

File: panels/status-alert.md

---
title: WARNING
position: header
priority: high
---
**CRITICAL** - 8/42 HP - Poisoned (3 rounds remaining)

Update triggers: HP changes, condition worsens/improves, save results Dismiss trigger: Character healed above threshold - delete the file

Timers & Countdowns (header)

When to create: Time pressure exists (ritual completion, event countdown, limited-time decision)

File: panels/timer.md

---
title: COUNTDOWN
position: header
priority: high
---
**Ritual Completes in 3 Rounds** - Portal stabilizing... Stop it now or too late!

Update triggers: Time passes (each round, turn, day), deadline extended/shortened Dismiss trigger: Timer expires - delete the file

Resource Tracking (sidebar)

When to create: Limited resource becomes tactically important (ammunition, spell slots, inventory weight, rations)

Pattern:

• ID: resources
• Position: sidebar
• Persistent: true (ongoing tracking)
• Content structure: Resource name, current/max, visual indicator if helpful

Examples:

**Resources**
- Arrows: 12/20
- Torches: 3 (4 hrs light each)
- Rations: 6 days
- Waterskins: Full (2/2)

**Spell Slots**
1st: 3/4
2nd: 2/3
3rd: 1/2

Update triggers: Resource consumed, resource restored (loot, rest, purchase) Dismiss trigger: Resources no longer scarce, tracking no longer relevant

Critical Choice (overlay)

When to create: Major decision point requiring player focus - moral dilemmas, branching paths, irreversible actions

Pattern:

• ID: critical-choice
• Position: overlay (demands attention, blocks other interaction)
• Persistent: false (dismiss after decision)
• Content structure: Situation summary, clear options with consequences hinted

Example:

**The Ritual Chamber**

The cultist holds a knife to the prisoner's throat. The portal behind him crackles with energy.

**Your options:**
- Attack the cultist (risk the prisoner)
- Negotiate (portal continues charging)
- Target the portal (cultist completes sacrifice)
- Something else?

*What do you do?*

Update triggers: New information revealed, situation changes Dismiss trigger: Player makes decision, situation resolves

Game State Patterns

Patterns triggered by specific game mechanical states.

Combat - Initiative Tracker (sidebar)

When to create: Combat begins and turn order matters

Pattern:

• ID: initiative
• Position: sidebar
• Persistent: false (combat-only)
• Content structure: Round number, initiative order with HP, current turn indicator, conditions

Example:

**Combat - Round 2**

> Kael (Init 18) - 24/32 HP - Shield of Faith
  Goblin 1 (Init 14) - DEAD
  Mira (Init 10) - 28/28 HP
  Goblin 2 (Init 8) - 6/12 HP - Prone
  Ogre (Init 5) - 45/59 HP - Raging

Update triggers: Turn advances, HP changes, conditions applied/removed, combatants join/die Dismiss trigger: Combat ends (all enemies defeated/fled, party flees, parley reached)

Social - Faction Standing (sidebar)

When to create: Party reputation with factions affects available options

Pattern:

• ID: factions
• Position: sidebar
• Persistent: true (ongoing political state)
• Content structure: Faction names, standing levels, recent changes, consequences

Example:

**Faction Relations**
- **Merchant Guild**: Honored (+3) [up]
  10% discount, guild hall access
- **City Guard**: Neutral (0)
- **Thieves Guild**: Hostile (-2) [down]
  Prices doubled, ambush risk

Update triggers: Party action affects faction, quest completed, time passes (reputation decays) Dismiss trigger: Factions become irrelevant to current story

Exploration - Discovery Log (sidebar)

When to create: Exploration-focused session where discoveries should be tracked

Pattern:

• ID: discoveries
• Position: sidebar
• Persistent: false (session-specific)
• Content structure: Recent discoveries, lore fragments, map updates

Example:

**Today's Discoveries**
- Ancient mural depicting ritual sacrifice
- 3 rooms mapped (see locations.md)
- Lore: "The Crimson King sleeps beneath"
- Treasure: 300gp, Ring of Protection +1
- NPC: Met ghost of Archmage Theron

Update triggers: Party discovers something notable, session time passes Dismiss trigger: Session ends, list becomes too long (archive to state files)

Additional Patterns

For more specialized patterns, see:

• Location Patterns - Tavern gossip, wilderness travel, dungeon exploration, city news
• Genre Patterns - High fantasy, cyberpunk, space opera, horror, survival

Best Practices

When to Create Panels

DO create panels when:

• Information is mechanically relevant (affects rolls, decisions, resources)
• Atmospheric enhancement matters (mood, genre reinforcement)
• Tracking is needed across multiple turns/scenes
• Player needs constant reminder of time pressure or danger
• Context would otherwise be repeated in narrative

DON'T create panels when:

• Information is one-time/transient (can be narrated once)
• Player action immediately resolves the situation
• Already at 5-panel limit (dismiss something first)
• Information is better revealed gradually in narrative
• Panel would spoil upcoming twist or surprise

When to Update vs Create

• Content changes but context remains (weather worsens, HP drops, timer ticks) - Update
• Mechanical effects shift (hazard intensifies, resources consumed) - Update
• New information relevant to existing panel (gossip updates, news breaks) - Update

Don't create duplicate panels - check existing files with Glob first and update existing.

When to Dismiss Panels

• Information no longer relevant (weather clears, combat ends, left location)
• Player situation resolves (healed, danger passed, timer expired)
• Panel space needed for higher priority (at 5-panel limit)
• Story moved on and panel is stale

Dismiss proactively - don't leave stale panels cluttering the UI.

Content Guidelines

• Keep it concise: 2KB limit, but aim for <500 characters for readability
• Use visual hierarchy: Headers, bullets, spacing
• Make it scannable: Key info upfront, details after
• Update don't duplicate: Same ID for related information
• Be consistent: Similar panels should have similar format

Position Selection

Using This Skill

This skill is for inspiration and reference when creating panels. Panels are managed via file operations:

Create panel: Write a markdown file to {playerRef}/panels/{id}.md with YAML frontmatter Update panel: Overwrite the file with new content Delete panel: Remove the file (rm or write empty) List panels: Use Glob/Read to check {playerRef}/panels/*.md

Workflow:

1. Recognize scenario that would benefit from a panel
2. Consult this skill for pattern ideas matching the context
3. Adapt pattern to current situation (customize content, adjust to genre)
4. Check existing panels with Glob to avoid duplicates
5. Write the panel file with proper frontmatter
6. Overwrite the file as story progresses
7. Delete the file when no longer relevant

Remember: These are suggestions, not requirements. Use judgment for what enhances the experience.