skills/cesaraugustusgrob/combat-ui-pattern-a/SKILL.md
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.
npx skillsauth add aiskillstore/marketplace combat-ui-pattern-aInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill guides implementation of the Split-Panel Combat UI, transforming the vertical theater mode into a horizontal confrontation layout.
┌───────────────────────────────────────────────────┐
│ TURN INDICATOR │ PHASE PIPELINE │ MODIFIERS │ ← PhaseHeader
├──────────────────┴───────┬───────────┴────────────┤
│ │ │
│ PLAYER PANEL │ ENEMY PANEL │ ← ConfrontationZone
│ (CharacterPanel) │ (CharacterPanel) │
│ │ │
├──────────────────────────┴────────────────────────┤
│ QUICK ACTIONS (SIDE/TOGGLE) │ MAIN ACTIONS │ ← ActionDock
└───────────────────────────────┴───────────────────┘
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)
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
Ask user which component to implement:
Based on selection, load the appropriate reference:
Follow the component template pattern:
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>
);
};
After component creation:
components/combat/index.tsCombat.tsx# 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
// 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';
player: Player
enemy: Enemy
turnState: 'PLAYER' | 'ENEMY_TURN'
turnPhase: TurnPhaseState
combatState: CombatState
onUseSkill: (skill: Skill) => void
onPassTurn: () => void
onToggleAutoCombat: () => void
autoCombatEnabled: boolean
// 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
CombatLayout.tsx with CSS GridCharacterPanel (extract from PlayerHUD + CinematicViewscreen)ActionDock (extract from skill grids)PhaseHeader (extract from inline indicators)VSDivider with effectsGenerate TypeScript React components with:
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 |
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.