4,681 件 ・ 関連度順
概要と使いどころ
Verify an open factory PR before human review - re-runs gates, checks the test proves the fix, checks scope and test tampering. Use when reviewing a factory PR, running the PR review routine, or asked to independently check a change.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect factory health, stale work, CI, security advisories, and recent run evidence without implementing fixes.
日本語の概要は準備中です。原文の説明を表示しています。
| Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui, implementing dark mode, debugging CSS variable issues, fixing theme switching, migrating from Tailwind v3, or encountering color/theming problems. Covers: @theme inline pattern, CSS variable architecture, dark mode with ThemeProvider, component composition, vite.config setup, common v4 gotchas, and production-tested patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow in WooCommerce projects.
日本語の概要は準備中です。原文の説明を表示しています。
Rewrites AI-sounding text so it reads like a human wrote it. Use when the user says 'sounds like AI/ChatGPT,' 'too robotic,' or 'humanize this.' Fixes AI vocabulary, inflated significance, hedging, robotic rhythm, and formulaic structure.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "add turnstile", "implement bot protection", "validate turnstile token", "fix turnstile error", "setup captcha alternative", or encounters error codes 100*/300*/600*, CSP errors, or token validation failures. Provides CAPTCHA-alternative protection for Cloudflare Workers, React, Next.js, and Hono.
日本語の概要は準備中です。原文の説明を表示しています。
Use for test lifecycle hooks: beforeAll, afterAll, beforeEach, afterEach, fixtures, preload.
日本語の概要は準備中です。原文の説明を表示しています。
Use when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to marketplaces, or checking release readiness
日本語の概要は準備中です。原文の説明を表示しています。
Use when optimizing a bundle-plugin or single skill — improving descriptions, reducing tokens, fixing audit findings, restructuring workflows, adding skills to fill gaps, or iterating on user feedback
日本語の概要は準備中です。原文の説明を表示しています。
Build a precise, step-by-step action plan before making any code changes. Use this skill whenever the user describes a feature, bug fix, refactor, or any multi-file change. Also use when the user says "plan", "think through", "what would it take", or describes a problem without jumping to code. TRIGGER BEFORE writing any code for non-trivial changes. Do not skip planning for changes that touch more than one file or involve architectural decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Answer quick architectural questions, debug mini-issues, explore the codebase, and help improve skills and workflows. Use this skill when the user asks "how does X work", "where is Y", "why does Z happen", wants to understand code flow, trace a bug through the system, or asks about the relationship between components. Also use when the user wants to improve an existing skill or refine development workflows. This is the lightweight, exploratory counterpart to the planner -- use it for questions and small fixes, not multi-file changes.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate an alert or incident in this channel: classify the symptom, load the matching triage reference, check lessons.md for known causes, and post a grounded first-pass diagnosis with evidence links and a proposed (never executed) fix. Use when an alert fires, a routine detects a new anomaly, or someone reports something broken ("tests aren't running", "deploys look stuck", "is CI down?").
日本語の概要は準備中です。原文の説明を表示しています。
Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
日本語の概要は準備中です。原文の説明を表示しています。
Build polished, intentional UIs with concrete CSS/Tailwind values — typography, color, layout, spacing, dark mode, accessibility, animations, components. Encodes specific, opinionated rules with exact values, not vague advice. Covers buttons, cards, forms, tables, navigation, dashboards, landing pages, onboarding, and more. Triggers on "absolute ui", "design a UI", "style this component", "make this less like AI slop", "fix the spacing/typography/color", "dark mode", "design a pricing page", "make this look better".
日本語の概要は準備中です。原文の説明を表示しています。
Summarize extracted paper text into concise Markdown memory for later Stage 2 and Stage 4 background use, with fixed section headings and no fabricated claims.
日本語の概要は準備中です。原文の説明を表示しています。
Audit web interfaces against WCAG 2.1 AA/AAA standards, identify violations, and produce actionable remediation reports with code fixes. Use when the user requests accessibility testing or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Histologist. Use when a task calls for Histologist judgment. Reasons from fixation-through-stain pre-analytical chain (NBF, grossing, processing, embedding orientation, microtomy); validates H&E pH/QC, CAP IHC (90% concordance, predictive scoring systems), RNAscope controls, WSI (60-case validation), and treats floaters, autolysis, crush, ice-crystal, and decalcification artifacts as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Food Scientist. Use when a task calls for Food Scientist judgment. Reasons from a_w and GAB isotherms, Maillard/acrylamide kinetics, HLB emulsions, TPA/rheology, ISO sensory methods, and HACCP/FSMA preventive controls while treating aw–moisture conflation, HLB-only emulsion fixes, and Arrhenius misuse as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Computational Social Scientist. Use when a task calls for Computational Social Scientist judgment. Reasons from social mechanisms, measurement validity, and sampling frames through DAGs, fixed-effects and IV/DiD/RDD designs, ERGM/SAOM network models, and human-audited text classifiers while treating unobserved homophily, network interference and SUTVA violations, platform-driven selection, bot contamination, and digital-skew unrepresentativeness as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Differential Geometer. Use when a task calls for Differential Geometer judgment. Reasons from connections, curvature, and holonomy; fixes Lee vs Besse/MTW Riemann signs; uses SageManifolds/xAct/Cadabra, Chern–Weil and Atiyah–Singer index theory, and model-space checks (S^n, flat tori) while treating chart artifacts, torsion misuse, and CAS convention drift as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Carbon Cycle Scientist. Use when a task calls for Carbon Cycle Scientist judgment. Reasons from carbon mass balance across reservoirs and timescales, sign conventions, and budget closure through the Global Carbon Budget protocol, ONEFlux/REddyProc eddy-covariance processing, atmospheric inversions (CarbonTracker, CAMS, GEOS-Chem), Δ¹⁴C/δ¹³C isotopic partitioning, and ILAMB model evaluation while treating NEE sign mismatches, gap-filled GPP read as measured, fixed-depth SOC comparisons, and uncounted lateral aquatic carbon export as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Anatomist. Use when a task calls for Anatomist judgment. Reasons from homology, EPB, and von Baer principles through gross dissection, diceCT/μCT/MRI pipelines, UBERON–PATO EQ annotation, MorphoSource/oVert digitization, geometric morphometrics, and NAV/TA2 nomenclature while treating fixation shrinkage, segmentation artifacts, landmark homology error, and collection bias as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。