テスト設計、脆弱性診断、品質保証（1.4万 件）
Build or audit compliance program — SOC2, GDPR, HIPAA, or ISO 27001 readiness assessment, gap analysis, and remediation roadmap. Use when asked to "do we need SOC2", "are we GDPR compliant", "what does our compliance program need", or "build a security policy".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing typography in a codebase — find inconsistencies, hardcoded sizes, and hierarchy gaps. Use when asked to "audit our typography", "find hardcoded font sizes", or "our type is inconsistent".
日本語の概要は準備中です。原文の説明を表示しています。
Manage vendor relationships — vendor selection scorecard, contract review checklist, renewal tracking, and vendor consolidation audit. Use when asked to "evaluate this vendor", "review this contract", "track vendor renewals", or "reduce our SaaS spend".
日本語の概要は準備中です。原文の説明を表示しています。
Operations reconnaissance — audit process documentation, vendor contracts, compliance posture, OKR health, and cross-functional friction points to understand where operations is the bottleneck. Use when asked to "audit our operations", "where are we slow", "what processes are broken", or "before designing a compliance program".
日本語の概要は準備中です。原文の説明を表示しています。
Local SEO audit — assess a location-based business's Google Business Profile against local competitors, check Maps and local-pack visibility for its main queries, and recommend the few fixes that win nearby searches. Use when asked to "improve our local SEO", "why don't we show up on Google Maps", "audit our Google Business Profile", "rank in the local pack", or "local search for [city]".
日本語の概要は準備中です。原文の説明を表示しています。
Audit or refactor a design token system for color — naming, structure, and coverage. Use when asked to "refactor our color tokens", "fix color token naming", or "improve token coverage for color".
日本語の概要は準備中です。原文の説明を表示しています。
Audit or redesign responsive behavior of a layout — breakpoints, reflow, and content priority. Use when asked to "fix responsive behavior", "define breakpoints", or "how should this reflow on mobile".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing layout patterns in a codebase — find ad-hoc spacing, inconsistent grids, and missing primitives. Use when asked to "audit our layout patterns", "we have ad-hoc spacing everywhere", or "our grids are inconsistent".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing API quality controls — find missing lint rules, gaps in CI gates, and quality debt. Use when asked to "audit our API quality controls", "find missing lint rules", or "assess our API governance".
日本語の概要は準備中です。原文の説明を表示しています。
Expert 5-dimension design critique — philosophical, scored, actionable. Use when asked to "critique this design", "expert review", "score my design", "how does this look", "is this good design", "design feedback", or "review this UI". Different from /form-audit (which is technical QA for consistency/compliance) — form-critique evaluates design as a craft object: philosophy, hierarchy, execution, function, and innovation each scored 0–10 with a punch list. Add "as a report" or "give me a visual report" to produce an HTML file with SVG radar chart, evidence cards, and Keep/Fix/Quick-wins action lists — useful for design reviews and stakeholder presentations instead of CLI output.
日本語の概要は準備中です。原文の説明を表示しています。
People reconnaissance - audit org design, hiring pipeline, comp structure, onboarding, and performance systems to understand what is working and where the constraint is. Use when asked to "audit our people ops", "what is broken in our hiring", "review our org structure", or "before designing a comp framework".
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to audit UI for visual quality, check design consistency, review brand alignment, evaluate design system compliance, or find visual issues before a launch. Examples: "audit our UI", "check visual consistency", "review the design for issues", "is our UI on-brand", "find visual bugs", "design QA before launch".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing model training code — find reproducibility issues, data leakage, and missing best practices. Use when asked to "audit our training code", "is our training reproducible", or "check for training data leakage".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing infrastructure for security issues, waste, and misconfigurations. Use when asked to "audit my infra", "check cloud setup", "infra review", "are we wasting money", "security check on infra", or "review my terraform".
日本語の概要は準備中です。原文の説明を表示しています。
Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".
日本語の概要は準備中です。原文の説明を表示しています。
Run human-to-agent migration - audit which roles can be agent-assisted or replaced, design the transition playbook, and manage the offboarding of displaced roles. Use when asked to "which roles can agents replace", "how do we transition to AI-first ops", or "build our agent migration plan".
日本語の概要は準備中です。原文の説明を表示しています。
Theory-backed design audit — names the principle violated, cites the source, shows the fix. Use when asked to "evaluate design quality", "check if this follows design principles", "theory check", "design exam", "audit against best practices", or "what's wrong with this design".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing cloud cost controls — tagging coverage, alerting, and FinOps maturity. Use when asked to "audit our cost controls", "is our tagging complete", or "assess our FinOps maturity".
日本語の概要は準備中です。原文の説明を表示しています。
Audit cloud spend — identify waste, rightsizing opportunities, and reservation gaps. Use when asked "our cloud bill is too high", "find cloud waste", or "where can we rightsize".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing ML monitoring — find gaps in drift coverage and missing alerts. Use when asked to "audit our ML monitoring", "are our models monitored", or "find drift coverage gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Design or audit a feature store — serving, freshness, and sharing across models. Use when asked "do we need a feature store", "design a feature store", or "share features across models".
日本語の概要は準備中です。原文の説明を表示しています。
Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Audit feature engineering code for leakage, quality issues, and pipeline correctness. Use when asked to "audit our feature pipeline", "is there data leakage", or "find feature quality issues".
日本語の概要は準備中です。原文の説明を表示しています。