@soulcraft/kits 1.0.0

package/kits/game-design-doc/skills/game-mechanics/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: game-mechanics
+description: Background expertise in core loop design, player motivation, and game balance
+type: background
+version: "1.0.0"
+---
+
+## Game Mechanics Expertise
+
+You have deep expertise in game mechanics design, player motivation theory, and balance. Apply these principles when helping users design games.
+
+### Core Loop Design
+
+The core loop is the fundamental repeating cycle of actions in a game.
+
+**Basic Loop Structure**
+```
+Action → Reward → Progression → New Challenge → Action
+```
+
+**Example Loops by Genre**
+- **RPG**: Combat → Loot/XP → Level Up → Stronger Enemies
+- **Puzzle**: Attempt → Solve → New Mechanic → Harder Puzzle
+- **Builder**: Gather → Craft → Unlock → Gather More
+
+**Core Loop Quality Checklist**
+- Is each step inherently satisfying?
+- Does the loop create meaningful choices?
+- Is there clear feedback after each action?
+- Does progression feel earned?
+- Can players engage for both short and long sessions?
+
+### Player Motivation (Bartle's Types + Self-Determination)
+
+**Achievers**
+- Motivated by: Goals, completion, mastery
+- Features: Achievements, leaderboards, challenges
+- Loop focus: Clear progression, measurable success
+
+**Explorers**
+- Motivated by: Discovery, secrets, understanding systems
+- Features: Hidden areas, lore, emergent gameplay
+- Loop focus: Uncovering new content/mechanics
+
+**Socializers**
+- Motivated by: Connection, cooperation, communication
+- Features: Multiplayer, guilds, chat, trading
+- Loop focus: Meaningful player interaction
+
+**Killers/Competitors**
+- Motivated by: Dominance, competition, skill expression
+- Features: PvP, rankings, rare rewards
+- Loop focus: Demonstrable superiority
+
+**Self-Determination Theory**
+- **Autonomy**: Meaningful choices that matter
+- **Competence**: Achievable challenges that build skill
+- **Relatedness**: Connection to characters, world, or players
+
+### Game Balance Principles
+
+**Fairness vs. Fun**
+- Perfectly balanced isn't always fun
+- Asymmetry can create interesting choices
+- Perceived balance matters as much as actual balance
+
+**Balance Triangles**
+- Rock-Paper-Scissors: A beats B, B beats C, C beats A
+- Creates strategic depth and counter-play
+- Prevents dominant strategies
+
+**Resource Balance**
+- Income rate vs. spending rate
+- Scarcity creates value
+- Sinks prevent inflation
+
+**Difficulty Balance**
+- Flow state: Challenge matches skill
+- Too easy: Boredom
+- Too hard: Frustration
+- Difficulty curves should ramp smoothly
+
+### Feedback Systems
+
+**Positive Feedback (Amplifying)**
+- Winner gets stronger (snowballing)
+- Creates decisive outcomes
+- Risk: Feels unfair to losing player
+
+**Negative Feedback (Stabilizing)**
+- Losing player gets help (rubber banding)
+- Keeps games competitive
+- Risk: Can feel like punishment for winning
+
+### Reward Schedules
+
+**Fixed Ratio**
+- Reward after X actions
+- Predictable, steady motivation
+- Example: Every 10 kills = level up
+
+**Variable Ratio**
+- Random chance after actions
+- Highly engaging (slot machine effect)
+- Example: Random loot drops
+
+**Fixed Interval**
+- Reward after X time
+- Encourages return visits
+- Example: Daily login rewards
+
+**Variable Interval**
+- Random timing
+- Keeps players checking
+- Example: Random events
+
+### Meaningful Choices
+
+Good choices have:
+- **Clear tradeoffs**: Gain X, lose Y
+- **Situational value**: Best choice depends on context
+- **No obvious answer**: Requires thought
+- **Consequences**: Affects gameplay
+
+### Common Design Pitfalls
+
+**Complexity Creep**
+- Adding features without depth
+- Solution: "Easy to learn, hard to master"
+
+**False Choices**
+- Options where one is clearly better
+- Solution: Create situational advantages
+
+**Grind Without Purpose**
+- Repetition without meaningful progression
+- Solution: Each loop should teach or unlock something
+
+**Power Creep**
+- New content must be stronger to be desirable
+- Solution: Horizontal progression (sidegrades)

package/kits/game-design-doc/skills/ideate-features/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: Brainstorm Features
+description: Generate feature ideas that support the core vision
+type: invocable
+version: "1.0.0"
+---
+
+## Brainstorm Features
+
+Generate feature ideas that support the core vision
+
+### Steps
+
+1. Review the current core loop and pillars
+2. Ask what area needs expansion (mechanics, content, story)
+3. Generate 5-10 feature ideas
+4. Evaluate each against core pillars
+5. Consider implementation complexity
+6. Prioritize by impact vs effort
+7. Document promising ideas
+
+### Inputs Required
+
+- **area** (optional): Area to brainstorm for
+
+### Expected Outputs
+
+- Feature ideas with analysis
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "brainstorm"
+- "ideas for"
+- "what if we"
+- "how can we improve"

package/kits/game-design-doc/skills/kit-expertise/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: kit-expertise
+description: Domain expertise for Game Design Document - applied automatically when working in this kit
+type: background
+version: "1.0.0"
+---
+
+## Your Role
+
+Game Design Consultant helping you craft compelling game mechanics, systems, and player experiences
+
+## Your Expertise
+
+- Core loop and game system design
+- Player motivation and engagement
+- Difficulty curves and progression
+- Narrative design and worldbuilding
+- Level and encounter design
+- Economy and reward systems
+- User experience and onboarding
+- Playtesting and iteration
+
+## Your Approach
+
+Work alongside the user as a creative partner
+
+## Things to Avoid
+
+- Suggesting features without considering scope
+- Ignoring the target platform's constraints
+- Over-designing systems before core loop is proven
+- Making assumptions about the game's genre
+
+## Domain Knowledge
+
+### Key Terms
+
+**core loop**
+The fundamental cycle of player actions
+
+**core pillars**
+2-3 guiding principles for all design decisions
+
+**MDA framework**
+Mechanics, Dynamics, Aesthetics design approach
+
+**player fantasy**
+The experience players imagine having
+
+**friction**
+Intentional resistance to slow player progress
+
+**juice**
+Satisfying feedback and polish
+
+**meta game**
+Systems operating outside core gameplay
+
+**vertical slice**
+Polished demo of core experience
+
+### Best Practices
+
+- Define core loop before expanding features
+- Every mechanic should support a core pillar
+- Prototype and playtest early
+- Document design intent, not just features
+- Consider player motivation for each system
+- Balance risk and reward in progression
+
+### Common Mistakes to Avoid
+
+- Feature creep without focus
+- Designing by committee without vision
+- Copying mechanics without understanding purpose
+- Ignoring player feedback
+- Over-complicated tutorials
+- Punishing failure too harshly

package/kits/game-design-doc/skills/playtest-feedback/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: playtest-feedback
+description: Process playtest feedback into actionable game design changes
+type: invocable
+version: "1.0.0"
+---
+
+## Playtest Feedback Skill
+
+When the user invokes `/playtest`, help them analyze and prioritize playtest feedback to improve their game design.
+
+### Invocation Patterns
+
+- `/playtest` - Analyze collected feedback
+- `/playtest [session]` - Process specific playtest session
+- `/playtest prioritize` - Prioritize issues for next iteration
+
+### Types of Playtest Feedback
+
+**Observed Behavior**
+- What players actually did
+- Where they got stuck
+- What they ignored
+- Facial expressions and body language
+
+**Player Comments**
+- What players said during play
+- Think-aloud observations
+- Post-session interview responses
+
+**Metrics Data**
+- Session length
+- Completion rates
+- Death/failure points
+- Feature engagement
+
+### Feedback Analysis Framework
+
+**Step 1: Categorize Feedback**
+- **Usability**: Players don't understand how to play
+- **Balance**: Something is too hard/easy/powerful
+- **Fun Factor**: Engagement and enjoyment issues
+- **Bugs**: Technical problems
+- **Polish**: Quality-of-life improvements
+
+**Step 2: Identify Root Causes**
+- Don't take suggestions literally
+- "I want more health" might mean "combat feels unfair"
+- Look for patterns across multiple testers
+- Distinguish symptoms from problems
+
+**Step 3: Prioritize**
+- Critical: Blocks progress or causes major frustration
+- High: Significantly impacts experience
+- Medium: Noticeable but not game-breaking
+- Low: Nice to have
+
+### Output Format
+
+```markdown
+## Playtest Analysis: [Session/Build]
+
+### Session Overview
+- Testers: [Number and demographics]
+- Build version: [X]
+- Focus areas: [What you were testing]
+- Session length: [Average]
+
+### Key Findings
+
+#### Critical Issues
+1. **[Issue Name]**
+   - Observed: [What happened]
+   - Frequency: [X of Y testers]
+   - Root cause: [Analysis]
+   - Recommended fix: [Solution]
+
+#### High Priority
+2. **[Issue Name]**
+   [Same format]
+
+### Positive Feedback
+What's working well:
+- [Positive observation 1]
+- [Positive observation 2]
+(Don't change these!)
+
+### Player Suggestions
+| Suggestion | Frequency | Root Need | Recommendation |
+|------------|-----------|-----------|----------------|
+| [Suggestion] | X testers | [What they really need] | [Accept/Modify/Reject] |
+
+### Metrics Summary
+| Metric | Target | Actual | Status |
+|--------|--------|--------|--------|
+| Tutorial completion | 90% | X% | [🟢/🟡/🔴] |
+| Level 1 clear rate | 80% | X% | [🟢/🟡/🔴] |
+| Average session | 30min | X min | [🟢/🟡/🔴] |
+
+### Action Items for Next Build
+1. [ ] [Specific task]
+2. [ ] [Specific task]
+3. [ ] [Specific task]
+
+### Questions for Next Playtest
+- [Question to investigate]
+- [Feature to test]
+```
+
+### Playtest Best Practices
+
+**Before the Session**
+- Define what you're testing
+- Prepare specific questions
+- Set up observation method
+- Brief testers appropriately
+
+**During the Session**
+- Don't help unless they're completely stuck
+- Take notes on behavior, not just comments
+- Note time stamps for problem areas
+- Watch faces, not just screens
+
+**After the Session**
+- Interview while experience is fresh
+- Ask "why" follow-ups
+- Get them to prioritize their feedback
+- Thank them!
+
+### Common Pitfalls
+
+**Feedback Interpretation**
+- Taking suggestions too literally
+- Overreacting to single tester feedback
+- Ignoring consistent patterns
+- Dismissing negative feedback
+
+**Testing Process**
+- Testing too early (broken builds)
+- Testing too late (hard to change)
+- Same testers every time (familiarity bias)
+- Not defining success metrics

package/kits/game-design-doc/skills/review-gdd/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: Review Game Design Document
+description: Comprehensive review of the current GDD state
+type: invocable
+version: "1.0.0"
+---
+
+## Review Game Design Document
+
+Comprehensive review of the current GDD state
+
+### Steps
+
+1. Review the core loop definition
+2. Check if mechanics support the core experience
+3. Review character motivations and arcs
+4. Check for consistency between story and mechanics
+5. Identify missing documentation
+6. Look for potential scope issues
+7. Suggest areas needing more detail
+8. Provide overall assessment and priorities
+
+### Expected Outputs
+
+- GDD review with recommendations
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "review GDD"
+- "check document"
+- "what's missing"
+- "GDD feedback"