4,143 件 ・ 関連度順
概要と使いどころ
React useEffect best practices from official docs. Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization. Teaches when NOT to use Effect and better alternatives.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a product idea into a repeatable manual process you can start delivering today. Use to design manual-first products before writing any code.
日本語の概要は準備中です。原文の説明を表示しています。
Collaborative writing partner that assists with research, outlining, drafting, citations, and iterative feedback. Helps writers create high-quality content while maintaining their unique voice and style.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, reviewing, or deciding what to post on Threads. Also triggers when planning post-viral strategy or checking posting timing. Runs pre-publish checks based on Meta algorithm patents.
日本語の概要は準備中です。原文の説明を表示しています。
Technical blog post writing guide. rooftopsnow.tistory.com style — Korean formal technical prose, architecture diagrams, code blocks + design intent commentary, table comparisons, checklist wrap-up. Triggers on "blog", "포스팅", "블로그", "기술 글", "tech blog".
日本語の概要は準備中です。原文の説明を表示しています。
Linting and code quality workflow for Software Metrics Machine. Covers ESLint 9.x flat config, Prettier formatting, lint-staged (auto-fix on commit), per-workspace configs, TypeScript strict mode, and all lint commands. USE FOR: lint, eslint, prettier, format, code style, linting, lint fix, auto-fix, check style, code quality, lint-staged, typecheck, type-check, tsc noEmit. DO NOT USE FOR: writing tests (use tdd skill), building (use build commands), commit hooks setup.
日本語の概要は準備中です。原文の説明を表示しています。
Acceptance testing workflow for the Software Metrics Machine CLI e2e suite. Use when writing, extending, debugging, or reviewing bashunit acceptance tests under apps/cli/e2e, including command help checks, cached fixture flows, GitHub MSW-backed flows, local git repository fixtures, SMM_STORE_DATA_AT workspaces, and pnpm run test:cli:acceptance. USE FOR: CLI acceptance tests, e2e tests, bashunit, apps/cli/e2e, command smoke tests, persisted CLI output tests. DO NOT USE FOR: unit tests or Vitest tests (use tdd skill), linting (use lint skill), webapp browser tests.
日本語の概要は準備中です。原文の説明を表示しています。
Watch a CI run's jobs to completion without idling or hand-writing a poll loop. Use when a dispatched or pushed build takes minutes to finish and its per-job results decide the next step.
日本語の概要は準備中です。原文の説明を表示しています。
Gives a repository one idempotent, repo-local worktree setup script (local env files, dependency install, build steps) that worktrunk's `.config/wt.toml` pre-start hook and Orca's `orca.yaml` scripts.setup both call, so every new git worktree is usable at once. Use when adding or fixing worktree setup hooks, writing `wt.toml` or `orca.yaml` setup, when new worktrees lack dependencies or `.env` files, or when asked to make worktrees "just work" in a repo. For creating a worktree in a repo that already has setup, use `git-branch-management` instead.
日本語の概要は準備中です。原文の説明を表示しています。
Load before the first bd command of any kind (reads included) in every session, even when bd prime context is already present. Applies reusable Beads writing and update practices when reading, creating, updating, commenting on, closing, superseding, or handing off Beads issues, alongside beads, beads-solo, and plan-to-beads workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Revisa o produce textos visibles para la persona usuaria (texto de UI, encabezados, botones, mensajes de error, marketing) con la voz y el tono del proyecto. Úsalo cuando la persona pida escribir/mejorar textos, corregir la redacción, revisar el tono o redactar microcopy (p. ej. "escribe el texto del estado vacío", "haz este mensaje de error más amable", "revisa el titular de la landing").
日本語の概要は準備中です。原文の説明を表示しています。
Produces neutral, section-pinned U.S. legislative bill summaries translating statutory language into plain terms with identifying data, provisions, fiscal impacts, and controversy. Use when summarizing bills, analyzing proposed legislation, preparing bill briefs, digesting committee reports or fiscal notes, or writing legislative updates.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure HIPAA compliance when handling PHI (Protected Health Information). Use when writing code that accesses user health data, check-ins, journal entries, or any sensitive information. Activates for audit logging, data access, security events, and compliance questions.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares for hiring manager rounds at Staff+ (L6+) level — scope of impact, influence without authority, ambiguity navigation, mentorship, strategic thinking. Use when practicing HM rounds or calibrating story depth for target level. Activate on "hiring manager round", "HM screen", "staff level", "scope of impact". NOT for coding interviews, system design, behavioral/values rounds, or resume writing.
日本語の概要は準備中です。原文の説明を表示しています。
Frontend stack decisions, Cloudflare deployment patterns, component systems, and internal tools architecture. Use for framework selection, deployment strategy, design system bridging, shadcn setup. Activate on "frontend architecture", "tech stack", "Cloudflare Pages", "component library", "internal tools", "shadcn setup". NOT for writing CSS (use frontend-developer), design critique (use design-critic), or backend APIs.
日本語の概要は準備中です。原文の説明を表示しています。
Interprets GitHub Actions run status and logs, diagnoses CI failure patterns, and suggests targeted fixes. Handles dependency install failures, test timeouts, build OOM, flaky tests, and workflow misconfigurations. Activate on: 'CI failing', 'build broken', 'workflow error', 'GitHub Actions debug', 'flaky CI', 'pipeline timeout', 'CI red'. NOT for: writing new workflows from scratch (use github-actions-pipeline-builder), CI caching strategy (use ci-cache-optimizer), deployment orchestration (use devops-automator).
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes ticket complexity and dependencies against the codebase before sprint planning. NOT for writing plans (mk:plan-creator); NOT for scope review (mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing TypeScript code, fixing type errors, or configuring strict type safety. Auto-activates on .ts/.tsx files. Covers null handling, utility types, and ESLint.
日本語の概要は準備中です。原文の説明を表示しています。
Writing tests, running validation, and (TDD mode) red-green-refactor. Active in Test + Build phases. NOT for coverage-gap mapping (mk:nyquist) or sprint contracts (mk:sprint-contract).
日本語の概要は準備中です。原文の説明を表示しています。
Implementing features or writing code. TDD is opt-in via --tdd / MEOWKIT_TDD=1. Provides code patterns, skill loading, and coding standards.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, reviewing, or refactoring Vue 3 code — components, composables, reactivity, Pinia state, Pinia Colada data-fetching, file-based routing, and forms. Targets Composition API + <script setup> + TypeScript. Auto-activates on .vue files. For deep best-practices review/recommendations or the full ordered workflow (built-in components, animations, performance pass), use mk:vue-best-practices.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing tests, running validation scripts, or (in TDD mode) enforcing red-green-refactor cycle. Activates during Phase 2 (Test) and Phase 3 (Build). NOT for coverage gap mapping (see mk:nyquist); NOT for sprint contract negotiation (see mk:sprint-contract).
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing TypeScript code, fixing type errors, or configuring strict type safety. Auto-activates on .ts/.tsx files. Covers null handling, utility types, and ESLint.
日本語の概要は準備中です。原文の説明を表示しています。