7,630 件 ・ 関連度順
概要と使いどころ
[General] Use when you need to (re)generate a DERIVED navigation index, cross-capability ERD, or reimplementation guide assembled FROM the canonical Feature Specs under docs/specs/**. Never extracts a separate A-E engineering tree.
日本語の概要は準備中です。原文の説明を表示しています。
[Skill Management] Use when enhancing, compressing, or expanding prompts, docs, or skills with attention anchoring [INTELLIGENT ROUTING]. Flag: --op={compress|expand|enhance} (default enhance); --op=compress strips token bloat, --op=expand reconstructs compressed text.
日本語の概要は準備中です。原文の説明を表示しています。
[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.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when the user asks to analyze package upgrades, check for outdated dependencies, plan npm/NuGet updates, or assess breaking changes in package updates.
日本語の概要は準備中です。原文の説明を表示しています。
[Testing] Use when you need to drive an integration-test suite to fully green — each round runs /integration-test-verify (whole system by default, or the target named in the prompt), and on ANY failure combines /debug-investigate + /integration-test-review (report-only) to adjudicate the fault (test wrong · test not optimal · source wrong), then /fix to resolve it at the owning layer, then /changes-review on that round's fix diff, then re-runs a FRESH full verify — looping until the whole suite passes its 2-consecutive-green-runs gate with zero failures.
日本語の概要は準備中です。原文の説明を表示しています。
[Planning] Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes.
日本語の概要は準備中です。原文の説明を表示しています。
[Content] Use when you need to build structured learning/teaching course material with Bloom taxonomy objectives, modules, lessons, exercises, and assessments.
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when creating user stories, writing acceptance criteria, analyzing requirements, or mapping business processes.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrator for agent-flow. Runs one issue or task through Implementer, Reviewer and QA as separate processes, with mechanical risk classification, a review-round cap and escalation to Needs Me, ending in a PR. Use for /implement <issue> or when asked to take an issue end to end ("have an agent take issue
日本語の概要は準備中です。原文の説明を表示しています。
Plan, write, and maintain automated tests in any language, with worked examples in Python and JavaScript/TypeScript. Use this skill whenever the user wants to write or plan tests, apply TDD (red-green-refactor), structure unit tests with arrange-act-assert and given-when-then naming, choose between fakes, stubs, and mocks, set up dependency injection for testability, build integration tests with testcontainers, database seeding, or transaction rollback, write Playwright or Cypress end-to-end tests, use property-based testing with Hypothesis or fast-check, create pytest fixtures or factory_boy factories, review coverage or mutation testing, or triage flaky tests in CI. Also trigger for "test pyramid", "test trophy", "test isolation", "mocking", "snapshot tests", "golden files", "parametrized tests", "make the tests pass".
日本語の概要は準備中です。原文の説明を表示しています。
Find, build, evaluate, and improve systems using decision models. Use for bounded classification, routing, ranking, Choice/Score/Noul, decision-model composition, evaluation harnesses, prompt/program hill climbing, and Software 3.0 workflows across software, business, organizations, and life. Separate models, code, and human judgment. TypeSafe Jev is the default hosted exemplar. Not for straightforward arithmetic, prose rewriting, or provider setup alone.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and improves task-specific decision artifacts from application requirements and labeled records. Use for data assembly, primitive and base-model selection, fitting, export/reload, inference policy, or bounded data/model/program improvement. Includes rules and no-training outcomes; does not require a rung ladder or training a general Jev.
日本語の概要は準備中です。原文の説明を表示しています。
Content quality and E-E-A-T assessment for AI citability — evaluate experience, expertise, authoritativeness, trustworthiness, and content structure
日本語の概要は準備中です。原文の説明を表示しています。
Manages brand identity, visual design system, and creative quality for MMIND.ai. Generates complete image prompts for Nano Banana Pro (Gemini), enforces the strict 5-color palette, flat-vector SaaS style, and typography standards. Use when user needs graphic prompts, brand consistency checks, visual style guidance, design briefs, or creative QA for any marketing asset.
日本語の概要は準備中です。原文の説明を表示しています。
Assess development requests, then execute and resume complete TaskBelay tasks in ZCode with Core-owned state.
日本語の概要は準備中です。原文の説明を表示しています。
Assess development requests, then execute and resume complete TaskBelay tasks in Claude Code with Core-owned state.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce traceability from natural-language intent to machine predicates, final observables, evidence, and owner-readable acceptance. Use when conducting any audit, review, QA pass, parity or compliance check, security assessment, code or architecture review, visual or behavioral comparison, data validation, system verification, completion gate, or claim that an implementation satisfies a human request.
日本語の概要は準備中です。原文の説明を表示しています。
Create Chinese PPT pages through a prompt-to-image-to-editable-PPT workflow. Use when the user wants 中文PPT图片提示词, PPT image prompts, 16:9中文PPT页面图片, 直接生成PPT图片, 根据提示词生成图片, 把图片/PDF/截图复刻成可编辑PPT, 转成可编辑PPTX, 按图片完全复刻PPT, or full production from topic/source material to generated page images and editable PowerPoint slides with editable text, cards, tables, lines, callouts and high-quality icon/image assets.
日本語の概要は準備中です。原文の説明を表示しています。
Continuously detect recurring UI/UX concepts during frontend discussions, track conversation-wide recurrence, and register repeated concepts as structured knowledge assets in a Notion database via MCP. Activates when UI/UX principles, heuristics, laws, or design patterns recur during frontend work, or on manual @ux commands (@ux save, @ux skip, @ux link).
日本語の概要は準備中です。原文の説明を表示しています。
Re-audit code changes to identify side effects, regression risks, and unhandled edge cases before merging or deploying. Use after a change is complete and before merging to a shared branch, before deploying a hotfix, after complex multi-module refactoring, or when a previous review may have missed side effects in async, state-mutating, or security-sensitive code paths.
日本語の概要は準備中です。原文の説明を表示しています。
Specialized GitHub PR intelligence agent for automatically gathering comprehensive context from Pull Requests. Activate when users need CI failure analysis, review comment investigation, or PR status assessment. Triggers on requests like "CI 실패 원인 찾아줘", "gather review comments", "check PR status", "analyze PR".
日本語の概要は準備中です。原文の説明を表示しています。
Use when reverse engineering binaries, firmware, mobile apps, JavaScript/Electron apps, .NET assemblies, network protocols, or malware samples; when decompiling, deobfuscating, unpacking, debugging, or hooking shipped artifacts; when solving CTF challenges (pwn, crypto, forensics, web); when a conclusion needs evidence from a shipped artifact rather than available source; or when routing authorized pentest and security-analysis work. Do not use for ordinary review of source code you already have.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need this project's coding standards (line length, quotes, import order, naming, commit format) — derive them from the REAL tooling config as a pointer + digest, never a guessed claim.
日本語の概要は準備中です。原文の説明を表示しています。
Use BEFORE any verbose CLI run, large file read, doc conversion, or near-context handoff — decision tree keyed by intent citing the canonical token-saving asset.
日本語の概要は準備中です。原文の説明を表示しています。