600 件 ・ 関連度順
概要と使いどころ
Perform a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the work is functionally complete and needs finishing touches—not when the hierarchy, structure, tone, or technical foundation still need major changes.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and realign UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
日本語の概要は準備中です。原文の説明を表示しています。
Final quality pass fixing alignment, spacing, consistency, interaction states, and micro-details before shipping. Executes changes (unlike design-audit and design-critique which are report-only). Triggers on polish, finishing touches, final pass, something looks off, pre-launch, good to great.
日本語の概要は準備中です。原文の説明を表示しています。
Design Shiny application UIs using bslib for theming, layout_columns for responsive grids, value boxes, cards, and custom CSS/SCSS. Covers page layouts, accessibility, and brand consistency. Use when building a new Shiny app UI from scratch, modernizing an existing app from fluidPage to bslib, applying brand theming, making a Shiny app responsive across screen sizes, or improving accessibility of a Shiny application.
日本語の概要は準備中です。原文の説明を表示しています。
Build a feature store using Feast for centralized feature management, configure offline and online stores for batch and real-time serving, define feature views with transformations, and implement point-in-time correct joins for ML pipelines. Use when managing features for multiple ML models, ensuring training-serving consistency, serving low-latency features for real-time inference, reusing feature definitions across projects, or building a feature catalog for discovery and governance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to find duplication, check consistency, establish or repair SSOT, consolidate facts, or when the user says "consolidate this" or "ssotize this". Not for remote or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Playwright automation failures against code-server (VS Code in browser). Use when: (1) trust dialog blocks all clicks — "monaco-dialog-modal-block intercepts pointer events", (2) button:has-text() finds wrong buttons behind modal dialog, (3) keyboard shortcuts don't work — Meta vs Control inconsistency, (4) VS Code extension activity bar icon not found by aria-label, (5) panels show placeholder text despite extension being "Connected". Covers trust dialog dismissal, keyboard shortcut hybrid mode, extension panel selectors, and database connection verification for Grafema extension.
日本語の概要は準備中です。原文の説明を表示しています。
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish".
日本語の概要は準備中です。原文の説明を表示しています。
Local SEO audit — "best [cuisine] near me" targeting, Google Business Profile optimization, NAP consistency, citation building, restaurant schema markup
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要验证一个信念/理论/策略/商业模式的正确性、在做决策前想检验逻辑、或在问"怎么判断这个观点对不对""这个方案有没有逻辑漏洞""怎么系统地检验一个想法"时激活。 核心信号：用户需要对某个命题做系统性的逻辑验证，而非直觉判断。 不适用于：纯情感判断、不需要逻辑验证的常识性问题、时间紧迫的直觉决策。
日本語の概要は準備中です。原文の説明を表示しています。
训练与推理数据不一致的端到端根因分析。当模块映射/值比较不足以定位问题时使用，可追踪首个可信的分歧边界，过滤融合或结构性误报，遵循生产者-消费者链，并生成包含具体假设和证据的根因报告。
日本語の概要は準備中です。原文の説明を表示しています。
Use when editing a draft, checking for AI voice patterns, reviewing prose quality, running readability analysis, auditing consistency, or validating SEO requirements on finished content.
日本語の概要は準備中です。原文の説明を表示しています。
Write and improve prompts for Kling AI video generation, and pick the right Kling model for the job. Covers image-to-video, text-to-video, multi-shot storyboards, talking avatars from one photo plus audio, motion transfer, video editing of an existing clip, Element Reference for character consistency, Voice Control and voice cloning, native audio and dialogue, first/last frame control, credit and API costs, and troubleshooting failed generations.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews construction plans for architecture consistency and implementation feasibility. Use when reviewing implementation plans before approval.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews integration completeness including design-implementation consistency, review/test coverage, and completion criteria. Use when performing integration review in Construction Phase.
日本語の概要は準備中です。原文の説明を表示しています。
Master coordinator for the founder. Filters noise, owns cross-functional processes, enforces consistency, routes decisions, and positions outputs for impact so the founder can think clearly. Doesn't own any function owns the space between all of them.
日本語の概要は準備中です。原文の説明を表示しています。
Use when existing copy needs tightening for clarity, accuracy, tone consistency, or executive readability without changing the underlying message.
日本語の概要は準備中です。原文の説明を表示しています。
Discover how a codebase already handles a specific concern — search broadly, find every instance, and assess consistency. The "how does this app do X?" tool.
日本語の概要は準備中です。原文の説明を表示しています。
Prose quality checker for Quarto (.qmd) files, grounded in William Zinsser's *On Writing Well* (30th Anniversary Edition). Checks for clutter, weak verbs, hollow qualifiers, clichés, inflated academic voice, poor leads and endings, pronoun and tense inconsistency, and unclear explanation. Produces a structured markdown report organized by document section — never modifies the source file. Use when asked to improve prose quality, tighten writing, reduce clutter, or apply Zinsser's writing principles to a draft. For grammar and punctuation, use the proofread skill. For APSA style rules, use the apsa-style skill. Supports an optional output-file argument and an optional @sec-label argument to restrict checking to one section.
日本語の概要は準備中です。原文の説明を表示しています。
"Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-activates when synthesizing outputs from multiple parallel sub-agents to create cohesive, integrated design with consistency checking and conflict resolution.
日本語の概要は準備中です。原文の説明を表示しています。
Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation). Use when a user has a Go spec to review, asks "is this spec ready?", or is about to implement from a written design. Distilled from spf13/go-skills and adapted to this repo's conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Draft or restructure research-paper sections, refine local prose, and audit manuscript-wide consistency. Use for evidence-grounded academic writing and revision, not independent acceptance-risk review or official rebuttal management.
日本語の概要は準備中です。原文の説明を表示しています。