Evan-Kim2028

High-retention insight Reels for Instagram (Silph Scope / SilphCo Analytics). Create or optimize faceless, AI-voice Pokémon TCG market insight Instagram Reels — price/volume analysis, myth-busting set narratives, concentration stats, collector mental models. Optimizes strictly for 2026 Instagram Reels ranking signals (skip rate / first 1–3s, watch time, DM shares, saves). Apply when writing Instagram Reel scripts, reviewing or ranking finished .mp4 Reels for algorithm impact, improving retention, designing share triggers, or generating new Silph Scope Instagram episodes. Routed from /instagram. When ranking which Instagram Reel will travel farthest, this skill overrides data-reels craft density. Use when the user runs /high-retention-insight-reels-instagram, /instagram, or mentions Instagram Reels, Silph Scope, or insight reels.

Instagram routing hub for SilphCo / Silph Scope. Use when the user runs /instagram or asks about Instagram Reels, Reels ranking, skip rate, shares, captions, Insights diagnosis, or which Instagram short to ship. Owns the native metrics map (skip/share/like/save/repost/comment) and post-publish primary-action decision tree. Routes to high-retention-insight-reels-instagram for faceless TCG insight Reels create/review/rank. Prefer this hub for any Instagram-first task so specialists stay discoverable under one slash command.

Principles for high-retention short-form data video (Instagram Reels, TikTok, Shorts) built from measured competitor research on data-viz and stats accounts. Use when making or reviewing data-driven short-form video, reels, TikToks, voiceover-timed data animations, retention/format questions for social video, or when a project's own reel playbook needs a philosophy layer to sit on top of. This is concepts, not commands — pair with your project's own reel playbook (operational scripts, render pipeline, asset paths) for execution.

Routing hub for marketing — offers, StoryBrand messaging, direct-response ads, word-of-mouth, social virality, and Silph Scope insight Reels. Use when creating or reviewing landing pages, pricing, emails, ads, lead magnets, launches, referral loops, Instagram Reels, or social content, or when the right marketing skill is unclear. Routes to marketing-offers, marketing-storybrand, marketing-cashvertising, marketing-contagious, marketing-going-viral, high-retention-insight-reels-instagram. Prefer product-design for product app UI craft; quality-check for ship/e2e; data for pipelines. Prefer this hub over loading all marketing specialists at once.

Production Flutter UX audit: ranked polish findings (dead taps, null text, a11y, keyboard, haptics, layout shift, async/offline honesty, motion, empty states, destructive confirm, permission priming, RTL, charts/number consistency) with optional PLAN.md per pick. Use for Flutter app polish, "feels off", release UX pass, /flutter-pro-ux-review, /flutter. Complements official Flutter architecture/test skills — does not replace them. Not for greenfield layering, RenderFlex-only fixes, React/web craft, or CI setup.

Routing hub for Flutter app work — structure vs polish vs tests vs layout fixes. Use when the task is Flutter/Dart mobile UI and the right specialist is unclear, or user says /flutter. Routes to official flutter-* architecture, test, layout skills when present, and flutter-pro-ux-review for production UX polish. Not for React/web product craft (product-design) or pure backend.

Routing hub for product UI/UX craft — density, hierarchy, mobile chrome, design-system fidelity, interaction quality, explore-before-build, and product chart judgment. Use when polishing app surfaces (card, chat, trade, filters, HUDs), sticky/mobile UX, empty/loading/error states, "works but feels off", motion/micro-interaction review, or when the right craft skill is unclear. Routes to product-ui-craft, mobile-product-ux, design-system, web-quality, ui-explore, mockup-implement, tufte, emil-design-eng, make-interfaces-feel-better, 12-principles-of-animation, flutter-pro-ux-review (Flutter apps), then browser-verify. Prefer frontend-design for full FE implementation pipelines (perf, SPA structure) when the ask is build-the-feature not craft. Do not use for marketing landings (marketing), pure QA/e2e (quality-check), or data pipelines (data).

Mobile-readable **product ECharts** (card price/volume, portfolio history, set charts) without desktop regressions — grid gutters, axisLabel floors, legend placement, adaptive height, touch tooltips, dual-viewport proof. Use when card or portfolio charts are clipped, tiny, sparse, legend-jammed, "mobile echarts", or /mobile-app-echarts-visual. Prefer mobile-blog-chart-visual for blog SVG. Prefer design-system chart tokens + tufte for honesty.

Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.

Dispatch scoped coding personas through Agent Fleet review pipelines — parallel runs from Hermes with pluggable execution backends

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Four LLM reviewers challenge changes from independent angles.

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.