テスト設計、脆弱性診断、品質保証（1.3万 件）
Test a changed user interaction for realistic sequence failures such as double submission, stale responses, navigation, and recovery; use for interaction QA rather than general code review.
日本語の概要は準備中です。原文の説明を表示しています。
当管理者犹豫是否留用"还行但不够出色"的员工、想知道何时该让人离开、或团队中有人离开反而让人松了口气时触发。提供基于"留任测试"的决策框架和体面离职流程。
日本語の概要は準備中です。原文の説明を表示しています。
Map requirement acceptance to proportionate executable checks and real user journeys before implementation and completion.
日本語の概要は準備中です。原文の説明を表示しています。
Builds the "Report Sources" child page for a finished Weekly Community Signal report — an evidence-backed defense of WHY every item landed in the column/section/rank it did. The agent argues each placement like a lawyer (claim → evidence → rule → rebuttal) but is under oath: it CANNOT invent, spin, or overstate — every claim ties to a verifiable fact (issue #, label, PR type, quoted comment, npm output, the front-door test). Not CYA — it's so Nathan can defend the report with facts and see the exact reasoning behind each call. Runs after the report (invoked by weekly-report, last steps) and on "report sources", "defend the report", "why is this here".
日本語の概要は準備中です。原文の説明を表示しています。
Enterprise-specific view across CopilotKit + AG-UI. "Enterprise" here = CopilotKit's COMMERCIAL surfaces (Premium / CopilotKit Enterprise / Intelligence Platform / paid tiers), NOT CopilotKit running inside a big company. Tracks the commercial product surfaces (from product-surface-scan — Enterprise Intelligence, Cloud, self-host license, threads/persistence tier, Inspector, premium UI/Angular SDK, analytics, security bundle, Slack/Teams), applies the free-vs-paid classifier to decide if an issue belongs here, surfaces cross-page product contradictions, and tracks enterprise questions/complaints, community-sourced prospects (with a sales owner), and enterprise reporters with prior-week trend. Elevated to the top of the weekly report. Runs standalone ("who's at enterprise this week") or invoked by weekly-report. Triggers on "enterprise report", "enterprise signals", "enterprise status", "who at enterprise this week".
日本語の概要は準備中です。原文の説明を表示しています。
Use when building, testing, and deploying JavaScript/TypeScript applications. Reach for Bun when you need to run scripts, manage dependencies, bundle code, or test applications with a single unified tool.
日本語の概要は準備中です。原文の説明を表示しています。
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
日本語の概要は準備中です。原文の説明を表示しています。
NoteDeck を起動して動作確認する。Tauri デスクトップ / ブラウザ (Dev Dashboard) / E2E の起動手順と起動判定
TDD Red Phase - Activate ONE test from the test list and make it fail with explicit predictions
日本語の概要は準備中です。原文の説明を表示しています。
TDD Test List Phase - Create a comprehensive test list covering every example and rule from the specification
日本語の概要は準備中です。原文の説明を表示しています。
TDD Green Phase - Implement minimal code to make the failing test pass
日本語の概要は準備中です。原文の説明を表示しています。
Generates complete features from natural language — components, API routes, migrations, types, and tests.
日本語の概要は準備中です。原文の説明を表示しています。
Audit project dependencies for known vulnerabilities (CVEs)
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level computer networks covering OSI model, TCP/IP stack, routing protocols, transport layer, application protocols, network security, and software-defined networking.
日本語の概要は準備中です。原文の説明を表示しています。
Frontend UI design, critique, audit, polish. Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Add a tool function to the Medox agent. Use when creating a tool file, registering it in the API loop, and writing its test.
日本語の概要は準備中です。原文の説明を表示しています。
Add a new E2E test case to tests/e2e/prompts.yaml for LangSmith evaluation. Use when adding interaction pairs to test, covering new ANSM drug classes, or rebalancing eval coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Audit code changes on the current branch and update docs/ + .claude/rules/ to stay in sync. Run before /pr.
日本語の概要は準備中です。原文の説明を表示しています。
Guides Quarkus development across REST APIs, CDI dependency injection, Hibernate ORM, Panache, configuration, OpenAPI, templates, messaging, security, observability, packaging, and tooling. Use when building Quarkus applications, adding endpoints or clients, configuring datasources or OIDC, debugging build or runtime issues, or choosing extensions.
日本語の概要は準備中です。原文の説明を表示しています。
Audit datasets, joins, labels, and ground truth before analysis or modeling. Use when data meaning, row grain, time semantics, source-of-truth reliability, or label construction may invalidate conclusions; not for general model evaluation after the evidence base is already trusted.
日本語の概要は準備中です。原文の説明を表示しています。
Measure, root-cause, fix, verify and record performance contention on a developer machine: cloud-sync daemons (iCloud Drive, OneDrive, Dropbox, Google Drive), file indexers, AI-tool MCP server fleets, and automation browsers left behind by tests and browser skills. Trigger when the machine is slow, apps freeze, browser or MCP tool calls time out, load exceeds the core count, or before and after any UI/UX/performance test run. Includes the L0–L4 optimisation scale and the test-hygiene contract.
日本語の概要は準備中です。原文の説明を表示しています。
Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.
日本語の概要は準備中です。原文の説明を表示しています。
Measure real frontend performance — Core Web Vitals (LCP, CLS, INP), page-load traces, CPU and network throttling, Lighthouse accessibility/SEO scores, and heap growth — using chrome-devtools-mcp against a live browser. Trigger when asked "is the page fast enough", "measure Core Web Vitals", "why is this route slow", "run Lighthouse", "check for a memory leak", before any performance-gated certification (Built for Shopify, Core Web Vitals thresholds, store listing review), and before any launch or traffic-multiplier event. Measurement only — this skill never drives functional journeys.
日本語の概要は準備中です。原文の説明を表示しています。