メニュー
Alias for browser-verify (Playwright + DevTools proof). Prefer loading browser-verify. Use when user or older docs say visual-verify, Playwright snapshots, or axe e2e proof. Prefer quality-check when QA path is unclear.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | visual-verify |
| description | Alias for browser-verify (Playwright + DevTools proof). Prefer loading browser-verify. Use when user or older docs say visual-verify, Playwright snapshots, or axe e2e proof. Prefer quality-check when QA path is unclear. |
This skill was merged into browser-verify.
Open browser-verify now and follow mode A (harness / Playwright) or B (DevTools).
Do not keep a parallel workflow here.
