Internal legal controls review — approval workflows, contract lifecycle, access to sensitive docs. Use when asked to "audit our controls", "review approval workflows", or "who can access sensitive contracts".
日本語の概要は準備中です。原文の説明を表示しています。
Design customer support onboarding flow -- first-contact experience, proactive support touchpoints, and setup success checklist. Use when asked to "design our onboarding support", "how do we support new customers during onboarding", or "reduce early churn from setup failures".
日本語の概要は準備中です。原文の説明を表示しています。
Survey the project's existing contracts and policy docs. Use when asked "what contracts do we have", "survey our policy docs", or "inventory our agreements".
日本語の概要は準備中です。原文の説明を表示しています。
Developer relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event strategy, and success metrics. Use when asked to "build a DevRel program", "design our developer community", "create a contributor program", "start a developer advocacy program", or "how do we grow our dev community".
日本語の概要は準備中です。原文の説明を表示しています。
Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program".
日本語の概要は準備中です。原文の説明を表示しています。
Map AI cost topology — billing attribution, team-level spend, forecast vs actuals, alert gaps. Use when asked to "map our AI spend", "who is spending on LLMs", or "set up AI cost attribution".
日本語の概要は準備中です。原文の説明を表示しています。
Design cost reduction strategies — model tiering, prompt compression, caching, batch inference. Use when asked to "reduce our AI costs", "set up model tiering", or "cut LLM spend".
日本語の概要は準備中です。原文の説明を表示しています。
Audit AI spend — per-model cost breakdown, top consumers, waste identification, optimization levers. Use when asked "why is our AI bill so high", "audit LLM spend", or "where is our token waste".
日本語の概要は準備中です。原文の説明を表示しています。
Review and redline a contract — flag risk, missing clauses, one-sided terms. Use when asked to "review this contract", "redline this agreement", or "is this contract risky".
日本語の概要は準備中です。原文の説明を表示しています。
Draft a contract or policy document from a description or template. Use when asked to "draft an NDA", "write an MSA", or "we need a vendor contract".
日本語の概要は準備中です。原文の説明を表示しています。
Design ticket triage system -- routing rules, priority tags, queue structure, and first-response automation. Use when asked to "design our ticket routing", "how should we tag tickets", "set up our helpdesk", or "reduce time to first response".
日本語の概要は準備中です。原文の説明を表示しています。
Design SLA framework -- response time targets, resolution time targets, tier definitions, and breach escalation process. Use when asked to "define our SLAs", "what response times should we commit to", "build a support tier structure", or "set up SLA monitoring".
日本語の概要は準備中です。原文の説明を表示しています。
Build or audit knowledge base -- article structure, coverage gaps, deflection rate, and maintenance process. Use when asked to "build a knowledge base", "what docs are missing", "improve our self-serve rate", or "audit our help center".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing security controls and detection coverage — find gaps against MITRE ATT&CK. Use when asked to "audit our detection coverage", "where are our security control gaps", or "check our MITRE coverage".
日本語の概要は準備中です。原文の説明を表示しています。
Write a hardening playbook for a system or service — CIS benchmark mapping and implementation steps. Use when asked to "harden this server", "apply the CIS benchmark", or "write a hardening playbook".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing compliance artifacts — policies, audits, certifications. Use when asked "what compliance docs do we have", "survey our policies", or "inventory our compliance artifacts".
日本語の概要は準備中です。原文の説明を表示しています。
Draft compliance policies required by a framework (access control, incident response, data retention). Use when asked to "write an access control policy", "draft our incident response policy", or "we need a data retention policy".
日本語の概要は準備中です。原文の説明を表示しています。
Run a compliance gap analysis against SOC2, GDPR, HIPAA, or ISO 27001. Use when asked "are we SOC2 ready", "run a GDPR gap analysis", or "what is missing for ISO 27001".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing performance testing — find missing benchmarks, stale baselines, and CI gaps. Use when asked "do we have benchmarks", "audit our performance testing", or "are our baselines stale".
日本語の概要は準備中です。原文の説明を表示しています。
Survey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues. Use when asked "how accessible is our codebase", "find accessibility debt", or "where are our a11y gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports. Use when asked to "write an ADR", "map the architecture", "document this decision", "onboarding docs", or "what changed".
日本語の概要は準備中です。原文の説明を表示しています。
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
日本語の概要は準備中です。原文の説明を表示しています。
Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".
日本語の概要は準備中です。原文の説明を表示しています。
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。