Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full legal compliance audit — contracts, policies, regulatory, IP, corporate hygiene. Use when asked to "run a legal audit", "are we legally compliant", or "full compliance review".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write accessibility fixes for specific WCAG failures — ARIA, focus management, keyboard patterns. Use when asked to "fix this accessibility issue", "add ARIA labels", or "make this keyboard navigable".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare API performance across versions — regression detection and root cause analysis. Use when asked "did performance regress", "compare API latency across versions", or "why is this slower".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design detection rules for a threat — SIEM queries, alert logic, and MITRE ATT&CK mapping. Use when asked to "write a detection rule", "how do we detect this attack", or "build a SIEM query for this TTP".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design escalation path -- Tier 1 to Tier 2 to Engineering handoff, decision criteria, and communication templates. Use when asked to "design our escalation process", "when should support escalate to engineering", "build an escalation runbook", or "reduce escalation rate".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design support metrics dashboard -- CSAT, FRT, TTR, ticket deflection rate, volume trends, and agent efficiency. Use when asked to "what metrics should support track", "build our support dashboard", "measure support quality", or "audit our support performance".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Support operations reconnaissance -- audit current ticket volume, SLA compliance, knowledge base coverage, escalation paths, and CSAT to understand where support is the constraint. Use when asked to "audit our support", "why is our response time bad", "how healthy is our support operation", or "before designing a support system".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a WCAG accessibility audit against a component, page, or full product. Use when asked to "run an accessibility audit", "is this WCAG compliant", or "check a11y on this page".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.