combat-ui-pattern-a
Implement Split-Panel Combat UI (Pattern A) for SHINOBI WAY game. Use when user wants to create the horizontal confrontation combat layout, character panels, action dock, phase header, VS divider, or any component from the Pattern A combat UI system. Guides through component creation following the established architecture.
What this skill does
# Combat UI Pattern A - Split-Panel Implementation
This skill guides implementation of the Split-Panel Combat UI, transforming the vertical theater mode into a horizontal confrontation layout.
## Architecture Overview
```
┌───────────────────────────────────────────────────┐
│ TURN INDICATOR │ PHASE PIPELINE │ MODIFIERS │ ← PhaseHeader
├──────────────────┴───────┬───────────┴────────────┤
│ │ │
│ PLAYER PANEL │ ENEMY PANEL │ ← ConfrontationZone
│ (CharacterPanel) │ (CharacterPanel) │
│ │ │
├──────────────────────────┴────────────────────────┤
│ QUICK ACTIONS (SIDE/TOGGLE) │ MAIN ACTIONS │ ← ActionDock
└───────────────────────────────┴───────────────────┘
```
## Component Hierarchy
```
Combat.tsx (scene orchestrator)
├── CombatLayout.tsx (CSS Grid container)
│ ├── PhaseHeader.tsx (top status bar)
│ │ ├── TurnIndicator
│ │ ├── PhasePipeline
│ │ ├── SideActionCounter
│ │ └── ApproachModifier
│ │
│ ├── ConfrontationZone.tsx (battle area)
│ │ ├── CharacterPanel.tsx (player variant)
│ │ │ ├── CharacterSprite
│ │ │ ├── IdentityBar
│ │ │ ├── ResourceBars (HP/CP)
│ │ │ └── BuffBar
│ │ │
│ │ ├── VSDivider.tsx (center emblem)
│ │ │
│ │ └── CharacterPanel.tsx (enemy variant)
│ │ ├── CharacterSprite
│ │ ├── IdentityBar (name, tier, element)
│ │ ├── HealthBar
│ │ ├── DefenseStats
│ │ └── BuffBar
│ │
│ └── ActionDock.tsx (skill bar)
│ ├── QuickActionsSection
│ │ ├── QuickActionCard (SIDE skills)
│ │ └── QuickActionCard (TOGGLE skills)
│ ├── MainActionsSection
│ │ └── MainActionCard (MAIN skills)
│ └── ControlButtons (Auto, End Turn)
│
└── FloatingTextLayer (z-50, unchanged)
```
## File Structure
```
src/components/combat/
├── index.ts # Barrel exports
├── CombatLayout.tsx # Grid container
├── PhaseHeader.tsx # Top status bar
├── ConfrontationZone.tsx # Player vs Enemy area
├── CharacterPanel.tsx # Reusable character display
├── VSDivider.tsx # Center VS emblem
├── ActionDock.tsx # Bottom skill bar
├── QuickActionCard.tsx # Compact SIDE/TOGGLE card
└── MainActionCard.tsx # Large MAIN skill card
```
## Implementation Workflow
### Step 1: Identify Target Component
Ask user which component to implement:
1. **CombatLayout** - Start here for new implementation
2. **PhaseHeader** - Top status bar
3. **ConfrontationZone** - Battle area with both panels
4. **CharacterPanel** - Individual character display
5. **VSDivider** - Center emblem and effects
6. **ActionDock** - Bottom skill bar
7. **QuickActionCard** - Compact skill card variant
8. **MainActionCard** - Large skill card variant
### Step 2: Load Component Reference
Based on selection, load the appropriate reference:
- **Layout/Structure**: See [layout-specs.md](references/layout-specs.md)
- **Component Props**: See [component-interfaces.md](references/component-interfaces.md)
- **Styling Guide**: See [styling-tokens.md](references/styling-tokens.md)
- **Animation Specs**: See [animations.md](references/animations.md)
### Step 3: Generate Component Code
Follow the component template pattern:
```typescript
import React from 'react';
import { cn } from '@/lib/utils'; // if using cn utility
interface ComponentNameProps {
// Props from component-interfaces.md
}
export const ComponentName: React.FC<ComponentNameProps> = ({
// destructured props
}) => {
return (
<div className={cn(
// Base styles from styling-tokens.md
// Conditional styles
)}>
{/* Component content */}
</div>
);
};
```
### Step 4: Wire to Combat.tsx
After component creation:
1. Export from `components/combat/index.ts`
2. Import in `Combat.tsx`
3. Replace corresponding section
4. Pass required props from existing state
## Quick Implementation Commands
### Create All Files (Scaffolding)
```bash
# Create directory
mkdir -p src/components/combat
# Create all component files
touch src/components/combat/{index,CombatLayout,PhaseHeader,ConfrontationZone,CharacterPanel,VSDivider,ActionDock,QuickActionCard,MainActionCard}.tsx
```
### Barrel Export Template
```typescript
// src/components/combat/index.ts
export { CombatLayout } from './CombatLayout';
export { PhaseHeader } from './PhaseHeader';
export { ConfrontationZone } from './ConfrontationZone';
export { CharacterPanel } from './CharacterPanel';
export { VSDivider } from './VSDivider';
export { ActionDock } from './ActionDock';
export { QuickActionCard } from './QuickActionCard';
export { MainActionCard } from './MainActionCard';
```
## Props Mapping from Existing Code
### From App.tsx → Combat.tsx (unchanged)
```typescript
player: Player
enemy: Enemy
turnState: 'PLAYER' | 'ENEMY_TURN'
turnPhase: TurnPhaseState
combatState: CombatState
onUseSkill: (skill: Skill) => void
onPassTurn: () => void
onToggleAutoCombat: () => void
autoCombatEnabled: boolean
```
### Combat.tsx → New Components
```typescript
// PhaseHeader
turnState, turnPhase, combatState.approach
// ConfrontationZone
player, enemy, playerStats, enemyStats
// CharacterPanel (player)
character: player, stats: playerStats, variant: 'player'
// CharacterPanel (enemy)
character: enemy, stats: enemyStats, variant: 'enemy'
// ActionDock
skills: player.skills, turnPhase, onUseSkill, onPassTurn
```
## Migration Strategy
### Phase 1: Layout Foundation
1. Create `CombatLayout.tsx` with CSS Grid
2. Create placeholder components
3. Add feature flag in Combat.tsx
### Phase 2: Component Extraction
4. Implement `CharacterPanel` (extract from PlayerHUD + CinematicViewscreen)
5. Implement `ActionDock` (extract from skill grids)
6. Implement `PhaseHeader` (extract from inline indicators)
### Phase 3: Visual Polish
7. Add `VSDivider` with effects
8. Implement animations
9. Adjust floating text positions
### Phase 4: Cleanup
10. Remove old theater mode code
11. Remove feature flag
12. Update tests
## Reference Files
- [layout-specs.md](references/layout-specs.md) - CSS Grid structure, responsive breakpoints
- [component-interfaces.md](references/component-interfaces.md) - TypeScript interfaces for all components
- [styling-tokens.md](references/styling-tokens.md) - Colors, spacing, typography tokens
- [animations.md](references/animations.md) - Animation keyframes and transitions
## Output Format
Generate TypeScript React components with:
1. **TypeScript interface** for props
2. **Tailwind CSS** for styling (matching existing codebase)
3. **Responsive classes** (mobile fallback to vertical)
4. **Memoization** where appropriate (React.memo for cards)
5. **Accessibility** attributes (aria-labels, roles)
## Existing Code References
When implementing, reference these existing files:
| New Component | Reference From |
|---------------|----------------|
| CharacterPanel (player) | `src/components/PlayerHUD.tsx` |
| CharacterPanel (enemy) | `src/scenes/Combat.tsx` lines 113-305 |
| ActionDock | `src/scenes/Combat.tsx` lines 308-607 |
| QuickActionCard | `src/components/SkillCard.tsx` |
| MainActionCard | `src/components/SkillCard.tsx` |
| PhaseHeader | `src/scenes/Combat.tsx` lines 311-328 |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.