838 件 ・ 関連度順
概要と使いどころ
Apply these opinionated C# conventions whenever writing or reviewing C# 12 / .NET 8+ code: nullable enabled with warnings as errors, records and primary constructors, pattern matching over cast chains, the Result pattern for expected failures, async all the way with CancellationToken, IOptions config, IHttpClientFactory, and never returning EF entities from an API.
日本語の概要は準備中です。原文の説明を表示しています。
Apply these opinionated .NET 8 architecture conventions whenever structuring or reviewing a backend service: clean architecture layering and which direction dependencies point, when CQRS with MediatR is worth it, cross-cutting concerns as pipeline behaviours, minimal APIs grouped by feature, keeping DbContext in Infrastructure, health checks and structured logging, WebApplicationFactory integration tests, and when AOT pays off.
日本語の概要は準備中です。原文の説明を表示しています。
Apply these opinionated JavaScript conventions whenever writing or reviewing JS or Node: ESM-first packaging, choosing between Promise combinators, error handling that doesn't swallow failures, AbortController for cancellation, keeping the event loop unblocked, and reaching for platform APIs before dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
Opinionated house conventions for NestJS backends — module boundaries and layering, provider wiring and injection scopes, guards/interceptors/pipes/filters, DTOs and validation, domain exceptions, config, and the Nest 11 / Express 5 behaviour that compiles cleanly and fails at runtime. Use whenever the code is NestJS (`@nestjs/*` in package.json, or `@Module`/`@Injectable`/`@Controller`/`@Cron` in the file), including when the question sounds like plain TypeScript, an OOP refactor, a code review, or an ops problem — the Nest-specific answer differs from the generic one. Typical asks: scaffolding a module, adding a controller, provider, or endpoint, wiring an enhancer, a boot-time DI or circular-import failure, a response leaking entity fields despite `@Exclude()`, a cron job firing on every replica, upgrading NestJS, or reviewing a Nest diff. Not for plain Express or Fastify, Angular, frontend, SQL, or CI.
日本語の概要は準備中です。原文の説明を表示しています。
Apply these opinionated Next.js conventions whenever writing or reviewing App Router code (14+): Server Components by default, where the 'use client' boundary belongs, the caching defaults that changed in Next 15, tag-based revalidation, treating Server Actions as public endpoints, the Metadata API, and next/image and next/font.
日本語の概要は準備中です。原文の説明を表示しています。
Apply these opinionated React conventions when writing React 18+ or 19 components: hooks patterns, Server Components, Suspense boundaries, state management, performance memoization, React 19 features (use, form actions).
日本語の概要は準備中です。原文の説明を表示しています。
Review a dygo Business App for framework conventions, model quality, access control, SDK boundaries, observability, and safe lifecycle behavior. Use for App audits and pre-merge reviews, not ordinary implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Write, refactor, or review Go code in the dygo framework or App SDK using dygo package boundaries and runtime conventions. Use for substantial Go implementation that is not primarily Cobra CLI work.
日本語の概要は準備中です。原文の説明を表示しています。
Suggest better variable, function, and class names based on context and conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Review staged changes and create atomic Git commits whose messages match repository conventions. Use when the user asks to commit, write a commit message, or finalize already staged work.
日本語の概要は準備中です。原文の説明を表示しています。
Create Claude Code slash commands, OpenCode command files, Pi prompt templates, and Codex custom prompts that delegate to the right subagent or skill. Use when creating new commands, porting commands across agent platforms, or refactoring existing commands to follow platform conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Handle MindIE-SD documentation, governance, contributor workflow, commit or PR conventions, history cleanup, template changes, and version-policy updates with minimal context, fixed review steps, and deterministic output. Use this skill whenever the task touches docs/ 或文档站点内容与配置（Sphinx / Read the Docs / conf.py / index.md / 目录导航 / 首页）、中英文双语配套、治理文档、贡献流程说明、PR/MR 模板或标题正文规范、提交历史整理、版本策略与发布规则。即使用户只说「改个文档」「双语要同步」「commit message 怎么写」「PR 模板加一项」「把提交压一下」「rebase 冲突怎么理」而未提治理规范，也应触发。不负责通用工程实现与仓库默认工作流定义（后者以 AGENTS.md 为准）；Python 格式见 code-standards，Markdown 格式见 markdown-lint。
日本語の概要は準備中です。原文の説明を表示しています。
Calculates pre-petition interest for bankruptcy proofs of claim and produces a filing-ready worksheet. Covers rate source hierarchy, day-count conventions, simple interest formulas, post-petition rules under 11 U.S.C. § 506(b), and fee inclusion standards. Use when preparing interest components of a proof of claim, calculating creditor claim amounts, or verifying interest calculations.
日本語の概要は準備中です。原文の説明を表示しています。
Correct file paths, project layout, and naming conventions. Two modes: advisory (return a path) and organize (restructure).
日本語の概要は準備中です。原文の説明を表示しています。
Generate or update docs/project-context.md — the source of truth for conventions, tech stack, and anti-patterns, loaded by all agents as a constitution.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating files and need the correct path, organizing project layout, or enforcing naming conventions. Two modes: advisory (return path) and organize (restructure).
日本語の概要は準備中です。原文の説明を表示しています。
Use when answering factual or explanatory questions about the current project — codebase, architecture, conventions, workflows, constraints — with minimal cited evidence. Triggers on "how does X work here", "what does X mean", "why is X structured this way", "is this claim true in the repo", "explain X with sources". NOT for brainstorming or comparing approaches (mk:brainstorming), trade-off decisions (mk:party), debugging/root cause (mk:investigate), code review (mk:review), plans (mk:plan-creator), security audits (mk:cso), visual explanations/diagrams (mk:preview --explain), test-coverage gaps (mk:nyquist), library docs (mk:docs-finder), or workflow navigation (mk:help).
日本語の概要は準備中です。原文の説明を表示しています。
Design and review durable REST, GraphQL, RPC, or event-facing API contracts. Use for public or shared API contracts, endpoint/schema consistency, compatibility, pagination, error semantics, and API documentation. Discovers existing consumers and conventions before recommending a style.
日本語の概要は準備中です。原文の説明を表示しています。
Structured logging conventions for DraftForge backend (Django/Celery/Daphne) and frontend (React). This skill should be used when adding log statements, creating new modules, debugging with logs, or reviewing logging patterns. Covers structlog usage, system/subsystem taxonomy, required fields, log levels, and Grafana query patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined goal-to-execution workflow for any user task. Parses objective, asks only for materially missing requirements via ambiguity-gate, inspects repo via idea, plans via sdd-dev or deep-plan, executes safely under project conventions, verifies completion per R020, and reports changed files with evidence. Use when user invokes /goal <task>.
日本語の概要は準備中です。原文の説明を表示しています。
Alembic migration patterns for naming conventions, safety checks, expand-contract, env.py configuration, and CI integration
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic Kotlin patterns from JetBrains conventions
日本語の概要は準備中です。原文の説明を表示しています。
Find UX pains and opportunities fast through competitor scans, pattern research, and web search. Surfaces how others solve the same flow, common failure modes, and conventions users already expect. Use when the user says "research this UX", "how do others do X", "competitor scan", "find UX patterns", "what's the convention for Y", or before ideating a flow. Part of the Product Design set. Uses web search/fetch tools.
日本語の概要は準備中です。原文の説明を表示しています。
Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.
日本語の概要は準備中です。原文の説明を表示しています。