1.4万 件 ・ 関連度順
概要と使いどころ
Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says "analyze this page", "check page SEO", "single URL", "check this page", "page analysis", or provides a single URL for review.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when modifying anything under features/files/, app/(core)/files/, app/(public)/share/, or any caller that uploads, downloads, lists, moves, renames, shares, or previews user files.
日本語の概要は準備中です。原文の説明を表示しています。
Recipe for building one focused UI section out for every consumer. Use when asked to 'make this section canonical', 'productize this widget', give it 'the full treatment', or set it up 'like the SEO metadata system', or when building a new analyzer, preview, or calculator section.
日本語の概要は準備中です。原文の説明を表示しています。
RichDocument action toolkit for markdown and interactive content outside live chat. Use when adding an action or content source, wiring a remote action surface, putting actions on a MarkdownStream/BasicMarkdownContent preview, or touching features/rich-document/**, <RichDocument>, <RichDocumentActionSurface>, registerAction, ContentSourceAdapter, or enableContextMenu. NOT for the live chat message bar (use overlay-system).
日本語の概要は準備中です。原文の説明を表示しています。
Continuous localhost UI iteration loop with Arman, through full surface certification. Use when he asks to fix, refine, review, or iterate on a page, route, panel, overlay, or other UI while he may inspect localhost. NOT for a report-only UI audit.
日本語の概要は準備中です。原文の説明を表示しています。
Delegating work down to subagents: briefs, report statuses, independent review. Use when writing an implementer or verifier brief, dispatching a subagent to build, fix, or verify work you own, or a subagent reports DONE, blocked, or concerns. NOT for campaign-scale doctrine (use campaign-pattern).
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end execution of a scouted third-party provider access campaign. Use when a Provider Access Launch task is ready_to_submit or scouted easy_execute and needs account or app registration, scopes, reviewer assets, Vault credential custody, the canonical connection, and real verification.
日本語の概要は準備中です。原文の説明を表示しています。
Follow-up sweep for pending third-party provider access campaigns. Use when the recurring 30-minute Provider Access Launch dispatcher wakes, or for a manual status check of due email threads, developer portals, support cases, or review deadlines.
日本語の概要は準備中です。原文の説明を表示しています。
The bar every automated test or guard must clear: green only when the real system works. Use when writing, fixing, or reviewing a test, mock, stub, fixture, snapshot, or self-test; adding a regression test for a bug; or about to call work done because tests pass.
日本語の概要は準備中です。原文の説明を表示しています。
Early-user discovery and feedback trials. Use when reviewing unfamiliar AI Matrx accounts, classifying owner relationships, recommending trial plans, or running approved outreach and reply checks.
日本語の概要は準備中です。原文の説明を表示しています。
iOS-native mobile web UX rules. Use when building any UI component, fixing mobile issues, reviewing responsive code, or touching viewport heights (dvh vs h-screen), safe areas, Dialog vs Drawer, tabs on mobile, touch targets, or input zoom.
日本語の概要は準備中です。原文の説明を表示しています。
Approved table usage rules. Use when configuring, migrating, or reviewing MatrxDataTable columns, toolbars, or pagination.
日本語の概要は準備中です。原文の説明を表示しています。
Preview a Remotion video
日本語の概要は準備中です。原文の説明を表示しています。
Preview a Remotion video
日本語の概要は準備中です。原文の説明を表示しています。
Apple Human Interface Guidelines for iPhone. Use when building, reviewing, or refactoring SwiftUI/UIKit interfaces for iOS. Triggers on tasks involving iPhone UI, iOS components, accessibility, Dynamic Type, Dark Mode, or HIG compliance.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.
日本語の概要は準備中です。原文の説明を表示しています。
Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.
日本語の概要は準備中です。原文の説明を表示しています。
Best practices for Remotion video creation in React. Use when building, reviewing, or optimizing Remotion compositions, animation timing, assets, captions, and render pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
PR、Story、PLAN、実装成果の初回レビューと再レビューで、現在契約と到達可能な影響範囲からGO／NO-GOを判定する。実装や自由な改善探索には使わない。
認証の追加、ユーザー入力の処理、シークレットの取り扱い、APIエンドポイントの作成、決済/センシティブ機能の実装時に使用。包括的なセキュリティチェックリストとパターンを提供。
ライブラリ非依存のFlutter/Dartコードレビューチェックリスト。ウィジェットのベストプラクティス、状態管理パターン（BLoC、Riverpod、Provider、GetX、MobX、Signals）、Dartイディオム、パフォーマンス、アクセシビリティ、セキュリティ、クリーンアーキテクチャをカバー。
Audits what Claude may do (permission rules, hooks, MCP scope, an agent's grants) and maps what it reaches on disk. Trigger on audit my permissions, why was this allowed, what stalls a routine, swap an allow for a deny, is this hook safe, gate my git pushes, a guard hook or call cap, PowerShell twins of Bash denies, where a rule should live, what is eating my disk, where has Claude been, config drift from a repo copy, skills loading twice; or say gatewarden (audit, harden, explain, scan, hooks, capreview, layout, map, footprint, drift, loads, status, refresh). Installs are trustwarden's; tokens keywarden's; secrets shieldwarden's; standing config rigwright's; agent design agentwright's.
日本語の概要は準備中です。原文の説明を表示しています。
Researches a question to something usable — a verdict with a flip condition, a versioned playbook or a graded report — every claim tagged by evidence. Trigger on which X should I pick (even from pasted pages), is Y worth it, compare A vs B, go/no-go, research this, deep research, fact-check a doc, write or merge a reference guide or playbook, grade a research report, read a bot-blocking source (Reddit, YouTube, X), or map an unfamiliar repo before contributing (entry points, flows, where to change X); or say researchscribe (verdict, playbook, research, verify, sources, map, refresh). Code review is engineering tooling's; fiction canon is lorescribe's; messages commscribe's; prompt model picks promptwright's; skill niches skillwright's; config rigwright's; brands brandscribe's.
日本語の概要は準備中です。原文の説明を表示しています。