Han: AI skills and agents for "Solo" product engineers and small teams
Agent
Audits and rewrites a finished draft against the shared Human-Readable Output Standard, preserving every fact. Assumes the draft leads with context instead of the answer, buries its point, and carries insider phrasing a non-author cannot follow — and rewrites it so the main point comes first, each paragraph carries…
Agent
Assumes all code is insecure, full of PII leaks, and an easy attack surface. Performs adversarial security analysis to prove real security vulnerabilities exist in first-party code and dependencies — not potential vulnerabilities, but actual exploit paths with file-level evidence. Use when thorough security…
Agent
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
Agent
Analyzes the runtime behavior of a specified codebase focus area — data flow, error propagation, state management, and integration boundaries. Produces numbered behavioral findings with file paths and verbatim code. Use when evaluating how data moves through a system, where errors are handled or lost, and how modules…
Agent
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
Agent
Analyzes concurrency and async patterns in a specified codebase focus area — race conditions, shared resource contention, deadlock potential, lock ordering, and async error handling. Produces numbered concurrency findings with file paths and verbatim code. Use when evaluating thread safety, async correctness, or…
Agent
Audits updated documentation against original source content to ensure no important facts were lost. Classifies facts as present, correctly removed, or missing, validates removals against the codebase, and identifies content that must be restored. Use for validating documentation updates preserve critical information.…
Agent
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
Agent
Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…
Agent
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
Agent
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
Agent
Performs gap analysis between two artifacts — finds what's missing, incomplete, conflicting, or assumed when comparing a current state against a desired state. Delegate whenever the user wants to check, compare, or verify code, features, or implementations against specs, specifications, PRDs, requirements, or design…
Agent
Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…
Agent
Adversarial-collaboration generalist, three to five years in, who assumes every plan, design, requirement, code change, or in-flight discussion hides assumptions, muddied scope, and claims made without evidence. Works in two modes: artifact-review over completed plans, PRDs, ADRs, design docs, code branches, and…
Agent
Adversarial on-call engineer who assumes application source will fail in production and the author will not be paged. Audits application source, not infrastructure, for code-level resilience anti-patterns: missing timeouts, retries without backoff and jitter, non-idempotent operations in retry paths, catch-and-swallow…
Agent
Synthesizes cross-specialist input into a plan the team can commit to, recording decisions, rejected alternatives with reasons, the evidence behind each call, and the items still open. Reads the inputs from every specialist who contributed, reconciles their recommendations, and applies an evidence standard to each …
Agent
Scans a code repository to discover project-level attributes: languages, frameworks, tooling, configuration, documentation structure, and infrastructure. Optimized for reading config files and directory structure rather than deep code tracing.
Agent
Assesses the risk of inaction for architectural findings produced by upstream analysis agents. Evaluates each finding across four dimensions: likelihood, severity, blast radius, and reversibility. Receives pre-digested structural, behavioral, and concurrency findings — does not perform its own codebase analysis. Use…
Agent
Adversarial software architect who assumes the current intra-codebase structure is wrong: over-coupled where it should be independent, under-cohesive, missing an abstraction at a trust or infrastructure edge, or over-abstracted with single-implementation interfaces. Synthesizes structural, behavioral, concurrency, and…
Agent
Analyzes the static structure of a specified codebase focus area — module boundaries, coupling, dependency direction, abstractions, and duplication. Produces numbered structural findings with file paths and verbatim code. Use when evaluating how code is organized and connected at the module level. Does not trace…
Agent
Adversarial system architect who assumes the current cross-service topology is wrong: bounded contexts leak, integrations are synchronously chained where events would decouple, and failure domains are uncontained. Synthesizes boundary-crossing findings into recommendations on bounded-context boundaries, context-map…
Agent
Examines code and plans tests focused on observable behavior — inputs, outputs, and collaborator interactions — rather than internal code paths. Identifies untested behaviors, recommends test doubles (stubs for queries, mock expectations for commands) for isolation, and produces a prioritized test plan with…
Agent
Adversarial UX and interaction designer who assumes the current interface is less than optimal. Audits features, screens, and flows for usability and interaction problems grounded in universal design, Nielsen's 10 heuristics, WCAG 2.2 accessibility, affordance and signifier clarity, microinteractions, goal-directed…