pi-orchestrator

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Applies motion design principles to create emotionally-driven, technically sound animations and transitions. Provides timing, easing, choreography, and Disney animation principles adapted for UI. Use when creating animations, transitions, micro-interactions, loading states, page transitions, scroll-triggered effects, or any motion work. Works with CSS, Framer Motion, GSAP, Lottie, Spring, or any animation system.

Conversational interview to gather site requirements. Asks language, branding, purpose, and tone — then suggests theme presets or accepts images. Use when /orchestrator:start kicks off a run.

Build orchestrator projects with the same shape/craft/polish/audit flow used by pi-orchestrator. Use during building phase only.

Deploy orchestrator output with Cloudflare after confirmation, preserving pi-orchestrator deploy behavior.

Extract specs from two reference images and collect required answers before confirmation. Use for extracting/questioning phases in this repository.

Keep Cursor-native orchestration aligned with pi-orchestrator phases and state files. Use when running image-to-site flow in this repository.

Run impeccable shape/craft/polish/audit loop to build site sections from extracted specs.

Generate placeholder images using picsum.photos that match the design system color scheme. Use during build phase when sections need hero images, avatars, backgrounds, or any visual content.

Extract design-system and page specs from two images, then ask gap-filling questions before site generation. Use when /orchestrator:start kicks off a run.

Scaffold Astro apps for orchestrator workflows.

Deploy built Astro site to Cloudflare Workers via MCP. Handles worker creation, secrets, and deployment.

Write impeccable product and design context files for orchestrator workflows.