DevSkyy

Have two genuinely different models (a Claude model, e.g. Fable, and Codex/OpenAI) debate a plan before anything gets built — one drafts, the other challenges, capped at 3 rounds, then the strongest coding model actually executes the converged plan and the planner reviews the real result. Use for any task where a wrong plan is expensive to discover late (rigging/animation work, architecture decisions, migrations) — not for small, obviously-correct changes.

Have two genuinely different models (a Claude model, e.g. Fable, and Codex/OpenAI) debate a plan before anything gets built — one drafts, the other challenges, capped at 3 rounds, then the strongest coding model actually executes the converged plan and the planner reviews the real result. Use for any task where a wrong plan is expensive to discover late (rigging/animation work, architecture decisions, migrations) — not for small, obviously-correct changes.

Specialized architect for building augmented reality, 3D, and immersive shopping experiences — across ANY output format (React JSX, standalone HTML/CSS/JS, WordPress/WooCommerce PHP, Python backends, or any other language). Use this skill whenever the user mentions: 3D product viewers, virtual try-on, AR fitting rooms, immersive brand showrooms, 3D collection environments, interactive drop pages, Three.js, React Three Fiber, A-Frame, model-viewer, WebXR, GSAP cinematic scroll, Lottie animations, spatial UI, parallax 3D scenes, or any request to make shopping feel like an experience rather than a webpage. Always use this skill even if the request seems simple — immersive experiences require specialized architecture that generic frontend patterns cannot match. This skill extends frontend-design with deep 3D and AR expertise; load frontend-design alongside it for complete visual design guidance.

Luxury streetwear design taste for SkyyRose surfaces — visual hierarchy, restraint, materials, motion, and imagery treatment. Use for any visual design, review, or elevation work on skyyrose.co or the DevSkyy dashboard. Replaces the lost high-end-visual-design / design-taste-frontend / image-taste-frontend skills.

The SkyyRose flagship theme's own engineering doctrine (wordpress-theme/skyyrose-flagship/) -- not a generic WordPress reference, a stack-specific one built around this brand's actual collections, visual canon, and production pipeline. Covers block/template development, WooCommerce integration, the vanilla three.js mascot and immersive worlds, and the quality gates that keep a luxury storefront feeling luxury. Use for any task touching the theme's PHP, the .min build pipeline, WooCommerce REST/webhooks, or the site's Three.js scenes.

Automate WordPress and WooCommerce operations via REST API. Use when managing products, orders, content, or site configuration programmatically. Triggers on requests to create/update products, manage inventory, generate Elementor layouts, handle WooCommerce orders, or automate any WordPress operations. Includes Elementor JSON generation patterns for skyyrose.co.

Specialized architect for building augmented reality, 3D, and immersive shopping experiences — across ANY output format (React JSX, standalone HTML/CSS/JS, WordPress/WooCommerce PHP, Python backends, or any other language). Use this skill whenever the user mentions: 3D product viewers, virtual try-on, AR fitting rooms, immersive brand showrooms, 3D collection environments, interactive drop pages, Three.js, React Three Fiber, A-Frame, model-viewer, WebXR, GSAP cinematic scroll, Lottie animations, spatial UI, parallax 3D scenes, or any request to make shopping feel like an experience rather than a webpage. Always use this skill even if the request seems simple — immersive experiences require specialized architecture that generic frontend patterns cannot match. This skill extends frontend-design with deep 3D and AR expertise; load frontend-design alongside it for complete visual design guidance.

Five-agent design-elevation pipeline for luxury HTML mockups. Audits a design-reference HTML file against brand canon, identifies polish gaps, generates a fix manifest, executes infrastructure changes via Senior Developer, and verifies the result. Use when refining a design mockup from "decent" to "production-grade luxury". Trigger phrases: "elevate this mockup", "luxury polish pass", "5-agent design pipeline", "/luxury-mockup-pipeline".

Brand identity guide for SkyyRose luxury streetwear. Use when creating content, designs, marketing materials, product descriptions, or any creative work for SkyyRose. Triggers on references to SkyyRose, the collections (Black Rose, Love Hurts, Signature, Kids Capsule), Oakland streetwear, luxury fashion content, or requests for brand-aligned outputs. Essential for maintaining brand consistency across all touchpoints.

Index hub for the SkyyRose social media branch — routes to 27 specialized social skills (content formats, strategy, community, influencer/PR, visual briefs) and the Elite Studio social venture. Use to find the right SkyyRose social skill, or for the at-a-glance brand-voice quick reference.

Full creator-program lifecycle for SkyyRose — from discovery profiling and personalized outreach (DM <150 words + email with subject) through a 3-touch follow-up sequence (day 0 / day 5 / day 15, hard stop), compensation tiers (nano gifting+affiliate through macro flat+usage), collab agreement outline, campaign brief, content approval workflow (max 2 rounds / 48 h turnaround), performance tracking (unique code + UTM), post-campaign analytics (day-7 screenshot), and anti-pattern recovery. Trigger phrases: influencer program, creator partnership, outreach, collab brief, ambassador, gifting, creator tier, FTC, influencer campaign, creator program, partnership pitch, DM pitch, micro-influencer, nano-influencer, mid-tier, macro, affiliate code, collab agreement, campaign brief, go-live, approval workflow, post-campaign analytics, Oakland creator, Bay Area creator, streetwear partnership.

Produces a photographer-ready brief for any SkyyRose photography session — product/e-commerce shots (PDP catalog: hero front, angle, back, detail, flat-lay, on-body, lifestyle) AND brand/lifestyle/founder/campaign/BTS sessions. Covers per-collection visual direction, lighting, shot-list tables, platform crop specs (WooCommerce PDP, IG, Stories/Reels, Pinterest, web hero, email), file naming, styling, AVOID list, and Elite Studio handoff. Merges both product-photography and brand-photography briefs into a single unified workflow with session-type routing.

WooCommerce SEO system for SkyyRose. Keyword strategy, product page optimization, collection SEO, schema markup with PHP code, technical SEO checklist, and site architecture. Use when optimizing skyyrose.co for search engines or auditing SEO performance.

Produces a photographer-ready brand shoot brief for SkyyRose — shot list, per-collection creative direction, mood board language, and deliverable specs — for lifestyle, founder, and campaign sessions that feed the Elite Studio imagery pipeline.

Produces slide-by-slide Instagram carousel scripts, design notes, and brand-voice captions for SkyyRose product launches, collection stories, and styling content.

Produces the complete SkyyRose brand media kit document — cover, brand story, founder bio, per-collection one-sheets, product highlights, press contact, and brand asset list — for journalist and partner outreach, with all metric fields marked operator-supplied.

Creates SkyyRose-specific meme content briefs — Oakland-community humor, streetwear insider takes, and brand-adjacent formats — that feel native to the platform without breaking founder canon.

Produces a platform-ready SkyyRose social media graphics brief — canvas specs, per-collection design direction, layout rules, color tokens, and file naming — for a coordinated graphic set across Instagram, TikTok, Pinterest, X, and email that feeds the Elite Studio social pipeline.

This skill activates when users want to extract patterns from sessions, save learnings to Serena memory, or improve the copilot based on past experiences. Automatically runs as Stop hook to capture patterns after each session.

Use when deploying WordPress themes to skyyrose.co, verifying deployments, checking CSP headers, validating console errors, or performing rollbacks. Triggers on keywords like "deploy", "upload", "production", "staging", "rollback", "verify deployment".

This skill activates when users discuss component architecture, design systems, CSS methodologies, or frontend patterns. Provides guidance on React patterns, state management architecture, component hierarchies, and scalable frontend design systems.

Expert knowledge in luxury fashion e-commerce, high-end jewelry presentation, SkyyRose brand DNA, luxury customer experience, and premium product storytelling. Triggers on keywords like "luxury", "fashion", "jewelry", "high-end", "premium", "skyyrose", "collection", "product presentation", "luxury customer experience".

Use when searching for open-source resources, themes, components, libraries, or examples. Triggers on keywords like "find", "search for", "look for", "discover", "open source", "github", "npm", "template", "example", "boilerplate".

Expert knowledge in HTML, CSS, responsive design, CSS Grid, Flexbox, modern layout techniques, and semantic markup. Triggers on keywords like "html", "css", "layout", "responsive", "grid", "flexbox", "semantic", "accessibility markup", "forms".

Expert knowledge in building custom WordPress themes, template hierarchy, hooks, filters, and WordPress.com compatibility. Triggers on keywords like "wordpress theme", "template", "wp_", "get_template_part", "theme.json", "block theme", "functions.php".

This skill activates when users discuss site speed, Core Web Vitals, optimization, bundle size, lazy loading, or performance issues. Provides guidance on measuring, analyzing, and optimizing web performance with focus on LCP, FID, CLS, and modern performance patterns.

Use to work the way the Claude Code team works — parallelize aggressively across worktrees and subagents, plan before non-trivial work, verify everything, and reach for /loop, /batch, /simplify, and effort:max on the right tasks. The power-user operating posture, distilled.

Use when adding, upgrading, or resolving Python/Node dependencies — declare every import, cap majors to stop silent drift, and keep the resolver consistent. Prevents undeclared-import and silent-major-bump defects.

Use for symbol-precise code navigation on the monorepo — go-to-definition, find-references, rename, hover-types via the installed LSP servers instead of grep guessing. Answers from the real symbol graph, not text matching.

Use at the start and end of every task — read the canonical memory before acting and write the outcome after. Unifies OpenWolf files and claude-mem so knowledge persists across sessions instead of being re-derived.

Use when structuring how you approach any task — select the reasoning technique that fits the task type (chain-of-thought, ReAct, few-shot, tree-of-thoughts, self-consistency, structured output) to produce production-quality work, always subordinate to verification.

Use after any correction, mistake, discovery, or fix — capture the lesson durably into cerebrum + buglog so the same discovery is never repeated. Closes the improvement loop that makes the team better across sessions.

Use before caching, quoting, or acting on ANY product, imagery, or brand fact — resolve it from the canonical source registered in SOT.md, never from memory or a filename. Prevents second-copy drift and wrong-fact defects.

Use before any git commit/stash/history operation in a repo that multiple Claude sessions may share — never rewrite another session's HEAD, never pop a shared stash. Prevents cross-session commit corruption.

MANDATORY before rendering, creating content, or editing skyyrose.co — eyes-on verify every product image is the CORRECT garment for its SKU by reading the actual pixels (vision), never the filename or manifest. Prevents wrong-garment imagery, the

Use after editing any SkyyRose theme CSS/JS — production serves the .min build, so every source edit must rebuild .min and re-verify BOTH source and .min. Prevents shipping stale minified assets.

Use when reviewing any gate, guard, validator, or permission check — audit that it FAILS CLOSED (absent input/config/token/manifest → block, never pass). Prevents the fail-open pattern (bug-230) where a gate silently succeeds because its input is missing.

Use before trusting any green test — prove the test can actually FAIL by mutating the code it covers. A test that still passes when its target is broken tested nothing.

Use when an authoritative signal reports a regression (failing test, live HTTP/size/PHP-error, canon drift) — diagnose the ROOT CAUSE, fix the source, and confirm the heal by INDEPENDENTLY re-deriving fresh evidence, not by trusting the fix's self-report.

Use when writing or debugging tests that pass alone but fail (or mutate the repo) in a full-suite run — enforce per-test isolation and environment-aware gating so tests never share state or depend on excluded trees.