AgentSkillsCN

juicer

为Wojak.ink游戏打造从研究到落地的全流程优化方案。捕捉新游戏体验中的关键洞见,更新主作战手册,并追踪15款游戏的实施进展。 **触发指令:** - “/juicer”命令 - “将此加入果汁作战手册” - “新增果汁学习” - “更新果汁文档” - “传播果汁变更” - “哪些游戏需要果汁更新?”

SKILL.md
--- frontmatter
name: juicer
description: |
  Juice research-to-implementation pipeline for Wojak.ink games. Captures new game feel learnings, updates the master playbook, and tracks implementation across all 15 games.

  **TRIGGERS:**
  - "/juicer" command
  - "Add this to the juice playbook"
  - "New juice learning"
  - "Update juice documentation"
  - "Propagate juice changes"
  - "What games need juice updates?"

Juicer - Juice Knowledge Pipeline

A workflow for capturing game feel research and systematically implementing it across all Wojak.ink games.

Workflow Overview

code
┌─────────────────┐     ┌──────────────────┐     ┌─────────────────┐
│  New Learning   │ ──▶ │  Master Playbook │ ──▶ │  Game Updates   │
│  (research)     │     │  (single source) │     │  (15 games)     │
└─────────────────┘     └──────────────────┘     └─────────────────┘

Commands

CommandAction
/juicer addAdd new learning to playbook
/juicer statusShow implementation status across games
/juicer propagateUpdate game guides from playbook
/juicer reviewReview recent additions for quality

Workflow 1: Add New Learning

When user shares new juice research (from conversation, article, video, etc.):

Step 1: Categorize the Learning

Identify which playbook section it belongs to:

  • Sound Design
  • Haptic Feedback
  • Visual Juice (particles, animations)
  • Screen Effects (shake, flash, vignette)
  • Combo/Streak Systems
  • Death Sequences
  • Near-Miss Feedback
  • Time Dilation
  • Camera Effects
  • Mobile Considerations
  • New section needed?

Step 2: Format the Learning

markdown
### [Learning Title]

**Source:** [Where this came from - conversation, article, game reference]
**Date Added:** [YYYY-MM-DD]
**Priority:** [P0-P2]

**The Pattern:**
[Concise description of the technique]

**Implementation:**
```typescript
// Code example

When to Use:

  • [Context 1]
  • [Context 2]

Games to Update: [List affected games or "All"]

code

### Step 3: Add to Playbook
1. Read `docs/game-juice-playbook.md`
2. Find appropriate section
3. Add formatted learning
4. Update "Last Updated" date in header

### Step 4: Update Tracker
Add entry to `docs/juice-implementation-tracker.md`:
```markdown
| Learning | Date | Playbook | FO | BP | CD | OS | BB | WW | OS | MM | OP | WR | OJ | KG |
|----------|------|----------|----|----|----|----|----|----|----|----|----|----|----|----|
| [Name]   | Date | ✅       | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ | ⏳ |

Legend: ✅ Done | ⏳ Pending | ➖ N/A | 🔄 In Progress


Workflow 2: Check Status

Show implementation progress across all games:

Read Tracker

bash
# Read the tracker file
cat docs/juice-implementation-tracker.md

Generate Status Report

code
## Juice Implementation Status

### Recent Additions (Last 30 Days)
- [Learning 1]: 3/12 games updated
- [Learning 2]: 12/12 games updated ✅

### Games Needing Updates
| Game | Pending Items |
|------|---------------|
| FlappyOrange | 0 (fully juiced) |
| BlockPuzzle | 2 pending |
| CitrusDrop | 3 pending |
...

### Priority Queue
1. [P0] Death shake on BlockPuzzle
2. [P1] Near-miss sound on CitrusDrop
3. [P2] Combo escalation on OrangeSnake

Workflow 3: Propagate to Games

Update game-specific implementation guides from master playbook:

Game Implementation Guides

GameGuide Location
FlappyOrangedocs/FLAPPY-ORANGE-JUICE-IMPLEMENTATION.md
BlockPuzzledocs/games/block-puzzle-juice.md
CitrusDropdocs/games/citrus-drop-juice.md
OrangeSnakedocs/games/orange-snake-juice.md
BrickBreakerdocs/games/brick-breaker-juice.md
WojakWhackdocs/games/wojak-whack-juice.md
OrangeStackdocs/games/orange-stack-juice.md
MemoryMatchdocs/games/memory-match-juice.md
OrangePongdocs/games/orange-pong-juice.md
WojakRunnerdocs/games/wojak-runner-juice.md
OrangeJuggledocs/games/orange-juggle-juice.md
KnifeGamedocs/games/knife-game-juice.md

Propagation Steps

  1. Read new learning from playbook
  2. For each applicable game:
    • Read game's juice guide
    • Add game-specific implementation notes
    • Mark as 🔄 in tracker
  3. After code implementation:
    • Mark as ✅ in tracker

Workflow 4: Review Quality

Periodically review playbook for:

Checklist

  • No duplicate patterns across sections
  • All code examples are tested
  • Priority levels are accurate
  • Outdated patterns marked or removed
  • Cross-references are valid
  • Implementation tracker is current

Files Managed by Juicer

FilePurpose
docs/game-juice-playbook.mdMaster playbook (single source of truth)
docs/juice-implementation-tracker.mdProgress across all games
docs/FLAPPY-ORANGE-JUICE-IMPLEMENTATION.mdFlappy Orange specific guide
docs/games/*-juice.mdOther game-specific guides
src/lib/juice/Reusable code libraries

Quick Add Template

For fast capture during conversation:

markdown
## Quick Juice Note

**What:** [Brief description]
**Why it works:** [Psychology/feel reason]
**Code hint:** [Rough implementation idea]
**Priority:** P0/P1/P2
**Applies to:** [Games or "All"]

---
To be formatted and added to playbook later.