shihwesley

Design consultation: understands your product, researches competitors, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. Use when asked to "design my app", "create a design system", "pick fonts and colors", "design consultation", or "make it look good". For existing sites, use /plan-design-review to infer the system instead.

Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update docs", "sync documentation", "document what shipped", "update the readme after shipping", or "post-release docs".

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review my plan", "eng review", "check my architecture", "review before I build", or "sanity check this plan".

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review my code", "review this PR", "check before merge", "pre-landing review", or "look at my diff".

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship it", "ship this branch", "merge and deploy", "create a PR", "land this", or "push to production".

Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence.

App Store Connect automation for iOS/visionOS: REST API, JWT auth, TestFlight, metadata management, build upload, submission flow. Use when automating any part of the App Store release pipeline.

App Store Connect CLI (asc) patterns, commands, and CI setup. Use when automating App Store submissions, TestFlight distribution, metadata, screenshots, or signing via the asc CLI tool.

File-based planning with interactive gates and native task tracking. Use when user says /plan, needs to break a complex feature into phases, or wants structured implementation planning with user approval at key decision points. Supports task mode (single plan file) and spec mode (multi-file architecture).

Automated plan execution pipeline. Use when running /orchestrate on an /interactive-planning output. Handles plan ingestion, review, skill matching, tech research, user gating, and phased execution with worktree isolation, testing, code review, and incremental commits.

[What it does — one sentence]. Use when user [trigger phrases users would actually say]. Handles [key capabilities]. Do NOT use for [negative triggers if needed to prevent over-firing].

Create a navigable skill graph for a domain from research output or existing skills/docs. Use when user says /create-skill-graph, wants to organize skills into MOCs, build a knowledge graph, or structure domain docs into a navigable hierarchy. Accepts a domain slug with --from-research or --from-existing flags.

Release a shihwesley plugin with semver versioning, conventional commit parsing, changelog generation, and GitHub Release creation. Use when user says /release, wants to tag a new version, publish a release, bump version, or create a changelog. Supports patch/minor/major and --dry-run.

Navigation protocol template for skill graphs. Copy and adapt per domain to teach agents how to efficiently traverse MOC hierarchies. Agent-only — not user-invocable. Use when building a new skill graph that needs a traversal protocol.

Research Apple frameworks against a spec or plan file using exported Dash docset documentation. Produces per-feature reference sections with verbatim code examples and API signatures. Use when user says /apple-research, needs to look up Apple framework APIs before implementation, or wants to generate framework reference docs from a spec file.

Research any topic — builds question tree, discovers sources, fetches to disk (zero context cost), indexes into .mv2, distills into expertise artifact. Agent becomes domain expert. Use when you need to learn about a technology, protocol, framework, or domain before working with it.

Audit previously researched topics and optionally re-index them through the current pipeline. Use when the research flow has changed and you want to backfill, or to see what's been researched.

Show what's indexed in the neo-research knowledge store — sources, chunk counts, file sizes. Use when the user asks what docs are available, what's been indexed, or wants a status check before searching.

Reverse engineer and extract capabilities from any source — GitHub repos, local Claude Code configs, installed binaries, articles, or raw settings files. Use when user says /agent-reverse, wants to analyze a repo for extractable skills, audit their local Claude setup, install capabilities from external sources, or sync their skill manifest. Includes security scanning, manifest tracking, and cross-agent restore.

Check for AgentReverse skill updates and Claude Code changelog changes on session start. Runs automatically via SessionStart hook — compares installed versions against remote, applies safe migrations, and flags breaking changes. Use when user says /agent-reverse-update to manually trigger an update check.

Maps and documents codebases of any size by orchestrating parallel subagents. Creates docs/CODEBASE_MAP.md with architecture, file purposes, dependencies, and navigation guides. Generates docs/.mercator.json merkle manifest for O(1) change detection. Updates CLAUDE.md with a summary. Use when user says "map this codebase", "mercator", "/mercator-ai", "create codebase map", "document the architecture", "understand this codebase", or when onboarding to a new project. Uses merkle tree for O(1) change detection — only re-explores changed files.

File-based planning with interactive gates and native task tracking. Use when user says /plan, needs to break a complex feature into phases, or wants structured implementation planning with user approval at key decision points. Supports task mode (single plan file) and spec mode (multi-file architecture).

TLDR-aware code simplifier that uses AST summaries for context and reads only target files in full. Achieves 80%+ token savings on large codebases. Use when user says /simplify, wants to reduce code complexity, remove dead code, eliminate redundant abstractions, or simplify over-engineered patterns. Merkle-integrated for O(1) cache lookups.

Ambient .tech.md documentation generator with freshness tracking. Auto-generates technical documentation alongside source files and tracks staleness per file. Use when user says /chronicler, wants to set up documentation for a project, check doc freshness, regenerate stale docs, or configure chronicler settings. Supports init, status, regenerate, and configure subcommands.

This skill should be used when the user says '/orbit', '/orbit init', '/orbit status', '/orbit test', '/orbit staging', '/orbit use', '/orbit sidecars', '/orbit logs', '/orbit stop', '/orbit check', '/orbit templates', asks about environment status or switching, wants to run tests in Docker containers, needs to manage dev/test/staging environments, or asks about sidecar services like PostgreSQL or Redis for their project.