4,470 件 ・ 関連度順
概要と使いどころ
Use when the user asks which /phx: command fits a task (review, plan, debug, test) or how two commands differ. Checks plans and git state, then recommends from the routing table. Not for bare /help, a tour, or ambiguous requests (intent-detection).
日本語の概要は準備中です。原文の説明を表示しています。
Generate interactive 3D holographic collectible-card websites from a user description or reference image, using layered artwork, Blender and Three.js. Includes project-local Blender installation, reusable parallax materials and browser verification. Host-agnostic — any harness that runs a multimodal model can use it, since the model draws the layer artwork and inspects the rendered frames. Use when the user asks for 全息闪卡, 镭射卡, 3D 卡牌网页, a holographic collectible card site, or an editable card.blend.
日本語の概要は準備中です。原文の説明を表示しています。
A complete marketing department in one skill. Website and landing-page audits with weighted 0-100 scores, copywriting with panel scoring and AI-slop removal, an 18-tactic ad hook engine, GEO/AEO for getting cited by ChatGPT/Perplexity/AI Overviews, paid-ads creative diagnosis and production briefs, email sequences, LinkedIn/X writing, launch playbooks, positioning and offer design, competitor teardowns, app store optimization, honest analytics and test design. Use for ANY marketing task — audit, write, rewrite, diagnose, score, plan, launch, position, price, analyze — whenever the user mentions marketing, growth, conversion, copy, ads, hooks, CPM, ROAS, SEO, GEO, email, social, landing pages, funnels, launches, competitors, brand, positioning, pricing, or app stores, or says "my landing page sucks", "nobody's converting", "why are my CPMs up", "AI doesn't recommend us", "write me 20 hooks". Route via the table inside; fan out subagents for multi-dimensional work. Not for pure engineering, legal, or finance.
日本語の概要は準備中です。原文の説明を表示しています。
Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any variation of wanting authentic-sounding output.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for managing R package lifecycle according to tidyverse principles using the lifecycle package. Use when: (1) Setting up lifecycle infrastructure in a package, (2) Deprecating functions or arguments, (3) Renaming functions or arguments, (4) Superseding functions, (5) Marking functions as experimental, (6) Understanding lifecycle stages (stable, experimental, deprecated, superseded), or (7) Writing deprecation helpers for complex scenarios.
日本語の概要は準備中です。原文の説明を表示しています。
表格文件采集工具。读取单个表格文件或目录中的 csv、tsv、xlsx、xls 文件，执行行记录采集，输出统一结构化表格记录文件。 当用户提到表格采集、读取科研数据表、汇总 CSV/TSV/Excel 表格、把本地表格文件转成结构化记录等需求时使用此 skill。 即使用户没有明确说出"表格采集"，只要任务涉及把本地结构化表格文件内容收集成统一记录，就应该使用此 skill。 不负责表格清洗、空行删除、字段去空格、格式校验、字段过滤或格式转换。
日本語の概要は準備中です。原文の説明を表示しています。
格式一致性校验工具。读取被检验表和标准化数据模式表，比对两者的表头结构（字段名、字段数量）是否一致， 校验通过后输出数据文件。当用户提到格式一致性校验、表头校验、数据结构比对、字段一致性检查等需求时使用此skill。 即使用户没有明确说出"格式一致性"，只要任务涉及比对数据表结构与标准模式结构，就应该使用此skill。
日本語の概要は準備中です。原文の説明を表示しています。
从PDF文件中提取表格数据，输出为JSON格式。当用户需要从PDF中提取表格时使用此skill。
日本語の概要は準備中です。原文の説明を表示しています。
Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill/edit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say "write a report", "draft a proposal", "make a contract", "fill in this form", "reformat to match this template", or any task whose final output is a .docx file. Even if the user doesn't mention "docx" explicitly, if the task implies a printable/formal document, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
日本語の概要は準備中です。原文の説明を表示しています。
Generate exactly one finished CRT retro computer-interface illustration from an uploaded portrait, group photo, creature, object, or described theme. Use when the user wants anchored subjects re-authored as an exaggerated circa-1980s bitmap editorial caricature beneath early Macintosh or Minitel-style windows, optionally invoking the exact Chinese presets 街头怪诞, 巨像符号, or 冷面几何. Before generation, collect a named or image-derived palette and aspect ratio through a strict two-stage intake unless supplied. Preserve each intended subject as a distinct identity, one shared pixel lattice, restricted non-skin checkerboard midtones, low-facet geometry, unequal extraction windows, mandatory barrel-curved CRT edges, and the immutable tait-crt-interface-skill title-bar signature. Never trace, auto-pixelate, imitate photographic detail, omit, merge, or duplicate subjects, retry, resize, expose prompts, or ask users to choose a style preset.
日本語の概要は準備中です。原文の説明を表示しています。
Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts. Use after security scans, before patch generation, or whenever the user wants confirmation that a suspected vulnerability is actually exploitable.
日本語の概要は準備中です。原文の説明を表示しています。
Precision-first adversarial bug hunting for runtime, logic, data, concurrency, and security defects. Uses deterministic risk triage, evidence-bounded retrieval, Hunter/Skeptic/Referee review, optional hybrid verification, and explicit immutable Fixer scope. Scan-only and single-pass by default; complete-coverage loops, edits, autonomous fixes, and commits each require explicit intent. Use for code review, security audits, regression hunting, PR review, and evidence-backed remediation planning in skills-capable coding agents.
日本語の概要は準備中です。原文の説明を表示しています。
Write robust, portable shell scripts with proper error handling, argument parsing, and testing. Use when automating system tasks, building CI/CD scripts, or creating container entrypoints.
日本語の概要は準備中です。原文の説明を表示しています。
API design and implementation across REST, GraphQL, gRPC, and tRPC patterns. Use when building backend services, public APIs, or service-to-service communication. Covers REST frameworks (FastAPI, Axum, Gin, Hono), GraphQL libraries (Strawberry, async-graphql, gqlgen, Pothos), gRPC (Tonic, Connect-Go), tRPC for TypeScript, pagination strategies (cursor-based, offset-based), rate limiting, caching, versioning, and OpenAPI documentation generation. Includes frontend integration patterns for forms, tables, dashboards, and ai-chat skills.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user uploads Excel (.xlsx/.xls) or CSV files and wants to perform data analysis, generate statistics, create summaries, pivot tables, SQL queries, or any form of structured data exploration. Supports multi-sheet Excel workbooks, aggregation, filtering, joins, and exporting results to CSV/JSON/Markdown.
日本語の概要は準備中です。原文の説明を表示しています。
Interpret medical lab/test reports (blood panels, urine, liver/kidney function, thyroid, tumor markers, coagulation, cardiac enzymes, hormones, etc.) uploaded as images, PDFs, or text. Trigger whenever the user uploads a lab report, medical test result, or clinical diagnostic sheet — or says things like "help me read this report", "what do these results mean", "化验单", "检验报告", "帮我看看这个报告", "blood test results", "lab results", "体检报告", "检查报告单", "血常规", "尿常规", "肝功能", "肾功能", "甲功", "凝血", "interpret my labs", "are these results normal", "这些指标正常吗". Also trigger when the user uploads ANY medical-looking document with tables of values, reference ranges, or clinical test names — even if they don't explicitly ask for interpretation. Do NOT trigger for symptom triage (use emergency-triage instead), drug interaction queries, or general medical Q&A without an actual report to interpret.
日本語の概要は準備中です。原文の説明を表示しています。
Build chapter-level briefs (`outline/section_briefs.jsonl`) from chapter skeleton plus section bindings before stable H3 decomposition.
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite subsection openers so they stop reading like a generated table-of-contents: remove \"overview/narration\" stems and reduce repeated opener cadences across H3s.
日本語の概要は準備中です。原文の説明を表示しています。
Use when `evidence-review` has screened includes and needs a schema-aligned extraction table.
日本語の概要は準備中です。原文の説明を表示しています。
Screen the direction pool with a discussion-first scoring pass, writing `output/trace/IDEA_SCREENING_TABLE.md`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when `evidence-review` has an extraction table and needs lightweight risk-of-bias fields.
日本語の概要は準備中です。原文の説明を表示しています。
Build a retrieval-informed chapter skeleton (`outline/chapter_skeleton.yml`) from taxonomy/core scope before stable H3 decomposition.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a broad paper candidate pool needs deterministic deduplication and a stable core set.
日本語の概要は準備中です。原文の説明を表示しています。