Recently Added
Fresh skills just added to the collection. Be the first to try them out!
commit-changes
by SamGu-NRX
Clean up, review, validate, and commit a repository's intended changes. Use when asked to commit, make a commit, write a commit message and commit, or finish local changes as a Git commit. Always invoke $deslop across every staged file before drafting the message or running git commit.
babysit
by SamGu-NRX
'Watch a PR or related PR stack until merge or closure, coordinate CI and review fixes, and recommend human review. Use for "babysit #N", "watch this stack", or "keep these PRs green". Never merges.'
apple-design
by SamGu-NRX
Cross-platform UI/UX design reviewer grounded in Apple's Human Interface Guidelines (123 pages pulled from developer.apple.com, including 57 component pages) plus a design-craft lens for distinctive, non-templated work. Use it to audit, review, critique, or improve any mobile app (iOS, Flutter, React Native) or desktop app (macOS, Tauri, Electron) design: design review, UI audit, HIG compliance, accessibility audit, dark mode, Liquid Glass or glassmorphism, navigation structure, iPhone Duo or foldable layouts, Apple Pay buttons and marks, widgets and Live Activities, onboarding, forms, app icons, generative AI UX, App Review rejections over design or branding, or requests like "make this look less generic". Also use whenever the user shares screenshots, mockups, wireframes, Figma exports, or UI code and wants feedback, even if they only say "review my design" or "is this good UI", or asks to audit a codebase or pull request. Works for SwiftUI, UIKit, AppKit, Flutter, React Native, Tauri, and Electron.
web-perf
by CxElegy
Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.
supabase
by CxElegy
"Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse)."
site-architecture
by CxElegy
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," "site navigation," "which website builder should I use," "migrate my website," or "add a blog to my existing site." Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.
signup
by CxElegy
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.
seo-audit
by CxElegy
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
onboarding
by CxElegy
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
interface-design
by CxElegy
Craft-first interface design for dashboards, admin panels, SaaS apps, tools, settings pages, data interfaces, and interactive products. Use when designing, building, reviewing, auditing, or refining product UI where visual craft, layout hierarchy, tokens, states, visual direction, or design-system consistency matter. Not for marketing pages, landing pages, campaigns, or brand-only work.
design-taste-frontend
by CxElegy
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Also for app screens: dashboards, admin and analytics views, settings, inboxes and other screens people work in, with their own run and rules.
copywriting
by CxElegy
When the user wants to write, rewrite, or improve marketing copy for any page, including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "hero section copy," "this copy is weak," "this sounds like AI," "AI slop," "make it sound human," or "help me describe my product." Drafts never use AI tells like "it's not X, it's Y" reveals, "no X, no Y, no Z" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers. Claims must be supportable, and a declined claim names the evidence that would unlock it. Diagnoses the input first (blank brief, real voice, or point edit) and changes only what it calls for.
verify
by ashishtyagi10
Drive the live crew GUI (winit app) to verify changes end-to-end on macOS — build, launch isolated, inject keys/mouse safely, screenshot.
delegate-to-zcode
by zrll2
Delegate code writing to ZCode (GLM) while Claude Code decides, verifies and reviews. Use when the user says "delegate to zcode", "let zcode write it", "zcode do this", asks for parallel or autonomous coding, or when a project's CLAUDE.md says to delegate code writing to ZCode. Covers the full loop: preflight, git worktree, work order, run, verify, fix order, review, commit.
upool
by weslo
How to drive Unity in a project pooled by upool, where each session works in its own slot under .claude/worktrees with its own Editor. Use before running the Unity CLI (unity test, run, build, close, cache key, command), before editing a scene or prefab, after a Unity call times out, and when a subagent needs a Unity project of its own.
quick-slide-update
by mrkm86
インストール済みの Quick Slide プラグインを更新し、版と導入状態を確認する。「Quick Slideを更新して」「Quick Slideを最新版にして」と頼まれたら使う。Codex・Claude の登録済み配布元を使い、Git配布とZIP配布を区別する。
quick-slide-setup
by mrkm86
Quick Slide の初回導入・キッティング・セットアップ・診断をする。「Quick Slide を使えるようにして」「Quick Slide をセットアップして」「見本を開いて」と頼まれたら使う。macOS と Windows の依存ソフト、CLI のログイン、サーバの起動、ブラウザの到達を確認する。
quick-slide
by mrkm86
Quick Slide で会話の続きからスライドを作り、会話から直す。この機械で初めて使うとき・「足りない」と言われたときは導入の確かめ（--doctor）と、利用者に聞いてからの導入（--setup）もする。ユーザーが「スライドにして」「資料にまとめて」「プレゼンを作って」「パワポにして」「企画書/提案書/説明資料にして」「デッキにして」「ピッチ資料にして」「〇〇について調べて5ページぐらいでまとめて」、または make slides / build a deck / turn this into a presentation のように言ったら、ツール名が出てこなくても使う。手元の PPTX を「取り込んで」「このパワポを Quick Slide で見たい」と言われたときも使う（原稿は要らない）。「Quick Slide を更新して」「新しいバージョンにして」「アップデートして」と言われたときも使う（下の「Quick Slide を更新する」）。デザインテンプレートを会話から「登録して」「更新して」「複製して」「書き出して」と言われたときも使う（下の「デザインテンプレートを登録・更新する」）。作ったスライドについて「7・8枚目を直して」「この絵を夜に」「見出しを短く」と言われたときも使う。人に見せる資料は構成（ページごとの見出しと要点）を会話で合意してから描き、自分が知るための「調べてまとめて」は調べてそのまま描く。会話の内容を原稿に整え、ローカルの Quick Slide（未起動なら自分で起動する）に投入し、スライドの画面の URL を会話に返す。台本を書き（Claude Code か Codex）、検査して、エンジン（html-slide・image-slide）が描くところまでは Quick Slide が自分で進める。
motion-slide
by mrkm86
クリックで「拍」が進む Web プレゼン（Motion Slide）を HTML 1枚で作るスキル。場面×拍の台本 HTML を書けば、エンジンが道しるべ（パンくず・拍の点・章のレール・ここまでの言葉）・一覧・話す台本・自動再生・効果音（Web Audio の合成）・BGM（MIDI を macOS 内蔵音源で鳴らした m4a）を足し、外へ何も取りに行かない HTML 1枚にする。値がカードから表のマスへ飛ぶ・線でつなぐ・手書きの丸・その場で触れる LIVE の部品・キー付きの表が使える。色は html-slide のテーマ（既定は default）。全部の拍を Chrome で開いて、はみ出し・切れ・重なり・泣き別れを数える検査つき。「モーションスライド」「Motion Slide」「動くプレゼン」「Web プレゼン」「クリックで進む HTML」「記事をモーションスライドに」「コラムを動くスライドに」「motion-slide」等で発動。※編集できる PPTX が要るなら html-slide、画像生成で描く1枚絵の資料は image-slide、mp4 の解説動画は html-video の領分。
image-slide
by mrkm86
html-slide と同じ台本（資料用の JSON）から、画像生成で1枚ずつ丸ごと描いた資料を作り、PPTX・PDF・ページごとの画像・サムネイル一覧にするスキル（--format で画像だけにもできる）。画像は Codex 経由の gpt-image-2（ChatGPT のサブスク枠・API の従量課金なし）で描く。認証は実行の最初に1度だけ確かめ、全ページを並列に描く（既定8本）。構図（レイアウト）は指定せず Codex に任せる。スタイルは visual（既定・プレゼン・ピッチ向け）・standard（説明・報告向け）・infographic（資料全体を1枚に凝縮したポスター）・カスタム（YAML）から選ぶ。週報のような決まった形は、カスタムスタイルとカスタムレイアウトを持ち込む。台本の文字は一字一句そのまま描かせる。ロゴ・フッタ・ページ番号は絵に描かせず、PowerPoint の部品として上に載せる（あとで直せる。ロゴは html-slide と同じく右下・ふさがっていれば左下・両方だめなら置かない）。中身を変えたページだけ描き直す。描いた1枚は指示で直せる（微修正＝今の絵を土台に・作り直し＝テイストを変える）。同じ台本を html-slide に渡せば編集できる資料、image-slide に渡せば絵の資料になる（quick-slide のピッチモードにあたる）。「画像のスライド」「絵で描く資料」「ピッチ資料を画像で」「image-slide」「台本を絵のスライドにして」「ワクワクする資料」「この1枚を微修正して」「作り直して」「サムネイルで見たい」等で発動。※編集できて動く PPTX は html-slide。
illust
by mrkm86
資料やスライドに置く挿絵（中身を表す動かない絵）を SVG で描き、確かめて、描いてよい形に絞り、PNG にするスキル。画像生成（Codex）は要らない。アイコンを組み合わせる描き方と、丸・角丸・太い線だけで人や物や場面を描く描き方の 2 つを持ち、ブランドの色から挿絵の配色を作る。<icon name="users" …/> と書けば共有のアイコン（Material Symbols）の形に展開する。スクリプト・外への参照・画像の埋め込みは落とす。「挿絵を描いて」「イラストを SVG で」「この場面の絵を描いて」「挿絵を PNG にして」「illust」等で発動。※写真風・水彩などの質感のある絵は画像生成（html-slide・image-slide の Codex）の領分。構造・手順・数字は図解（html-slide の型・motion-slide の場面）の領分。
loom-orphan-stack-replacement
by rjwalters
"Load when: you are working a PR that carries loom:merge-conflict and a trusted comment, in a repository where loom-daemon branch-update strategy answers merge."
loom-loom
by rjwalters
"Tier 2 daemon-mode operator surface: observes the running Rust loom-daemon via MCP tools and dispatches sweeps for multi-account autonomous batches"
loom-judge-reference
by rjwalters
"Detailed reference material for the Judge role, split out of judge.md (the largest prompt in the repo) to keep the main workflow scannable — mirroring how champion.md references champion-reference.md / champion-common.md."