3,380 件 ・ 関連度順
概要と使いどころ
Visible browser automation using Playwright MCP, CLI, and CDP without interrupting the user's foreground work. Use for navigation, forms, screenshots, durable file downloads, repeatable browser workflows, existing-session reuse, or troubleshooting CDP / iframe / modal / file chooser / passkey (WebAuthn) issues.
日本語の概要は準備中です。原文の説明を表示しています。
Socratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited. Leads you to see the issues through questions, names smells and moves precisely, then closes with a concrete plan.
日本語の概要は準備中です。原文の説明を表示しています。
命理圆桌会——多流派命理师（盲派、子平格局派、调候派、民国新派）对同一八字命盘进行圆桌论命：多视角总评、交叉质疑、可证伪断语、逐轮记分复盘。用户提到八字、四柱、命盘分析、批命、论流年大运、盲派/格局/调候论命、"多个命理师讨论"、验证式论命时使用本 skill；即使用户只是贴出一张八字排盘求分析，也应启用（可用轻量模式）。Multi-school Chinese BaZi (Four Pillars) roundtable reading: several fortune-tellers from rival schools analyze the same natal chart, cross-examine each other, issue falsifiable predictions, and keep score. Use whenever the user asks about BaZi, Four Pillars, Chinese astrology chart reading, or destiny analysis.
日本語の概要は準備中です。原文の説明を表示しています。
"Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Kingdon's multiple streams framework to analyze how problems, policies, and politics converge to open policy windows. Use this skill when the user needs to explain why certain policies get adopted while others don't, identify policy windows and entrepreneurial opportunities, or analyze the agenda-setting process in public policy — even if they say 'why did this policy pass now', 'policy window', or 'how do issues get on the agenda'.".
日本語の概要は準備中です。原文の説明を表示しています。
Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.
日本語の概要は準備中です。原文の説明を表示しています。
Profile and explore a dataset to understand its shape, quality, and patterns. Use when encountering a new table or file, checking null rates and column distributions, spotting data quality issues like duplicates or suspicious values, or deciding which dimensions and metrics to analyze.
日本語の概要は準備中です。原文の説明を表示しています。
Security testing checklist for HTTP APIs—authn/z, input validation, rate limits, sensitive data exposure, and common OWASP API issues. Use when reviewing or testing REST/GraphQL endpoints before release.
日本語の概要は準備中です。原文の説明を表示しています。
"Optimize Core Web Vitals (LCP, INP, CLS) for better search rankings and user experience. Use this skill when the user needs to diagnose page speed issues, improve Largest Contentful Paint, reduce layout shift, or pass Google's page experience signals — even if they say 'my site is slow', 'Core Web Vitals failing', or 'page speed optimization'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Optimize e-commerce search relevance across the full pipeline from query understanding to result presentation. Use this skill when the user needs to improve search quality, implement query processing features, or diagnose search relevance issues — even if they say 'search results are bad', 'improve product search', or 'search relevance optimization'.".
日本語の概要は準備中です。原文の説明を表示しています。
Auto-activates when analyzing GitHub issues to extract functional requirements, non-functional requirements, acceptance criteria, and user stories.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze story dependencies, detect issues, and generate visual dependency graphs
日本語の概要は準備中です。原文の説明を表示しています。
Triage, fix, and pre-flight a PR before merge. Checks mergeability, CI, reviews, and bot comments — fixes issues, runs /pre-commit before pushing, then hands off to /pr-merge.
日本語の概要は準備中です。原文の説明を表示しています。
Fast spec-driven implementation from a committed spec. Use after /spec to implement an issue with a phase roadmap, TDD waves, map patching, review, and pre-commit validation.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze feature requirements, dependencies, and security considerations. Use when starting feature implementation from GitHub issues to understand scope, technical feasibility, and risks.
日本語の概要は準備中です。原文の説明を表示しています。
Write a durable feature spec before touching code. Reads the codebase map, reads related models/migrations to ask technical questions (not generic ones), then produces a structured spec doc in docs/specs/. Designed to pipeline with /implementation --issue N. Use before any feature implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Works through the surviving mutants that cargo-mutants reports for packages/engine — classify each one as a real test gap, a mutant not worth killing, or dead code, then fix it and verify with `just mutants-diff`. Use when picking up the weekly "Mutatietesten" issue, when asked to improve engine test coverage, or when a pull request fails the Mutation Testing (diff) gate.
日本語の概要は準備中です。原文の説明を表示しています。
Processes all open Dependabot PRs sequentially — rebases if needed, analyzes for breaking changes and security issues, then merges or requests changes. Use when you want to handle pending Dependabot dependency updates.
日本語の概要は準備中です。原文の説明を表示しています。
Review a diff, commit, branch, PR, or implementation for actionable correctness and risk issues without duplicate reviewer loops or invented findings.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct structured root cause analysis using Ishikawa (Fishbone), 5 Whys, and Pareto methods. Suitable for production incidents, quality defects, customer complaints, and recurring operational problems. Use when problems recur or when initial fixes do not resolve the issue. Do not use for one-time, obvious fixes or strategic decision-making.
日本語の概要は準備中です。原文の説明を表示しています。
Build multi-project RAID and RAG views for portfolios, programs, or cross-functional workstreams. Use when PMOs, program managers, or leaders need a real status picture across milestones, dependencies, owners, and escalations. Do not use for a single standup note, one issue ticket, or generic meeting minutes.
日本語の概要は準備中です。原文の説明を表示しています。
Write structured legal memoranda following the Issue-Rule-Analysis-Conclusion (IRAC) framework. Suitable for internal legal opinions, advisory memos, and compliance assessments. Use when legal analysis needs to be documented for decision-makers. Do not use as a substitute for licensed legal advice on high-stakes matters.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize support tickets, chats, and customer threads into issue, impact, status, owner, and next response. Use for customer service handoffs, escalation triage, and support backlog review.
日本語の概要は準備中です。原文の説明を表示しています。
Audit data quality across six DAMA DMBOK dimensions — Completeness, Accuracy, Consistency, Timeliness, Validity, Uniqueness. Produces a scored data quality report with issue log and remediation plan. Use when profiling datasets, onboarding new data sources, or building data quality gates.
日本語の概要は準備中です。原文の説明を表示しています。