Coding & Development

Use only when the user asks to design a tablet UI screen or flow (split view, adaptive layouts, touch plus pointer). Do not use for phone, desktop, or non-UI work.

Turns a one-line product idea into a researched system design. It first tests whether an existing product would do, finds the laws and platform rules in force, compares structurally different stacks on real cost, then writes a stack card, two hosting cost tiers with dated prices and measurable upgrade triggers, C4 diagrams, data model, ADRs, a CI pipeline and a deployment runbook. Use it whenever someone describes software they want to build and asks what stack, database, hosting or architecture to use, what it will cost, how to deploy it, or how to "design the system", even if they only paste an idea like "an HRMS for my 20-person company" or ask "cheapest way to host X" or "should I use Supabase or Firebase for this". Covers web, mobile and desktop. Not for refactoring an existing codebase's architecture and not for writing the application code.

Use this skill whenever your answer will contain Rust code or Cargo/clippy/rustfmt config, or a verdict on existing Rust code. Simple-looking Rust tasks still need it - it holds the required conventions and a fmt/clippy/doc/test check that every Rust change must pass. That covers writing any new Rust (one function counts), fixing a compiler or borrow-checker error, adding rustdoc comments and examples, redesigning error types, refactoring, reviewing or auditing a .rs file or crate, and tidying a Cargo workspace (shared lints, editions, dependency versions). When the language is Rust, use this skill first and do not let a general debugging, documentation, refactoring, or code-review skill replace it. Skip it only when no Rust gets written or judged - explaining concepts, comparing languages, summarizing editions, or working in another language even inside a repo that also has Rust.

Designs one opinionated "Grand Slam Offer" for any app idea, new or already shipped, by running Alex Hormozi's $100M Offers method adapted to app stores. It covers the market and niche, the commodity check, a value-equation audit, the problem inventory, delivery vehicles, the trimmed value stack, pricing and tiers, scarcity, urgency, bonuses, the guarantee, naming, the paywall per placement, the onboarding fast win, a test plan and a ship plan. It works within App Store and Google Play rules. For a shipped app it reads the code and notes first and produces a before/after. Use it when the user says "/app-offer", "run app-offer on <idea>", "make a grand slam offer for my app", "Hormozi my app", "price my app" or "design my paywall offer", or asks how to package, price, name, guarantee or paywall an app. It writes offer/grand-slam-offer.md (or ./<app-slug>-grand-slam-offer.md for a new idea).

Competitor change tracker for GTM teams. Snapshots competitor pages (homepage, pricing, changelog, careers), diffs them against the last scan, and turns the changes into a GTM readout - what moved, why it matters, what to do. Use whenever the user asks what competitors changed, wants a competitor scan or weekly digest, asks about a competitor's pricing / launches / messaging / hiring changes, or wants to add or remove a competitor or page from the watch list. Triggers - "what did competitors change", "competitor scan", "run tripwire", "weekly competitor digest", "did X change their pricing", "watch this competitor", "竞品有什么变化", "竞品更新", "看看竞品这周改了什么", "加一个竞品".

Framework en 7 phases pour transformer un prototype en case study portfolio avec vidéos animées, contenu narratif bilingue et pack d'intégration. Déclencher quand l'utilisateur veut documenter un prototype, créer un case study, produire des vidéos de démonstration d'une interface, ou publier un projet dans un portfolio. Entrée : un fichier de code ou un prototype. Sortie : case study complet publié avec vidéos.

Turns the founder folder into the thing that gets one real person to say yes to the next step: a one-page pilot offer for a customer, an NSF Project Pitch or grant answer for a funder, an investor or lender one-pager, a business case for a boss, or an invite for the people who will use it. Always writes the one-sentence, three-sentence and three-minute versions first. Builds only from claims in the evidence ledger that the audience may see, never from simulated buyers, and checks the finished pitch with the ledger before it goes out. Use when the user says "pitch this", "write a pilot offer", "one-pager", "grant pitch", "NSF pitch", "deck for", "email this customer", "business case", or "what do I send them".

Delegate a general-purpose task to Google's Antigravity CLI (agy staffer, fast Gemini) with a minimal, unopinionated prompt. Use when the user says /agy:staffer, "have agy do/handle X", "have agy generate an image", or the task fits none of the specialist personas (researcher / reviewer / implementer / ask) — the template adds no role or output format, only the shared working rules and guardrails, so the task text shapes the output. Also the route to agy-native tools no specialist covers, notably image generation (generate_image).

Turn a pasted list of rough feature ideas into well-formed tracker issues, with a per-item debate before anything is filed. Use when the user hands over a batch of ideas, a backlog dump, a list of fixes, or says "file these as issues", "make tickets from this", "turn this list into issues", "batch these features", "create a backlog from this", "I have a list of things to do". Debates each item (restate, ask at most two questions with a proposed default, pin acceptance criteria), shows one review table for the whole batch, and only then files issues with labels. GitLab and GitHub.

Enforce Rule Cascade rules in Python services and jobs (FastAPI, Django, Flask, Celery, batch scripts) with the rule-cascade package. Use when wiring rules into a Python code path, replacing Pydantic validators or hand-written checks with the engine, or evaluating many records in a batch.

Enforce Rule Cascade rules in Go services and tools (net/http, chi, gin, echo, gRPC, workers) with rulescascade.com/go. Use when wiring rules into a Go code path, replacing validate tags or hand-written checks with the engine, or mapping rule findings to HTTP or gRPC errors.

Enforce Rule Cascade rules on the JVM - Java 17+, Kotlin and Scala; Spring Boot, Quarkus, Micronaut, Jakarta EE - with com.rulescascade:rules-cascade-core. Use when wiring rules into a JVM service, replacing Bean Validation or hand-written checks with the engine, or mapping rule findings to HTTP errors.

为国产麒麟 Linux 与奇安信可信浏览器进行前端兼容开发、排错和评审。涉及麒麟、银河麒麟、中标麒麟、奇安信、信创、Qianxin、Kylin、旧 Chromium，或在已声明此目标环境的项目中新增/修改页面、CSS、Tailwind、组件库、JS/TS、构建配置、浏览器 API、字体、弹窗、下载与打印时使用；覆盖源码和构建产物检查、能力降级及真机验证。

Use when a task has already been completed and accepted once and the user wants to repeat it or solidify the process — recurring deliverables, weekly reports, multi-source research, or a workflow that currently depends on one person remembering the steps.

适用于 AI 多 Agent 与人类团队协同研发的多角色状态流转、质量审计、防错闭环与看板自动化工作流技能包。可通过 /fy-flow help、/fy-flow start、/fy-flow status、/fy-flow kanban、/fy-flow trace 快捷指令或自然语言唤醒。

Reconstruct flat images, screenshots, posters, diagrams, or infographics as editable PowerPoint slides while preserving the source composition and visual effect. Use when the user asks to convert an image into an editable PPT/PPTX, split image elements into editable layers, recreate a screenshot in PowerPoint, translate in-image text into editable slide copy, or says 图片转可编辑PPT、把图片元素拆出来、保留当前效果、图片重绘成PPT、截图转PPT.

On-demand dual-model review via native `spawn_subagent` (defaulting to mcli models `deepseek-v4.1-flash` and `glm-5.3`, or user-specified models) for standalone or combined research actions (Plan, Coding, Test, or Coding+Test together). Use when designing an experiment plan, reviewing post-training/RL/masking code changes, or auditing test validity.

Set up and maintain a product lens — one git-tracked JSON graph of a product's purpose, core loop, avatars, interviewees, evidence, claims (Heard / seen · Owner's view · Untested), focus hypotheses with computed confidence, shipped surfaces and ideas, alternatives and competitors, market insights, content pillars and decisions — built into one self-contained, commentable index.html with a diff view. Use when asked to create a lens, add an interview or other evidence, update a surface after changing it, add an idea from a brainstorm, add a competitor, or show what changed in the lens.

Migrate an nf-core pipeline from the vendored utils subworkflows (utils_nextflow_pipeline, utils_nfcore_pipeline, utils_nfschema_plugin) and local helper copies to the nf-core-utils Nextflow plugin, or bump nf-core-utils / nf-schema to a newer version. Use this whenever someone wants to "use nf-core-utils", drop or replace vendored nf-core utils subworkflows, move helpers like getGenomeAttribute, softwareVersionsToYAML, paramsSummaryMultiqc, completionEmail or methodsDescriptionText to `plugin/nf-core-utils`, update the nf-core-utils or nf-schema pin, or build MultiQC tool citations from module meta.yml with citationsOnTheFly (publication blocks), or debug a run failing with "Missing process or function X ... Did you mean 'X'" after a plugin change (including AWS megatests / Seqera Platform runs).

用 PyAEDT 驱动 Ansys HFSS / AEDT 完成天线与 RF 仿真自动化的工作流骨架。当用户提到 HFSS、Ansys Electronics Desktop、AEDT、pyaedt、ansys.aedt.core,或要做天线仿真、S 参数(S11/S21)、回波损耗(return loss)、VSWR、远场方向图(far-field)、增益、辐射效率、阻抗匹配、参数化扫频(frequency sweep)、参扫优化(parametric sweep),或者说"自动化跑 HFSS / 用脚本驱动 HFSS / 让 agent 帮我跑仿真"时,务必使用本 skill。即使用户没明说"用 pyaedt",只要任务核心是"用 Python 控制 HFSS 做天线/RF 仿真",也应触发。

Perform an on-demand, bounded documentation review and update while keeping canonical docs accurate and lean.

Use when interacting with ANSYS AEDT through the current PyAEDT CLI. Triggers on requests to start or inspect AEDT sessions, manage projects, create designs, run scripts, export screenshots or configurations, or use the PyAEDT command line from the workspace virtual environment.

Prepare the current branch for review and open a GitHub pull request: run /code-review and fix its findings, review and fix the docs, run /security-review and fix its findings, record the branch's design decisions (ADRs) as commit trailers, then push and open (or update) the PR with the gh CLI, following the repo's PR template if it has one. Stops and reports, without pushing, if a finding can't be fixed. Use when the user says "/pr", "review and PR this branch", or "review, fix and open a PR". Accepts an optional base branch, a review effort (low|medium|high|xhigh), and --draft.

Entry point for work on the Nextora block-theme ecosystem — child themes, Gutenberg blocks, design presets and the visitor colour/font switcher, and template/part/pattern composition. Use when a request mentions Nextora or a Nextora child theme, when the task spans more than one of those areas, or when you need the source map and production quality gates for this ecosystem before writing code. Also use to decide which specialist skill a multi-part request needs.