Comments

review-engine-plan

by phase-rs

Review phase.rs engine, parser, AI, frontend, or rules implementation plans before code is written. Use when Codex needs an architectural gate for plans involving parser changes, engine mechanics, MTG Comprehensive Rules behavior, new variants, targeting, replacement effects, stack/casting flow, AI policy, or frontend GameAction workflows.

review-impl

by phase-rs

Review an implementation in scope, such as an uncommitted diff, a just-finished agent change, a commit, or named files, for missing or wrong behavior in phase.rs. Use when Codex needs a findings-only architecture and correctness review across engine, parser, frontend, multiplayer, AI, deck, build, or release changes.

add-engine-variant

by phase-rs

Runnable checklist gate for any proposed engine enum variant addition. Routes the proposal through the parameterization filter, the categorical-boundary check, and the existence verification before extension is permitted. Invoke this skill BEFORE proposing or implementing any new variant on QuantityRef, QuantityExpr, FilterProp, TargetFilter, ReplacementCondition, AbilityCondition, TriggerCondition, StaticCondition, ChoiceType, DelayedTriggerCondition, Effect, Keyword, ContinuousModification, or any other engine enum.

validate-cr-annotations

by phase-rs

Use when writing, modifying, or reviewing CR (Comprehensive Rules) annotations in engine code — any time a // CR or /// CR comment is added, changed, or audited. Ensures every CR number is verified against docs/MagicCompRules.txt before it enters the codebase.

pr-review-loop

by phase-rs

"Use to run a continuous review sweep over open contributor PRs in phase.rs. The skill is a thin orchestration layer over scripts/pr_review.py: discover candidates, detect stale reviews/follow-ups, dispatch review-impl for PRs that need judgment, and delegate authorized merge handling to pr-contribution-handler."

oracle-parser

by phase-rs

"Use when doing any parser work — adding new Oracle text patterns, verb forms, phrase helpers, target patterns, subject handling, effect chain composition, fixing Unimplemented fallbacks, or understanding the parser architecture. This is the SINGLE SOURCE OF TRUTH for all oracle parser knowledge. Covers the nom combinator mandate, parsing priority system, AST type system, all helper modules, and contribution checklists."

add-ai-feature-policy

by phase-rs

Use when adding a new deck-aware AI feature (DeckFeatures axis) and its companion policies (TacticalPolicy + optional MulliganPolicy) to phase-ai. Codifies the structural-detection pattern, AST-type locations, parts-based predicate convention, registry wiring sites, and recurring review traps so a new feature ships in a single commit without re-research.

springdoc-openapi

by claude-dev-suite

Springdoc OpenAPI for API documentation in Spring Boot. Covers Swagger UI configuration, annotations, schema customization, and security documentation. Based on production patterns from castellino and gestionale-presenze projects. USE WHEN: user mentions "Springdoc", "Spring Boot OpenAPI", "Swagger in Spring", "@Operation", "@Schema", "Swagger UI Spring", asks about "Spring Boot API documentation", "Spring REST documentation", "OpenAPI in Java" DO NOT USE FOR: General OpenAPI specs - use openapi instead; GraphQL - use graphql instead; Non-Spring Boot projects; Frontend OpenAPI generation - use openapi-codegen instead

gingiris-launch

by Gingiris-1031

🇺🇸 Product Launch & Product Hunt #1 Playbook — Multi-channel launch timing and sequencing. T-14 warm-up → T-0 launch day → T+7 momentum. Hunter selection, maker comment templates, comment cadence, anti-shadowban rules. Distilled from 30+ Product Hunt #1 daily launches across 150+ AI startups. Supports 3 product paths: developer/maker (PH+GitHub), B2C consumer (Reddit/communities/TikTok, skip PH), B2B (LinkedIn+media). 🇨🇳 产品发布与 Product Hunt 夺冠手册 — 多渠道发布的时序与节奏。T-14 预热 → T-0 发布日 → T+7 后续。Hunter 选择、maker comment 模板、评论节奏、防 shadowban。提炼自 30+ 次 Product Hunt 日冠、150+ AI 创业公司实战。支持三种产品路径：开发者/maker（PH+GitHub）、2C 消费者（社区种子/TikTok，跳过 PH）、B2B（LinkedIn+媒体）。 🇯🇵 プロダクトローンチ＆Product Hunt 1位プレイブック — マルチチャネルのローンチ時系列。T-14準備→T-0当日→T+7モメンタム。ハンター選定、メーカーコメント、コメントリズム、シャドウバン回避。3つの製品パス対応：開発者/maker（PH+GitHub）、2C消費者（コミュニティ種・TikTok、PHスキップ）、B2B（LinkedIn+メディア）。 🇰🇷 제품 출시 & Product Hunt 1위 플레이북 — 멀티채널 출시 타이밍과 시퀀싱. T-14 워밍업 → T-0 출시일 → T+7 모멘텀. 헌터 선정, 메이커 코멘트, 댓글 리듬, 섀도밴 방지. 3가지 제품 경로 지원: 개발자/maker(PH+GitHub), 2C 소비자(커뮤니티 씨드/TikTok, PH 건너뜀), B2B(LinkedIn+미디어). Triggers: "product launch" "launch strategy" "Product Hunt" "PH launch" "how to launch" "go to market" "GTM" "launch day" "find a hunter" "maker comment" "launch sequencing" "发布策略" "产品发布" "发 PH" "Product Hunt 准备" "找 hunter" "ローンチ" "출시 전략"

gr-backlinks

by Gingiris-1031

Systematic backlink building for indie founders. Covers 5 channel types ranked by GEO + SEO ROI: Wikipedia (entities), authoritative media (PR), industry reviews (G2/Capterra/Product Hunt), Reddit/Quora discussions, and HARO/Featured.com expert quotes. Designed for 0→1 sites where domain authority is the bottleneck. Aligns with 2026 Google/Bing GEO guidance: backlinks are the strongest brand-authority signal AI search engines use to decide citations. Defaults to dev/B2B link sources; for 2C products (education, consumer apps) authority links differ — see gingiris-seo-geo/references/2c-adaptation.md.

gh

by cli

Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback.

zoom-meeting-scribe

by xuiltul

Zoom会議の聞き取り担当ワークフロー。RTMS経由で届く会議トランスクリプトを黙って理解・記録し、緊急事項のみ上司へエスカレーション、会議終了後に人間の承認を得てからレポートを投稿する。 Use when: source=zoom のinboxメッセージ（「[Zoom会議実況 チャンク#N …]」または「[Zoom会議終了 …]」ヘッダ付き）を受信したとき。

zoom-meeting-scribe

by xuiltul

Zoom 회의 청취 담당 워크플로. RTMS를 통해 도착하는 회의 트랜스크립트를 조용히 이해·기록하고, 긴급 사항만 상사에게 에스컬레이션하며, 회의 종료 후 사람의 승인을 받은 뒤 리포트를 게시한다. Use when: source=zoom 인 inbox 메시지(「[Zoom会議実況 チャンク#N …]」 또는 「[Zoom会議終了 …]」 헤더 포함)를 수신했을 때.

pr-contribution-handler

by phase-rs

Use when asked to handle, harden, or shepherd one or more external contributor PRs. Checks out PRs in a worktree or main workspace, updates them against origin/main, resolves review comments, performs architecture-focused implementation review, decides whether fixes are inline or require engine-implementer review cycles, and usually closes explicitly deferred follow-up work while already in the PR.

Algorithmic Trading

by omer-metin

claude-code-plugins

by melodic-software

"Enforce self-describing code: delete zero-info comments, dissolve the rest into names, keep only terse load-bearing ones. Modes 'safe', 'aggressive', 'strip'. Use when: 'dissolve comments', 'remove comments', 'strip all comments', 'strip agent comments', 'too many comments', 'aggressive comment removal', 'make it self-documenting', 'make the code expressive', 'comments must earn their keep'. Skip residue (audit-comment-residue), tidyings (tidy), or batch-simplify."

0xwork

by BankrBot

"Find and complete paid tasks on the 0xWork decentralized marketplace (Base chain, USDC escrow). Use when: the agent wants to earn money/USDC by doing work, discover available tasks, claim a bounty, submit deliverables, post tasks with bounties, check earnings or wallet balance, sell digital products, list services, or set up as a 0xWork worker/poster. Task categories: Writing, Research, Social, Creative, Code, Data. NOT for: managing the 0xWork platform or frontend development."

gitlawb

by BankrBot

Decentralized git for AI agents and humans. Use when the user wants to create repositories, push code, open pull requests, review and merge PRs, manage issues, create or claim bounties, delegate tasks to other agents, register human-readable names on Base L2, or interact with the gitlawb decentralized git network. Supports cryptographic DID identities, Ed25519-signed pushes, UCAN capability delegation, libp2p networking, and 31+ MCP tools for AI agent integration. Do NOT use for GitHub, GitLab, or other centralized git hosts.

claude-in-mobile

by AlexGladkov

"This skill should be used when the user asks to interact with device screens (screenshot, annotate, tap, swipe, type text), manage apps (install, launch, stop, uninstall), transfer files (push, pull), query device info (logs, system info, clipboard, screen size), run shell commands, manage desktop windows, or automate Android, iOS, Aurora OS, or Desktop apps."

ctrl-clip

by davepoon

'⧉ Copy a message to the system clipboard cleanly formatted — no blockquote pipes, no terminal bars, no Claude commentary. Use whenever you draft a message the user will paste (Slack, Teams, PR comment, email) to add a clickable "⧉ ctrl + click" copy link under it, and when the user says "/ctrl-clip", "copy that", "put it on the clipboard" (in any language). Optional argument picks the target format: slack (default), md, plain.'

bro

by davepoon

"Re-explain the previous assistant message, or any text typed after the command, in a much simpler way. For when a reply made you go 'bro what'. Use /bro for a plain-language version of the last answer, or /bro <text> to simplify a pasted paragraph, error, email, or doc."

code-walk-thru

by pchalasani

Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.

report-sudus-issue

by eas4ai

Report a defect in Sudus itself to the eas4ai/sudus issue tracker after the developer's ok, then watch the issue and update the plugin when the fix is released. Use when a sudus command crashes or exits with an internal error, refuses something the manual says it accepts, wake keeps naming an action whose predicate already holds, or a sudus message contradicts the manual.

documentation-templates

by vudovn

Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.