テスト・セキュリティのスキル

Builds, audits and packages Agent Skills, with their evals. Trigger to build, audit (security too), score or package a skill or SKILL.md; to design or integrate a pack; whether a skill beats incumbents; for trigger evals, test cases or assertion suites (skill, prompt card, agent spec); to slim a skill; when a skill did not fire or a run cost too much; for a prose pass on a skill's own files; to port or sanitize a skill set; to build or contract-test the MCP tools a plugin or mod ships; or say skillwright (evals, slim, diagnose, mcp, refresh, port, pack, integrate, upkeep). Prompt tuning is promptwright's; running a suite, claude plugin eval's; config slims, rigwright's; other docs, commscribe's; brands, brandscribe's; runtime grants, gatewarden's.

日本語の概要は準備中です。原文の説明を表示しています。

Runs a session's fan-out — splits a large request into tiered, recoverable units, dispatches and reconciles them against the repo. Trigger when work needs many agents or spans many repos or files (rebuild, re-architect, sweep, migrate, 'do all of this'); when subagents would launch with no model or effort set; for the plan table (units, models, tokens, meters) before launch; to resume a unit that died or hit a usage limit; when units would share a repo; or say dispatchwright (plan, dispatch, resume, audit, refresh). Tiers come from its own table (scoutwright flags it stale); pacing, pacewright's; hooks, rigwright's; schedules, agentwright's.

日本語の概要は準備中です。原文の説明を表示しています。

Designs, hardens and audits the system around an agent that runs on its own — bot, scheduled task, routine, automation — all but the prompt text. Trigger for guardrails, kill switches, cadence and loop pacing (cron, wake, /loop), retries and failures, output contracts, protected resources, handoffs between agents, or isolating untrusted email and web content; to emit a spec as a Cowork task, routine, scheduled task or CI job; or say agentwright (emit, audit, refresh); it never schedules or runs one. Prompt text is promptwright's; CLAUDE.md, rigwright's; skills, skillwright's; runtime grants and credentials, gatewarden's scan; code threats, a security harness's.

日本語の概要は準備中です。原文の説明を表示しています。

Decides where a standing rule lives and builds the config Claude reads before work — CLAUDE.md, AGENTS.md, Project instructions and knowledge files, profile preferences, .claude/rules and agents, hooks, .mcp.json. Trigger on 'where should this rule live', 'set up a Claude Project', 'write or trim my CLAUDE.md', 'my rules get ignored', 'audit my setup for bloat or stale status', 'cut my CLAUDE.md token cost', 'add what we learned to CLAUDE.md', or rigwright (place, build, audit, learn, slim, refresh). Permissions, hook safety and config maps are gatewarden's; skills, skillwright's; unattended work, agentwright's; a block's wording, promptwright's.

日本語の概要は準備中です。原文の説明を表示しています。

Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, components, and AI-generated code. Use when reviewing code that touches user data, PII, or access control, or before any deploy of an app with auth.

日本語の概要は準備中です。原文の説明を表示しています。

Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.

日本語の概要は準備中です。原文の説明を表示しています。

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

日本語の概要は準備中です。原文の説明を表示しています。

Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.

日本語の概要は準備中です。原文の説明を表示しています。

Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories. Use when running convex-doctor, fixing convex-doctor warnings or errors, improving the convex-doctor score, or when asked about Convex code quality, static analysis, or linting Convex functions.

日本語の概要は準備中です。原文の説明を表示しています。

Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.

日本語の概要は準備中です。原文の説明を表示しています。

Convex code reviewer — security, auth, validators, performance, and pattern checks for code in a convex/ directory. Use to review or audit Convex functions before shipping.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and harden a Convex app's authorization: identity-from-arg impersonation, missing per-document ownership checks, public queries leaking data by a client-supplied id, and writes into a parent/container the caller doesn't own. Scans for the 4 shapes, applies requireIdentity/requireOwner, verifies with tsc. TRIGGER on 'secure my app', 'audit auth/authz', 'who can access this data'. SKIP when there is no convex/ directory.

日本語の概要は準備中です。原文の説明を表示しています。

Generate convex-test tests for the app's Convex functions.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and optimize an existing Convex app: security, scale, upgrades, observability.

日本語の概要は準備中です。原文の説明を表示しています。

Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.

日本語の概要は準備中です。原文の説明を表示しています。

Prove a Convex feature works — seed, drive as multiple mocked users via convex-test, assert behavior including the negative authz cases (wrong user refused, data-scope enforced).

日本語の概要は準備中です。原文の説明を表示しています。

Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, and AI-generated code. Use when reviewing code that touches user data, PII, or access control.

日本語の概要は準備中です。原文の説明を表示しています。

Use when adding or repairing Spark regression tests for asynchronous ownership, cancellation, persistence, restart recovery, or cross-surface projections. Not a coverage campaign, performance benchmark, source-text policy check, or full delivery review.

日本語の概要は準備中です。原文の説明を表示しています。

Use when GitHub may have shipped a GraphQL schema update affecting timeline event unions (PullRequestTimelineItems / IssueTimelineItems), when the gh-timeline dispatcher fallback is hitting more than expected, before a gh-timeline release, or when the user requests phrases like "verify timeline coverage", "audit gh-timeline schema", "check for new timeline events", "GitHub schema changed". Walks through schema diff → patch → test update → live verification → optional fixture refresh, marking each spot where a human decision is required.

日本語の概要は準備中です。原文の説明を表示しています。

macOS アプリのクラッシュログ (.ips) を解析し、根本原因を特定するスキル。「クラッシュした」「crash」「.ips」「DiagnosticReports」「SIGSEGV / SIGABRT」で発火。**macOS 専用**（.ips の読み方が macOS の DiagnosticReports 前提。iOS の .ips は未対応）。解析は crash-analyzer subagent に委譲する。クラッシュログが存在しない一般のバグ調査・テスト失敗には使わない。

プロジェクト監査。「監査して」「audit」「/audit」で発火。設計/UX/品質/テストなどの観点でコードベース全体を監査し、課題をissuesディレクトリに書き出す。実行ログで重複実行を防止。特定の差分・コミットのレビューには使わない（codex-review / cross-review を使う）。