1,120 件 ・ 関連度順
概要と使いどころ
Analyse the language demands of a classroom task to identify barriers for EAL and multilingual learners. Use when adapting tasks, planning support, or assessing linguistic accessibility.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinates UDL and differentiation tools through a universal-first hierarchy: barrier removal before targeted differentiation before individualised accommodation. Use when planning accessible learning.
日本語の概要は準備中です。原文の説明を表示しています。
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
日本語の概要は準備中です。原文の説明を表示しています。
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.
日本語の概要は準備中です。原文の説明を表示しています。
Garnish — Craft CMS's built-in JavaScript UI toolkit for the control panel. ALWAYS load when writing, editing, or reviewing JavaScript that runs in the Craft CP — plugin CP assets, custom field type JS, element index JS, CP webpack config, or code importing garnishjs / referencing window.Garnish. Also for CP accessibility, keyboard interactions, drag-sort, and CP JS memory issues.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews shadcn/ui components for CVA patterns, composition with asChild, accessibility states, and data-slot usage. Use when reviewing React components using shadcn/ui, Radix primitives, or Tailwind styling.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews iOS animation code for correctness, performance, accessibility, and Apple API best practices. Use when reviewing .swift files containing animation code — withAnimation, .animation(), PhaseAnimator, KeyframeAnimator, matchedGeometryEffect, navigationTransition, CABasicAnimation, CASpringAnimation, UIViewPropertyAnimator, UIDynamicAnimator, symbolEffect, scrollTransition, contentTransition, or custom Transition conformances.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews SwiftUI code for view composition, state management, performance, and accessibility. Use when reviewing .swift files containing SwiftUI views, property wrappers (@State, @Binding, @Observable), or UI code.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and run manual tests of the project's running app. Runs a session in one of five modes: exploratory, verification, smoke, assessment (UX, localization, accessibility, improvement review), or AI probe. Also writes a manual test plan that holds only what automated tests cannot judge. Use whenever the user asks, in any language, for something to be tested by hand or for a manual test plan — "manual test", "exploratory test", "bug hunt", "verify the bug fix", "smoke test", "QA this screen", "review this screen's UX", "what would you improve", "check the localized copy", "test the AI agent's answers", "write manual test cases", "kịch bản test manual" — or assigns a test design, test plan or test-case IDs to execute by hand. Not for writing automated tests.
日本語の概要は準備中です。原文の説明を表示しています。
AI-powered insights, UX copywriting standards, and user experience guidelines for vehicle insurance platform. Use when designing insight panels, writing user-facing copy, implementing status messages, creating onboarding flows, or improving accessibility. Covers tone standards, interactive patterns, error messages, and empty states.
日本語の概要は準備中です。原文の説明を表示しています。
Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing icons and illustrations in a codebase — find inconsistencies, unoptimized SVGs, and accessibility gaps. Use when asked to "audit our icons and illustrations", "find unoptimized SVGs", or "find inconsistent assets".
日本語の概要は準備中です。原文の説明を表示しています。
Design an icon system spec or audit existing icons for consistency and accessibility. Use when asked to "design an icon system", "audit our icons", or "are our icons consistent".
日本語の概要は準備中です。原文の説明を表示しています。
Expert guide for Web Accessibility (WCAG a11y) and Internationalization (i18n) / Panduan ahli untuk Aksesibilitas Web dan Internasionalisasi.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guide for designing, building, and maintaining scalable UI design systems with design tokens, headless primitives, Material Design 3 (M3), Tailwind v4 @theme, and WCAG 2.2 accessibility.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrator that routes a UI/UX task through brand, tokens, layout, components, polish and accessibility. Use for multi-concern work such as a design review, UI build or interface audit.
日本語の概要は準備中です。原文の説明を表示しています。
Elite frontend design taste for building, reviewing, and polishing web interfaces. Use whenever the user wants to design, redesign, shape, critique, audit, polish, or improve any UI (landing pages, portfolios, dashboards, product UI, components, forms, onboarding, empty states) or asks to make something look better / premium / modern, fix the styling, add or fix animations, or make a design feel less generic ("AI slop"). Covers typography, color, spacing, layout, visual hierarchy, motion, micro-interactions, component states, accessibility, responsive behavior, UX copy, and anti-pattern detection.
日本語の概要は準備中です。原文の説明を表示しています。
Extending propositional and predicate logic with modal operators -- necessity and possibility, and their relatives (obligation, knowledge, belief, time). Covers Kripke possible-worlds semantics, accessibility relations, the main modal systems (K, T, S4, S5), translation from natural language, and applications in epistemic, deontic, and temporal reasoning. Use when ordinary logic is insufficient to capture distinctions like "must" vs "might," "knows" vs "believes," "always" vs "sometimes."
日本語の概要は準備中です。原文の説明を表示しています。
Grammar of graphics, chart type selection, color theory, interactive visualization, dashboards, and the principles of honest, effective data display. Covers Tufte's data-ink ratio, Bertin's visual variables, perceptual principles, accessibility, small multiples, annotation, and the full workflow from exploratory plots to publication-quality graphics. Use when creating charts, designing dashboards, critiquing visualizations, or choosing how to display data.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare your codebase for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates comprehensive documentation (flowcharts, user stories, inline comments). (project, gitignored)
日本語の概要は準備中です。原文の説明を表示しています。
Use when a diff needs four parallel perspective reviewers (Security, Performance, Quality, Accessibility). Creates an ephemeral SAM plan, collects structured verdicts, synthesizes them into one deduplicated cross-referenced punch list, prints one summary line per perspective, and exits non-zero if any perspective returns REJECT. SKIP is a passing outcome.
日本語の概要は準備中です。原文の説明を表示しています。
Review a code change for correctness-maintainability defects not owned by a narrower security/performance/accessibility perspective. Use for an independent quality perspective on a defined change set.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews browser-rendered HTML, CSS, JSX, TSX, JavaScript, and TypeScript for accessibility, XSS, forms, focus, rendering performance, styles, and lifecycle cleanup. Loaded by dh:code-reviewer when source or framework entrypoints establish frontend execution; composes with TypeScript checks.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
日本語の概要は準備中です。原文の説明を表示しています。