2,446 件 ・ 関連度順
概要と使いどころ
Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
日本語の概要は準備中です。原文の説明を表示しています。
Measure, root-cause, fix, verify and record performance contention on a developer machine: cloud-sync daemons (iCloud Drive, OneDrive, Dropbox, Google Drive), file indexers, AI-tool MCP server fleets, and automation browsers left behind by tests and browser skills. Trigger when the machine is slow, apps freeze, browser or MCP tool calls time out, load exceeds the core count, or before and after any UI/UX/performance test run. Includes the L0–L4 optimisation scale and the test-hygiene contract.
日本語の概要は準備中です。原文の説明を表示しています。
学术论文参考文献管理与格式核对。输入是参考文献列表（混乱格式）、BibTeX/RIS 文件、DOI 列表、或正文+引用混合时使用。功能包括：统一格式（format）、格式检查（check）、生成 BibTeX（bibtex）、格式互转（convert）、DOI 验证（verify）、正文引用位置核对（inline）。覆盖期刊/会议/学位/标准/数据集/预发表/网页 7 种文献类型，GB/T 7714 与 APA/IEEE/Nature 多种风格。不适用于：正文段落润色（用 academic-writing）、图表生成（用 academic-figure）。
日本語の概要は準備中です。原文の説明を表示しています。
Verify that the current Git branch, upstream state, and dirty working tree match the user's intended task before staging, committing, pushing, or continuing work from another session. Use this to detect stale branch reuse, leftover dirty files from previous sessions, unrelated commits on the current branch, cases where work should be split into a new branch or worktree, and post-publish cleanup decisions after push, PR creation, or PR merge.
日本語の概要は準備中です。原文の説明を表示しています。
Ship an already-committed Git branch through GitHub: verify branch/worktree intent, push, create or mark a pull request ready for review, optionally wait for CI, optionally address review comments automatically, and merge with explicit safety gates. Use when a solo developer repeatedly asks to publish committed work, register a ready PR, handle PR feedback, and complete merge.
日本語の概要は準備中です。原文の説明を表示しています。
Before adding/installing any dependency the agent named — verify the package exists (slopsquatting: ~1 in 5 AI suggestions are hallucinated), isn't typo-adjacent, is pinned + locked, and CVE-scanned
日本語の概要は準備中です。原文の説明を表示しています。
Use when claiming 'done', suggesting a commit, push, or PR — runs the evidence gate so completion claims come from fresh output in this message, not memory or earlier runs.
日本語の概要は準備中です。原文の説明を表示しています。
Use on a bug, test failure, crash, or unexpected behavior — enforce reproduce → isolate → hypothesize → verify before any fix; fires even on 'this is broken' / 'quick fix'.
日本語の概要は準備中です。原文の説明を表示しています。
Use to iterate a change until tests/quality checks pass — bounded run→revise→re-run gated by a numeric threshold, then a judge confirms. Triggers 'iterate to green', 'keep fixing until tests pass'.
日本語の概要は準備中です。原文の説明を表示しています。
Use for multi-step / ambiguous / end-to-end work — refactor a whole module, drive a vague ticket to a verified result, plan+build+verify a migration; coordinates the reasoning chain across skills.
日本語の概要は準備中です。原文の説明を表示しています。
Before stating any specific fact about an LLM provider's product — models, pricing, limits, context windows, SDK/API — for OpenAI, Gemini, Claude & others, verify against official docs, not memory.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to learn a topic or verify real understanding — rapid-competence session, error drills, learning sprint, gap probe, Feynman check. Triggers 'teach me X', 'quiz me'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing, debugging, refactoring, or reviewing code — enforces the think → analyze → verify → execute workflow — even when the user just says 'implement X' without naming it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when verifying cross-references between skills, rules, commands, guidelines, and context documents are not broken after edits, renames, or deletions.
日本語の概要は準備中です。原文の説明を表示しています。
Automate terminal UI (TUI) apps with agent-tui for testing, inspection, demos, and scripted interactions. Use when automating CLI/TUI flows, regression testing terminal apps, verifying interactive behavior, or extracting structured text from terminal UIs. Also use when asked what agent-tui is, how it works, or to demo it. Do not use for web browsers, GUI apps, or non-terminal interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project contains text, UI components, icons, form controls, data visualisations, or focus indicators — in short, almost every project. Under no circumstances hard-code colour values without verifying contrast ratios. Absolutely always ensure text meets 4.5:1, large text meets 3:1, and non-text UI elements meet 3:1 against adjacent colours. Test in light mode, dark mode, and forced-colors (high contrast) mode.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Write Integration Tests workflow for spec-first integration test authoring. Also covers converting existing test specs into integration test code and verifying integration test stability (repeat-run verification).
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when you need to enforce quality gates, verify compliance with standards, track quality metrics, and generate audit trails.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when you need to review integration tests for assertion quality, bug protection, repeatability, and test-spec traceability — AND verify the review target (changed production code) has test coverage (integration-first) with spec↔test↔code alignment.
日本語の概要は準備中です。原文の説明を表示しています。
[Planning] Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when evaluating review feedback, requesting targeted code-quality review, or verifying completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
[AI & Tools] Use when you need create, verify, or enhance Claude Code custom agents (Claude Code custom agent files).
日本語の概要は準備中です。原文の説明を表示しています。
Converts structured prospect research into concise outreach preparation briefs. Use when the user provides prospect or account research and wants a brief with context, angles, and claims to verify. It generates a research brief and must not invent personalization or send outreach.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing, fixing, or verifying a pull request. Focus on correctness regressions, missing tests, permission mistakes, unsafe behavior, and minimal fixes.
日本語の概要は準備中です。原文の説明を表示しています。