wcygan
@wcygan
Public Skills
Cognitive Load Reviewer & Guide
by wcygan
References: principles, code-patterns, architecture, review-checklist
Beads Decompose
by wcygan
Configuration for Development Environments
Beads Assign
by wcygan
Configuration for Development Environments
async-rust
by wcygan
Async Rust and Tokio ecosystem expert. Provides idiomatic patterns, architectural guidance, and code review for async Rust code using tokio, futures, bytes, tracing, tonic, hyper, tower, axum, tokio-stream, and pin-project. Covers runtime internals, cancellation safety, graceful shutdown, channel selection, shared state, backpressure, structured concurrency, error handling, Tower middleware, stream processing, and performance tuning. Also identifies async footguns (blocking the runtime, holding locks across .await, silent task panics, accidental cancellation) and suggests fixes. Use when writing async Rust, debugging async issues, reviewing async code, choosing between spawn/join/select, designing channel topologies, implementing graceful shutdown, or learning how futures, Pin, and the Tokio runtime work under the hood. Keywords: async, await, tokio, futures, spawn, select, join, channels, streams, pin, tower, tonic, hyper, axum, tracing, bytes, cancellation, runtime, backpressure, graceful shutdown.
axum
by wcygan
Axum Rust web framework expert. Auto-loads when working with axum Router, handlers, extractors, FromRequest, IntoResponse, State, middleware, tower layers, tower-http, axum::serve, method routing, Json extractor, Path extractor, Query extractor, error handling, or Rust HTTP APIs. Keywords: axum, router, handler, extractor, middleware, tower, IntoResponse, FromRequest, State, Rust web, HTTP API
idiomatic-rust
by wcygan
Analyze and generate idiomatic Rust code following official style guide, std library conventions, and API design guidelines. Auto-loads when writing, reviewing, or refactoring Rust code. Use when writing Rust, reviewing Rust code, checking Rust idioms, or generating Rust scaffolding. Keywords: rust, idiomatic, ownership, borrowing, lifetime, trait, error handling, pattern matching, clippy, rustfmt, cargo
clone-research
by wcygan
Comprehensive product research for building an MVP clone. Spawns 4 parallel research agents to produce 9 standardized documents: Product Thesis, Feature Priority Matrix, MVP Scope Contract, Core User Journeys, Domain Model, System Architecture, Revenue & Pricing Model, API Surface Spec, and Design System Brief. Use when planning a clone, building a competitor alternative, scoping an MVP, or analyzing a product to replicate. Keywords: clone, MVP, product research, teardown, feature matrix, domain model, reverse engineer, competitor clone
clone-sprint
by wcygan
Sprint-scoped MVP builder that consumes clone-research output. Decomposes research into a beads task DAG (epics per bounded context, subtasks per feature slice), spawns worktree-isolated builder agents in batches of 2-3, merges via bd merge-slot, and reports progress. Idempotent: first invocation creates the DAG; subsequent invocations run the next sprint via bd ready. Keywords: clone, build, sprint, MVP, beads, worktree, parallel, task DAG, feature slice
deep-dive
by wcygan
Deep dive into a codebase to understand specific topics, patterns, or implementations. Spawns parallel agents with distinct investigation strategies (breadth-first mapping, depth-first tracing, optional history/boundary analysis) then synthesizes findings into a layered summary. Use for understanding how something works, exploring unfamiliar code, or building a mental model of a large system. Keywords: deep dive, explore, understand, how does, architecture, codebase exploration, trace, investigate, mental model
brainstorm
by wcygan
Multi-agent brainstorming for software design decisions and architecture choices. Spawns parallel agents with differentiated roles (codebase explorer, trade-off analyst, devil's advocate) to evaluate options, surface blind spots, and produce structured analysis including trade-off matrices, pre-mortems, and ADR-ready summaries. Use when making architecture decisions, choosing between approaches, or evaluating trade-offs. Keywords: brainstorm, decision, trade-off, architecture, design, evaluate, options, approach, choose, pros cons, ADR, pre-mortem, WWHTBT
context-decorate
by wcygan
Scan a codebase and place CLAUDE.md context files in directories that lack them. Spins up a team of subagents to parallelize the work — each agent covers a few directories and generates a succinct overview of the directory's purpose and key subdirectories. Use when onboarding to a new codebase, improving Claude context quality, annotating project structure, or scaffolding directory-level context for AI assistants. Keywords: context, CLAUDE.md, annotate, codebase, directory, onboard, decorate, scaffold context, context files.
connectrpc
by wcygan
ConnectRPC expert for Go servers and Node.js clients. Auto-loads when working with ConnectRPC, connect-go, connect-node, protobuf RPC, buf codegen, gRPC-compatible APIs, streaming RPCs, ConnectError, interceptors, service handlers, transport configuration, or REST-to-RPC proxy patterns. Covers the architecture where Node frontend servers proxy REST+JSON from the UI into ConnectRPC calls to Go backend services.
plan-mode
by wcygan
Research, analyze, and create a detailed implementation plan without making any code changes. Read-only planning mode with sub-agent exploration. Use when planning implementation, designing approach, creating technical plans, or analyzing before building. Keywords: plan, design, approach, implementation plan, analyze, research, strategy, read-only planning
interview
by wcygan
Conduct an in-depth requirements interview to flesh out a plan or spec file. Ask non-obvious questions about technical implementation, UI & UX, tradeoffs, and concerns — then write the finalized spec back to the file. Use when you need to flesh out requirements, refine a spec, clarify a plan, or gather details before implementation. Keywords: interview, spec, plan, requirements, flesh out, questions, clarify spec, requirements gathering.
explain
by wcygan
Explain code, functions, modules, or programming concepts with structured walkthroughs covering purpose, patterns, data flow, edge cases, and performance. Use when explaining code, understanding how something works, learning a concept, or walking through a codebase. Keywords: explain, how does this work, what does this do, walkthrough, understand, code explanation, concept, teach, learn
refactor-scan
by wcygan
Scan code for refactoring opportunities to improve modularity, testability, extensibility, reusability, understandability, and cognitive complexity. Use when reviewing code quality, identifying technical debt, planning a refactor, or improving code structure. Keywords: refactor, refactoring, code quality, modularity, testability, extensibility, reusability, cognitive complexity, code smell, clean code, SOLID, DRY, coupling, cohesion
expand-tests
by wcygan
Analyze existing test patterns and create comprehensive, idiomatic tests to expand coverage. Detects framework (Jest, Vitest, pytest, Go, Rust, JUnit), matches project conventions, and fills coverage gaps. Use when adding tests, improving coverage, expanding test suite, or writing tests for untested code. Keywords: test, tests, testing, coverage, unit test, integration test, expand tests, test coverage, write tests, add tests, test gaps
new-global-skill
by wcygan
Interactive wizard to create new global Claude Code skills for dotfiles distribution. Use when creating skills available across all projects, adding personal workflows to dotfiles, or scaffolding ~/.claude/skills. Keywords: create global skill, new global skill, dotfiles skill, personal skill, cross-project skill, global workflow
new-skill
by wcygan
Interactive wizard to create new agent skills for Claude Code. Use when creating skills, building agent capabilities, adding model-invoked workflows, or setting up skill directories. Keywords: create skill, new skill, agent skill, skill wizard, build skill, SKILL.md
postgres
by wcygan
PostgreSQL best practices, query optimization, connection troubleshooting, and performance improvement. Load when working with Postgres databases.
mysql
by wcygan
Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations. Use when creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; or troubleshooting replication and connection issues. Load when using a MySQL database.
fast-commit
by wcygan
Stage all changes with git add -A and commit immediately with a concise message derived from recent work. Use when you want to quickly commit everything without interactive review or confirmation. Keywords: fast commit, quick commit, commit everything, stage all, commit all, ship it
design-research
by wcygan
Research website design, styling, and frontend implementation using Playwright CLI to capture screenshots and analyze structure. Use when a software engineer wants to understand and implement a similar design. Keywords: design research, website design, frontend analysis, UI study, design system, screenshot, Playwright
Product Discovery
by wcygan
Example queries and expected outputs