simota.
103 skills across 1 repo
- 100/100
accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
- 100/100
agora
Designing learning and curriculum content. Authors measurable objectives, prerequisite checks, curriculum maps, lesson plans, materials, quizzes, assessment rubrics, and coaching support — aligning objectives/content/assessment via Bloom's taxonomy + backward design. No code. Use when designing curricula. Not for technical specs (Scribe), QA cases (Matrix), or diff-to-doc (Tome).
- 100/100
anvil
Building terminal UIs, CLI tools, and dev-tool integrations (linter/test-runner/build-tool wiring). Use when CLI/TUI design or implementation is needed. Language-agnostic — supports Node.js, Python, Go, and Rust.
- 100/100
artisan
Implementing production frontend code for React/Vue/Svelte. Handles hooks design, state management, Server Components, form handling, and data fetching. Converts Forge prototypes to production-quality code.
- 100/100
ascent
Planning career strategy for job change/side-business/independence. Owns self-analysis, market & salary research, positioning, skill-gap plans, job search (target lists, tracker, outreach), interview prep, and salary negotiation. Advisory only — no code. Use when planning career moves. Not for engineer SNS branding (Crest), UX research (Field), or product competitive (Compete).
- 100/100
atelier
Orchestrating design-to-implementation pipelines (code-to-visual-to-code closed loop). Persists a project design system across downstream agents. Use when a request spans design extraction, prototypes, visual assets, slides, and production together. Not for single-token tweaks (Muse), single prototype (Forge), direction only (Vision), or generic orchestration (Nexus).
- 100/100
atlas
Analyzing dependencies, circular references, and God Classes; authoring ADRs/RFCs. Use for architecture improvement, module decomposition, and technical debt assessment.
- 100/100
attest
Verifying spec compliance by extracting ACs from specs, adversarially checking implementation conformance, and generating BDD scenarios, traceability matrices, and evidence-based compliance reports. No code. Use when verifying impl matches spec (PRD/SRS/AC) or producing machine-adjudicated conformance proof for a PR.
- 100/100
bazaar
Orchestrating super-premium landing-page studio chains. Orchestrates the full LP pipeline (Discover → Audience → Strategy → Structure → Design → Build → Optimize → Verify → Launch) across 6 craft axes (Design/Animation/Branding/Marketing/SEO/IA) with explicit rubrics and quality gates. Use when a request asks for a complete, conversion-tuned, brand-defining LP. Not for single LP section (Funnel), design-only pipeline (Atelier), product-wide build (Titan), generic orchestration (Nexus), or A/B execution (Experiment).
- 100/100
beacon
Engineering observability and reliability through SLO/SLI design, distributed tracing, alerting, dashboards, capacity planning, toil automation, and reliability review. Use when designing observability instrumentation, defining SLOs/SLIs, building dashboards/alerts, or reviewing reliability posture.
- 100/100
bolt
Optimizing frontend (re-render reduction, memoization, lazy loading) and backend (N+1 fix, indexing, caching, async) performance, including continuous auto-tuning loops (profile → parameter → optimize → verify for GC/threadpool/pool/cache/worker settings — absorbed from dial). Use when one-shot speed improvement or continuous tuning is needed.
- 100/100
bond
Designing retention strategy, re-engagement, and churn prevention. Covers retention analysis frameworks, re-engagement trigger design, gamification elements, habit formation design, and loyalty programs. Use when engagement tactics are needed.
- 0/100
breach
Designing red team attack scenarios, building threat models, applying MITRE ATT&CK/OWASP frameworks, running Purple Team exercises, and performing AI/LLM red teaming. Use when adversarial security validation is needed.
- 95/100
builder
Implementing robust business logic, API integrations, and data models with type safety and production readiness. Use when business logic implementation or API integration is needed. Offers an interactive pair-programming mode (co-implement, confirming each increment).
- 100/100
canon
Assessing standards compliance and analyzing gaps. Evaluates codebases against OWASP/WCAG/OpenAPI/ISO 25010 standards, detects violations, provides actionable remediation with citations. Use when checking industry-standard compliance (security/a11y/API/quality) or producing citation-backed audit reports.
- 100/100
cast
Casting personas via rapid generation, persistence, lifecycle management, and inter-agent sync. Generates personas from diverse inputs, manages via a registry, evolves data-driven, and distributes in unified format. Use when creating, updating, or syncing personas across agents. Not for UI walkthroughs (Echo) or user research design (Field).
- 100/100
clause
Reviewing legal documents for Terms of Service, Privacy Policy, and Tokushoho compliance. Detects clause gaps, flags risks, and aligns regulatory requirements. Don't use when legal advice is needed — consult a lawyer.
- 100/100
cloak
Engineering privacy and data governance via PII detection, data flow mapping, consent management patterns, GDPR/CCPA-compliant code implementation, and DPIA facilitation. Use when privacy-by-design implementation is needed.
- 100/100
compass
Navigating the skill ecosystem and guiding onboarding. Lists agents, recommends best fit for tasks. Don't use for task execution (Nexus), agent design (Architect).
- 100/100
compete
Researching competitors, analyzing differentiation, and shaping strategic positioning. Covers feature matrices, SWOT, benchmarking, positioning maps, battle cards, win/loss, and LLM brand visibility. Research only — no code. Use when scoping competitive landscape, building positioning artifacts, or assessing LLM brand visibility.
- 100/100
crest
Building engineer self-branding by transforming technical contributions into a professional brand. Use when GitHub/LinkedIn/blog/conference/SNS positioning, profile optimization, or content strategy is needed.
- 80/100
crypt
Designing cryptographic architecture: algorithm selection, key management, E2EE, KMS integration, signature verification, and TLS configuration. Use when designing cryptographic protocols, key rotation flows, or end-to-end encryption architectures.
- 100/100
cue
Writing video scripts, storyboards, and narration designs. Used for product videos, explainer videos, and onboarding content planning.
- 100/100
cull
Scanning supply-chain malware infections via IoC-based local scan + safe eradication for npm/PyPI worm campaigns (Shai-Hulud, S1ngularity, lottie-player). Detects OS persistence (LaunchAgent/systemd), IDE-hook implants (.claude/.vscode/.github/workflows), lockfile-pinned malicious versions, and C2/exfil traces. Sequences credential rotation so revocation does not trigger `rm -rf ~/` retaliation payloads. Use when worm infection is suspected. Not for SAST (Sentinel), skill/MCP audit (Chain), Sigma/YARA (Vigil), or incident coordination (Triage).
- 100/100
darwin
Orchestrating ecosystem self-evolution by detecting project lifecycle phases, evaluating agent relevance, synthesizing cross-agent knowledge, and proposing evolution actions (health checks, fitness scoring, structural proposals). Use when auditing skill-ecosystem health, scoring agent fitness, or proposing structural evolution.
- 100/100
dot
Generating pixel art as code (SVG/Canvas/Phaser 3/Pillow/CSS). Also supports SVG generation delegation to Antigravity CLI. Use when generating pixel-art assets as code, building retro/8-bit visuals, or composing sprite sheets and tile maps for games.
- 100/100
field
Conducting user research via interview guides, usability test plans, qualitative data analysis, persona creation, and journey mapping. Complements Echo's UI validation. Use when user research design or analysis is needed.
- 100/100
flow
Implementing CSS/JS animations for hover effects, loading states, modal transitions, and gesture interactions. Use when adding meaningful motion, improving interaction feedback, or implementing performance-safe animations.
- 100/100
flux
Refracting thinking by challenging assumptions, combining cross-domain knowledge, and shifting perspectives to reframe problems. Use when breaking through stuck situations or paradigm shifts are needed. Does not write code.
- 100/100
funnel
Constructing landing pages end-to-end via structure design, conversion strategy, CTA optimization, and responsive design. Use when creating or improving landing pages.
- 100/100
gauge
Auditing SKILL.md normalization and self-evolving compliance. Scans SKILL.md files against the 19-item checklist, classifies violations, produces fix snippets, and researches emerging best practices. No code. Use when auditing SKILL.md compliance, generating fix recommendations, or running ecosystem health dashboards.
- 20/100
gear
Managing dependencies, CI/CD optimization, Docker configuration, and operational observability (logging/alerting/health checks). Use when build errors, dev environment issues, or operational config fixes are needed.
- 100/100
glance
Designing game UI/UX (no code) — HUD & diegetic UI, menu/inventory flow, controller & console navigation, game accessibility, and genre UI conventions. Don't use for app/web UX (Palette), art direction (Vision), game systems design (Quest), or UI implementation (Tick/Artisan).
- 100/100
grok
Designing regex, parsers, and DSLs for grammar authoring and ReDoS-safe regex. Not for REST APIs (Gateway) or DB schemas (Schema).
- 100/100
grove
Designing, optimizing, and auditing repository structure. Covers directory design, docs/ layout (PRD, specs, ADR), test/script organization, anti-pattern detection, and migration planning for existing repositories.
- 100/100
growth
Optimizing SEO (meta/OGP/JSON-LD/heading hierarchy), SMO (social sharing), CRO (CTA/form/exit-intent), and GEO (AI citation optimization) across four pillars. Use when search ranking, conversion, or AI visibility improvement is needed.
- 100/100
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.
- 100/100
guild
Designing hiring processes and team structure (employer side). Produces recruitment strategy, job descriptions, competency matrices, interview rubrics, scorecards, outreach templates, candidate-journey maps, 30/60/90 onboarding, performance reviews, culture docs, and bias-reduction checklists. Does not write code; flags labor-law content for professional review. Use when designing the hiring process or team structure. Not for regulatory audit (Oath), persona generation (Cast), candidate side (Ascent), or engineer personal branding (Crest).
- 100/100
hearth
Generating, optimizing, and auditing personal development environment config files (zsh/tmux/neovim/ghostty). Use when dotfile management, shell, terminal, or editor configuration is needed.
- 100/100
helm
Simulating business strategy via short/mid/long-term scenario planning from financial, market, and competitive data. Applies SWOT/PESTLE/Porter analysis, KPI forecasting, and strategic roadmap generation. Does not write code.
- 100/100
hone
Auditing and optimizing AI CLI configuration. Audits Codex CLI (~/.codex/), Antigravity CLI (~/.gemini/ — `agy`), and Claude Code (~/.claude/) configs (config.toml/settings.json/CLAUDE.md/hooks/MCP) and proposes Before/After diff improvements. Never edits configs directly. Use when auditing AI CLI configs, optimizing prompt cache hierarchy, or reviewing hooks/MCP/plugins security posture.
- 100/100
ink
Generating SVG icons/illustrations, designing icon systems, and constructing sprite symbols. Use when vector assets are needed.
- 100/100
judge
Reviewing code via multi-engine orchestration. Orchestrates parallel review via subagents with grounding verification, shipping only findings worth fixing. Reviews on three axes — secure, correct, and lean. Default Claude + Codex (dual-engine); agy optional third axis. Use for PR review or pre-commit checks — detects bugs, vulnerabilities, logic errors, waste, and intent misalignment. Offers an interactive pair-review mode (fix-as-you-go). Complements Zen refactoring.
- 80/100
latch
Proposing, configuring, debugging, and maintaining Claude Code hooks (PreToolUse/PostToolUse/Stop and other lifecycle events). Use when workflow automation, quality gates, or security enforcement via hooks is needed.
- 100/100
ledger
Optimizing FinOps and cloud costs. Cost estimation from IaC, right-sizing, RI/SP recommendations, anomaly detection, budget alerts, AI/GPU workload cost analysis. Use when forecasting cloud spend, optimizing instance/reservation mix, designing budget alerts, or modeling AI/GPU economics.
- 100/100
lens
Comprehending and investigating codebases. Systematically performs structure mapping, feature discovery, and data flow tracing for "does X exist?", "how does Y work?", or "what is this module's responsibility?". Includes a conversational Q&A mode ("ask") for navigator-style, multi-turn questions about a project. Does not write code.
- 100/100
loom
Designing a project's operating layer — the blueprint of which project-local skills, repo-tailored recipes (task playbooks), and skill-and-agent orchestration workflows a repository needs, designed together as a coherent system. Analyzes the repo, designs the layer, then delegates skill-body authoring to Sigil and runtime routing to Nexus. Use when a repository needs a coordinated set of project agents, recipes, and orchestration workflows designed together. Don't use for authoring a single skill body (Sigil), runtime request orchestration (Nexus), autonomous loop runners (Orbit), application or business-process workflows and code-level state machines (Weave), or ecosystem-wide global agents (Architect).
- 80/100
mend
Remediating known failure patterns automatically. Receives Triage diagnoses and Beacon alerts, executes runbooks with safety-tier classification, staged verification, and rollback. Use when automated incident remediation is needed.
- 100/100
mint
Generating test data and fixtures. Use when factory pattern design, boundary value data generation, synthetic data generation, or seed data management is needed.
- 100/100
morph
Converting document formats (Markdown/Word/Excel/PDF/HTML). Converts specs from Scribe and reports from Harvest into distributable formats; generates reusable conversion scripts. Use when converting documents, building accessibility-compliant PDFs, or creating Pandoc/LibreOffice pipelines.
- 100/100
muse
Defining and managing design tokens, applying token systems to existing codebases, and building design system foundations. Covers token architecture for spacing, color, typography, dark mode, and cross-platform output.
- 100/100
native
Implementing pure-native mobile features for iOS (Swift 6.3 + SwiftUI + Liquid Glass) and Android (Kotlin 2.4+ + Jetpack Compose + Material 3 Expressive). Builds production features with @Observable/Swift Concurrency, Compose Strong Skipping, SwiftData/Room, Credential Manager + Passkeys, Privacy Manifest, App Intents, Foundation Models/Gemini Nano, and store-compliance staged rollout. Use when building production iOS/Android features. Not for cross-platform (RN/Flutter/KMP/CMP — out of scope), porting design (Port), prototypes (Forge), or web (Artisan).
- 100/100
nest
Designing LLM-optimized folder structures. Audits and restructures directories for context efficiency, progressive disclosure, and prompt cache performance. Don't use for general repo structure (Grove), config audit (Hone), or skill generation (Sigil).
- 100/100
oath
Auditing regulatory compliance and mapping business requirements (SOC2/PCI-DSS/HIPAA/ISO 27001), checking control implementations, designing audit trails, and implementing Policy as Code. Use when compliance auditing is needed.
- 100/100
omen
Enumerating failure modes via pre-mortem analysis. Systematically identifies failure scenarios for plans, designs, and features, scoring them with RPN/AP. Does not write code.
- 100/100
orbit
Running autonomous loops for nexus-autoloop. Generates script sets from goals, designs operation contracts, audits live loops, and recovers state — delivering end-to-end runners that complete reliably.
- 100/100
palette
Improving usability, interaction quality, cognitive load reduction, feedback design, and a11y compliance. Use when improving UX usability or interaction feel.
- 100/100
pdm
Navigating project delivery status as a PdM-style read-only navigator. Reconciles planned scope (specs/issues/roadmap/PRD) against implemented code to produce feature inventories, unimplemented-feature lists, roadmap rollups, and WBS views. Use for "what's built / what's left / where are we". Don't use for code comprehension (Lens), priority scoring (Rank), spec authoring (Scribe), AC conformance (Attest), or live task execution (Sherpa).
- 80/100
pipe
Designing GitHub Actions workflows in depth — covering trigger strategy, security hardening, performance optimization, PR automation, and Reusable Workflow design. Use when new GHA workflow design or advanced optimization is needed.
- 100/100
pixel
Generating pixel-accurate HTML/CSS code from image mockups (PNG/JPG/screenshots) and performing visual verification for faithful reproduction. Use when mockup-to-code generation is needed.
- 100/100
plea
Role-playing as end users to generate authentic feature requests, surface unmet needs, and challenge team assumptions as a synthetic user advocate. Don't use for real feedback analysis (Voice) or UI evaluation (Echo).
- 100/100
pmm
Translating shipped product capability into market positioning, messaging, and go-to-market plans as a Product-Marketing strategist. Authors positioning statements, messaging houses, GTM / launch-marketing plans, and sales-enablement assets — every message grounded in a real, shipped capability. Use for "how do we position / message / launch this". Don't use for competitive research (Compete), narrative story craft (Saga), landing-page build (Funnel), UX microcopy (Prose), SEO/CRO channel execution (Growth), priority scoring (Rank), or technical release engineering (Launch).
- 100/100
polyglot
Implementing internationalization (i18n) and localization (l10n). Extracts hardcoded strings to t() functions, integrates Intl API for date/currency/number formatting, manages translation keys, and adds RTL layout support.
- 100/100
port
Designing web-to-iOS/Android porting strategies. Produces feature parity matrices, native architecture maps, platform-UX adaptation, data/auth/CRDT strategies, BFF redesigns, and Strangler-Fig phased roadmaps from React/Vue/Svelte/Angular SPAs (RSC/SSR included). Optionally proposes a hybrid path (pure-native UI + KMP shared logic). 2026 spec aware (Swift 6.3 / Compose 1.11 / Privacy Manifest / 16KB / Passkey / DMA / EAA). Use when designing web-to-native ports. Not for cross-platform UI (Native — RN/Flutter), same-language framework migration / dependency upgrades / modernization (Shift), legacy archaeology (Trail `static-rules`), or pure-native impl (Native).
- 100/100
prune
Cleaning up the skill ecosystem by auditing the agent roster for overlap, redundancy, and inactivity; proposes merge candidates and sunset plans with evidence + archive instructions. Propose-only (no execute). Use when the ecosystem needs portfolio cleanup, agent consolidation, or sunset planning. Not for individual skill quality (Architect IMPROVE), strategic ecosystem direction (Darwin), code-level YAGNI (Void), file-level dead code (Sweep), or SKILL.md format audit (Gauge).
- 100/100
quest
Designing games — GDD, core mechanics, game balance, economy and progression, level design, and narrative. Produces design docs, not code. Don't use for game implementation (Tick), general specs (Scribe), feature proposals (Spark), or use-case stories (Saga).
- 100/100
radar
Adding edge-case tests, repairing flaky tests, and improving coverage. Use when test gaps need filling, reliability needs raising, or regression tests need adding. Multi-language support (JS/TS, Python, Go, Rust, Java).
- 100/100
rally
Orchestrating multi-session parallel execution using Claude Code Agent Teams API and Codex CLI Subagents to launch, manage, and coordinate concurrent task execution across multiple instances. Use when parallel work is needed.
- 100/100
rank
Quantifying priority by scoring and ordering competing items using ICE/RICE/WSJF/MoSCoW/Cost of Delay/Kano frameworks. No code. Use when prioritizing features/bugs/initiatives, ranking by ICE/RICE/WSJF/etc., or arbitrating Must-have vs Should-have at MVP scoping.
- 100/100
relay
Integrating messaging platforms, developing bots, and designing/implementing real-time communication. Covers channel adapter patterns, webhook handlers, WebSocket servers, event-driven architecture, bot command frameworks. Use when integrating Slack/Discord/Teams bots, designing webhook receivers, or wiring event-driven messaging.
- 100/100
ripple
Analyzing pre-change impact by evaluating risk across vertical (dependency chains, affected files) and horizontal (pattern consistency, naming) dimensions. Does not write code. Use when estimating blast radius before a refactor, audit, or migration — or when a PR's risk surface is unclear.
- 100/100
saga
Designing narratives that tell product and feature use cases as customer-centric stories. Use when customer experience storytelling, scenario stories, or product narratives are needed.
- 100/100
sage
Advising founders YC-style by surfacing the #1 bottleneck via socratic probing, giving pattern-matched honest feedback, detecting founder anti-patterns, and extracting 1-2 week action items. Use when seeking founder-mode advisory. Not for brainstorming (Riff), triadic deliberation (Magi), long-term scenarios (Helm), feature gen (Spark), or impl (Builder).
- 100/100
schema
Designing database schemas, planning migrations, and authoring ER diagrams. Handles normalization, index strategies, and relation definitions. Use when DB schema design is needed.
- 100/100
scribe
Authoring specifications, design documents, implementation checklists, and test specifications. Handles PRD/SRS/HLD/LLD technical documents, review checklists, and test case definitions. Does not write code. Use when technical documentation is needed.
- 100/100
seek
Designing search engines and vector DBs for full-text, vector, and hybrid retrieval. Use when full-text search, vector search, or hybrid search design, index optimization, or RAG retrieval layer implementation is needed.
- 80/100
sentinel
Analyzing code statically for security flaws: hardcoded secret detection, SQL injection prevention, input validation, security headers, and dependency CVE scanning. Don't use for runtime exploit verification (Probe), general code review (Judge), CI/CD management (Gear), or detection rule authoring (Vigil).
- 100/100
sherpa
Guiding workflows by decomposing complex tasks (Epics) into Atomic Steps under 15 minutes each. Manages progress tracking, drift prevention, risk assessment, and timely commit proposals. Use when complex task decomposition is needed.
- 100/100
shift
Orchestrating migrations, upgrades, and modernization across frameworks, libraries, APIs, databases, native runtimes, and dependencies. Detects deprecated libraries, suggests native API replacements, runs technology radar, generates codemods, applies incremental strategies (Strangler Fig/Branch by Abstraction), verifies behavioral equivalence, and produces rollback plans.
- 100/100
siege
Verifying system resilience via load testing, contract testing, chaos engineering, and mutation testing. Use when system limit verification, non-functional testing, or reliability validation is needed.
- 100/100
sigil
Generating, updating, auditing, and sync-repairing project-specific Claude Code skills. Analyzes the repo stack and conventions, synthesizes Micro or Full skills matched to project patterns, and installs to both .claude/skills/ and .agents/skills/. Use when authoring project-local skills.
- 100/100
snap
Automating iOS UI via XCUITest, accessibility-identifier-driven queries, programmatic screenshot capture, and fastlane snapshot pipelines for App Store assets. Authors XCUITest targets with XCUIApplication/XCUIElement/XCUIElementQuery patterns, Page Objects in Swift, status-bar-clean sessions, and xcodebuild+xcresulttool CI. Use when authoring iOS UI tests or store-screenshot pipelines. Not for cross-platform E2E (Voyager — Appium/Detox/Maestro), iOS feature impl (Native), demo recording (Director), or unit tests (Radar).
- 100/100
stream
Designing ETL/ELT pipelines, visualizing data flows, selecting batch/streaming approaches, and architecting Kafka/Airflow/dbt systems. Use when building data pipelines or managing data quality.
- 100/100
summon
Channeling the documented thinking of named notable figures (an 'itako' medium) — applies their mental models, heuristics, and decision-style to your problem as advisory lenses. Don't use for decisions/verdicts (Magi), synthetic user personas (Cast), or fixed founder-mentor coaching (Sage).
- 100/100
sweep
Detecting unnecessary files, unused code, and orphaned files, and proposing safe deletion. For repo cleanup, dead code removal, or tidying. Don't use for removal execution (Builder), deletion review (Judge), repo structure (Grove), or scope cutting (Void).
- 100/100
tempo
Designing scheduling and time-aware logic for cron, timezone/DST, retry/backoff, and business-calendar systems. Use when schedule design is needed.
- 100/100
tick
Implementing engine-agnostic game architecture — game loop, ECS, game state, collision/physics integration, save/load, and netcode foundations. Don't use for game design/GDD/balance (Quest), pixel-art sprites (Dot), game audio, or general app logic (Builder).
- 100/100
titan
Delivering working code fastest via build-first product delivery. Routes through minimum agent chains scoped to the task. S/M scopes skip planning and build immediately. Use when shipping the shortest path to working code, fast-tracking S/M scopes, or compressing time-to-first-PR on small-to-medium features.
- 100/100
tome
Converting repository changes into detailed learning documents. Use when turning diffs into teaching materials, recording design decisions, or creating onboarding materials for new members.
- 100/100
trail
Investigating git history, analyzing regression root causes, and performing code archaeology. Time-travels through commit history to uncover truth. Use when git history investigation or regression analysis is needed.
- 100/100
trawl
Architecting crawl and scraping systems — distributed crawler topology, URL frontier, politeness, and compliance. Architecture-only (no execution code). Don't use for single-page scraping (Vector) or ETL pipelines (Stream).
- 100/100
tuner
Tuning database queries via EXPLAIN ANALYZE, query plan optimization, index recommendations, and slow query detection/fixing. Complements Schema's schema design. Don't use for schema/migrations (Schema), app rewrites (Builder), non-DB performance (Bolt), or unknown root cause (Scout).
- 100/100
vector
Automating browsers via Playwright and Chrome DevTools for data collection, form interaction, screenshot capture, and network monitoring. Task completion focus (vs Voyager for E2E testing).
- 100/100
vigil
Engineering detection rules (Sigma/YARA), mapping detection coverage, designing threat hunting hypotheses, executing Purple Team Blue side, and integrating Detection-as-Code CI/CD. Use when defensive security verification is needed.
- 100/100
vision
Directing UI/UX creative work — complete redesigns, new designs, and trend application. Use when design direction decisions, Design System construction, or orchestration of Muse/Palette/Flow/Forge is needed. Does not write code. Offers an interactive co-design pair mode (decide direction together, one decision at a time).
- 100/100
vitrine
Authoring Storybook stories, managing component catalogs, and integrating Visual Regression. Covers UI component docs, visual testing, CSF 3.0/Factories. Supports Storybook 10 (ESM-only) and React Cosmos. Use when authoring Storybook stories, building a component catalog, or wiring Visual Regression into CI.
- 100/100
voice
Collecting user feedback via NPS surveys, review analysis, sentiment analysis, feedback classification, and insight extraction reports. Use when establishing feedback loops.
- 100/100
void
Verifying YAGNI, cutting scope, pruning, and proposing complexity reductions. A 'subtraction' agent that questions the justification for every code, feature, process, document, design, spec, dependency, and config. Does not write code.
- 100/100
voyager
Authoring E2E tests for web (Playwright/Cypress/WebdriverIO) and native mobile (Appium/Detox/Maestro/XCUITest/Espresso). Covers Page Object design, auth flows, parallel execution, visual regression, a11y, CI, and remote device-farm (BrowserStack/Sauce Labs/AWS/Firebase). Use when authoring E2E suites. Not for unit (Radar), load/chaos (Siege), ad-hoc browser (Vector), or native impl (Native).
- 100/100
weave
Designing workflows and state machines. Use when state transition design, invalid transition detection, Saga patterns, or approval flow design is needed.
- 100/100
wield
Automating the macOS desktop via AppleScript, JXA, and osascript. Controls native apps (Finder, Mail, Safari, Calendar, Notes, Music, System Events) through Apple Events, scripts non-scriptable apps via UI/GUI scripting, glues multi-app workflows, and wires osascript into shell/Python/Node. Use for Mac desktop automation, app control, and Apple Events scripting. Don't use for web/browser automation (Vector), iOS UI automation (Snap), CLI/TUI tool building (Anvil), dotfile/shell config (Hearth), AI CLI config (Hone), or cron scheduling (Tempo).
- 100/100
zen
Refactoring code via variable name improvement, function extraction, magic number constants, dead code removal, and code review. Does not change behavior. Don't use for bug/security (Judge), new tests (Radar), architecture (Atlas), or feature implementation (Builder).
- 100/100
zine
Authoring tech blog/article series for note/Zenn/Qiita/dev.to. Not for specs (Scribe) or microcopy (Prose).