6,773 件 ・ 関連度順
概要と使いどころ
Improve UX writing, marketing copy, labels, microcopy, instructions, and error messages so interfaces and product messaging are easier to understand and act on. Use when the user mentions confusing copy, unclear labels, bad error text, weak CTAs, hard-to-follow instructions, or wanting better UX writing.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate an interface from a UX perspective, assessing hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring and actionable feedback. Use when the user wants an overall design or UX review—not when the main need is measurable accessibility/performance diagnosis, or final micro-detail polish.
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants measurable accessibility, performance, responsive, theming, or anti-pattern findings—not when they mainly want an overall UX critique or final visual/detail polish.
日本語の概要は準備中です。原文の説明を表示しています。
Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health
日本語の概要は準備中です。原文の説明を表示しています。
Content strategy, copywriting frameworks (AIDA/PAS/BAB/4Ps/FAB), editorial calendar management, platform-specific content, A/B testing, campaign planning, audience targeting, and content performance measurement.
日本語の概要は準備中です。原文の説明を表示しています。
Independent LLM judge evaluates task completion separately from the executing agent, catching false success claims by reviewing task goal, actions taken, final state, and evidence. Produces PASS/FAIL with confidence score and reasoning.
日本語の概要は準備中です。原文の説明を表示しています。
Feature flag lifecycle management -- safe feature toggling, gradual rollouts, A/B testing patterns, flag cleanup strategies, and technical debt prevention. Covers LaunchDarkly, Unleash, OpenFeature, and custom implementations.
日本語の概要は準備中です。原文の説明を表示しています。
Compress large context before reasoning to reduce token usage while preserving evidence. Use this whenever the user mentions huge files, long prompts, RAG payloads, prompt caching, expensive sessions, codebase context, chat history compaction, or wants the same answer quality with fewer tokens.
日本語の概要は準備中です。原文の説明を表示しています。
Detect Claude Code context compaction events in session JSONL logs. Identifies compaction boundaries, measures token delta before/after, reports compaction events with timestamps and token impact.
日本語の概要は準備中です。原文の説明を表示しています。
N-round opposing-stance debates for trade-off analysis. Assigns pro/con roles to agents, runs structured debate rounds with quality scoring, and produces a moderator synthesis with confidence-rated recommendation. Generalizable to architecture, technology, security, and design decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.
日本語の概要は準備中です。原文の説明を表示しています。
用户需要管理一个复杂系统的核心枢纽时; 当"面面俱到"策略失效, 需要找到关键节点集中管理时; 当系统有多个核心功能区域需要分别监测时。 不适用于: 只有一个中心节点的简单系统、不需要分层管理的场景。
日本語の概要は準備中です。原文の説明を表示しています。
用户询问如何根据季节调整作息饮食运动时激活;当需要做年度健康计划或生活节奏调整时; 当感到身体状态与季节不匹配时(如冬天精力过旺无法安眠、春天却萎靡不振)。 典型触发信号: 用户提到"最近换季身体不太对""想调整作息适应季节""一年四季怎么安排生活"。 不适用于: 与季节无关的即时性问题(如突发外伤、急性感染),或已有明确西医诊断只需遵医嘱的场景。
日本語の概要は準備中です。原文の説明を表示しています。
用户需要从外部可观测信号推断内部隐藏状态时; 当需要"从表象看本质"时; 当直接观测不可行, 必须通过间接指标推断时。 不适用于: 可以直接观测内部的场景、纯数据查询、不需要推断的场景。
日本語の概要は準備中です。原文の説明を表示しています。
Trains the HUMAN user's critical thinking through four modes: drill (argument-analysis items with a single defensible answer, judge stance), scene (Socratic exploration of synthetic scenes or user-supplied material, no verdicts on interpretations; includes a configure track — design the information request and verification plan for a decision before any analysis), expedition (guided audit of impossible-tier problems from verified packs), and detective (a runtime-generated multi-layer case worked as an escape room, guide-and-judge stance). Use when the user wants to practice critical thinking, analyze arguments, hunt assumptions, examine bias, train reasoning, or decide what information a decision needs first. Triggers: critical thinking practice, train my thinking, drill, scene, byom, configure, information plan, what would I need to know, spot manipulation tactics, scam literacy, 批判思考練習, 話術辨識, detective, 查案, 破案, 偵探.
日本語の概要は準備中です。原文の説明を表示しています。
Used when the user asks to "create a PowerPoint", "generate PPTX slides", "make a PowerPoint presentation", "build a .pptx deck", "create editable slides", "PptxGenJS", "editable presentation", "corporate deck", "slide deck for sharing", or when the output format is PPTX for any presentation task. Also triggers on "export to PowerPoint", "pitch deck PPTX", "offline presentation", or when the context implies an editable/corporate format. Generates OOXML-compliant .pptx files with PptxGenJS, precise layout, text measurement, and overlap validation.
日本語の概要は準備中です。原文の説明を表示しています。
Desktop GUI automation via OpenInterpreter — mouse, keyboard, screenshot, and OCR control for native macOS/Linux applications. Three modes: Library (Claude reasons, OI executes), OS subprocess (full autonomous computer use), and Local agent (Ollama, offline). This skill should be used when interacting with desktop apps that have no CLI or API, automating GUI workflows, reading screen content via OCR, or controlling mouse/keyboard.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used to spawn specialized OpenAI Codex CLI subagents for code review, debugging, architecture analysis, security audits, refactoring, documentation, comparative evidence adjudication, and autonomous /goal runs. It adds each persona through process-local developer instructions while preserving the project's AGENTS.md chain, including during parallel launches. Supports GPT-6-Astra across low, medium, high, xhigh, max, and ultra reasoning with default or priority service tiers, plus GPT-5.6 and GPT-5.5 models. Triggers on 'delegate to Codex', 'Codex Astra', 'Astra subagent', 'Codex subagent', 'code review agent', 'security audit', 'refactor with Codex', 'goal run', 'autonomous goal', 'have Codex weigh this'.
日本語の概要は準備中です。原文の説明を表示しています。
Package codebases into LLM-optimized markdown, and run the Deep Think Authority pipeline (context-builder → Deep Think review → structured AUTHORITY → Flash/Antigravity implementation agent). Use when generating project context, preparing Deep Think reviews, or binding a weaker coding agent to a senior reasoning pass.
日本語の概要は準備中です。原文の説明を表示しています。
Use when stress-testing a proposal, plan, architecture or decision before committing to it, such as pre-mortems, assumption audits, "should we even do this?" questions, or when everyone agrees too easily. Not for code review; it challenges strategy, approach and hidden risks.
日本語の概要は準備中です。原文の説明を表示しています。
Ask Kimi a read-only free-form question about the current repository. Use for prose explanations, flow tracing, module comparisons, or conceptual reasoning where Codex should delegate the answer to local kimi-code rather than perform implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Deep cross-domain synthesis engine for the vault. Triggers on "synthesize X", "what do I know about X", "connect ideas about X", "cross-domain analysis of X", "map everything in the vault about X". Searches comprehensively, surfaces non-obvious patterns and tensions, then challenges the user to generate original thought. The vault should surprise you — if synthesis only confirms what you already think, it failed.
日本語の概要は準備中です。原文の説明を表示しています。
Agent Brain /brain-ship: a reviewed artifact is ready for release or publication.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses and fixes Claude behavioral issues in system prompts and Projects using tested countermeasure templates. Use when "Claude is too verbose," "keeps hedging," "agrees with everything," "claims it did something it didn't," "won't use a tool," "fix Claude's output," "tune Claude's behavior," "Claude ignores my preferences," "adds unsolicited disclaimers," "uses too many lists." Covers ten tendencies: agreeableness (output-content + persistent-preference), hedging, verbosity, list overuse, fabricated precision, over-exploration, tool miscalibration (over- and under-triggering), LaTeX defaulting, editorial drift, self-referential fabrication. Also use when auditing a system prompt for behavioral calibration or recalibrating a pre-4.7 prompt, and when users describe recurring output problems without naming a tendency. Do NOT use for scoring a prompt's overall quality — use rootnode-prompt-validation if available.
日本語の概要は準備中です。原文の説明を表示しています。