liaoann
- 21 skills
- 0 followers
- 6 hours ago last updated
- ▌ Knip · liaoannUse when configuring or debugging Knip — creating or editing a knip config, tuning entry/project globs, silencing false positives, or reading Knip output. Mentions of knip, `knip.jsonc`, "unused exports", or "unused dependencies" are triggers.
- ▌ Tdd · liaoann bundleTest-driven development via red-green-refactor. Use when the user wants to build a feature or fix a bug test-first, mentions "TDD" or "red-green-refactor", wants behavior verified through tests as code is written, or is deciding whether a schema, migration, type, or configuration change is owed a test at all.
- ▌ Ask Me · liaoannRouter for my process skills. Type /ask-me when unsure which workflow fits the situation.
- ▌ Plan It · liaoannPlan a code change before implementation. Use when the user wants to add, modify, remove, or fix behavior and needs an approach, impact analysis, testing strategy, acceptance criteria, or implementation plan.
- ▌ CI Triage · liaoannTriage and boundedly remediate failing CI or local validation checks. Use when builds, type checks, lint, tests, GitHub checks, or other CI jobs fail and the user wants to know what is caused by the current change, what can be auto-fixed safely, what needs implementation work, or what can be treated as unrelated.
- ▌ Study Repo · liaoannUse for repo/package questions, feature tracing, usage checks, and dependency uncertainty about behavior, contracts, limits, versions, or bugs. Verify package claims with primary sources before answering or coding.
- ▌ Drizzle Orm · liaoannUse when working with Drizzle ORM on any SQL driver (Cloudflare D1, Postgres, MySQL, SQLite, LibSQL) — writing or editing a schema, adding or changing migrations, declaring column types (especially JSON columns), setting up timestamps, or testing Drizzle-backed code with Vitest — and when reviewing such a change. Mentions of drizzle, drizzle-kit, `.sql` migrations, or `drizzle/meta` are triggers.
- ▌ Contracts · liaoannContract-design principles for APIs, schemas, events, jobs, module exports, configuration, and other cross-boundary interfaces. Use when defining, changing, or reviewing a public interface or data shape that other code, users, services, jobs, or future versions may depend on.
- ▌ Diagnose Bug · liaoannDiagnose a reported product, runtime, or performance bug before fixing it. Use when the user reports broken, slow, surprising, inconsistent, or user-visible behavior and wants root cause analysis, reproduction steps, fix strategy, or acceptance criteria. For failing CI, build, lint, typecheck, or test jobs, use ci-triage first unless the failure has already been classified as a product behavior bug.
- ▌ Review Change · liaoannReview a completed or in-progress code change from a fresh reviewer perspective. Use when the user asks for code review, wants a diff checked before finishing, or wants subagents to inspect correctness, regressions, tests, and maintainability.
- ▌ Implement Plan · liaoannImplement an agreed code-change plan. Use when a plan exists or the user asks the agent to execute planned work, edit code, run validation for that work, fix validation failures encountered during implementation, and report the final state.
- ▌ Architecture · liaoannModule-boundary and dependency-hygiene principles for organizing a codebase. Use when placing new files, deciding where logic belongs, adding cross-module imports, or reviewing whether a change respects existing boundaries.
- ▌ Devcontainer Exec · liaoannUse when a project is developed inside a Dev Container — the repo has a `.devcontainer/` directory, or CLAUDE.md/AGENTS.md states the project runs in a devcontainer — and any install, build, test, lint, typecheck, script, or app-run command must execute inside the container rather than on the host.
- ▌ Reviewable Change · liaoannDiff hygiene principles for human-auditable changes. Use when deciding how to split, limit, or report a diff so behavior changes, refactors, renames, formatting, generated output, and test changes remain separable and reviewable.
- ▌
- ▌ Engineering Quality · liaoannMaintainable-code principles for clarity, comments, error context, small local refactors, and algorithmic shape. Use when a planning, implementation, or review decision specifically needs judgment about readability, debuggability, scope control, or avoidable complexity.
- ▌ Codebase Stewardship · liaoannCodebase-coherence principles for fitting a change into existing patterns. Use when choosing names, file placement, extension points, abstractions, test fixtures, or domain vocabulary so new work does not create parallel systems or drift from local conventions.
- ▌ Property Based Testing · liaoann bundleUse when generated inputs can search for unknown counterexamples to a stated behavioral property, law, invariant, round trip, model comparison, or state transition rule. Common fits include parsers, serializers, validators, calculations, permissions, state machines, migrations, normalization, ordering, grouping, and deduplication, but do not use merely because code belongs to one of these domains.
- ▌ Agent Instruction Files · liaoannPlacement rules for agent instruction files (AGENTS.md, CLAUDE.md, .cursorrules, .github/copilot-instructions.md) and their relationship to code comments. Use when deciding whether a fact belongs in one of those files or in a comment next to the code, before adding or expanding a paragraph in one, or when such a file has grown long, repetitive, or stale.
- ▌ Persistent Side Effects · liaoannPersistent side-effect approval contract. Use before creating files or directories, staging or committing changes, creating or switching branches, deleting/moving/overwriting user-visible files, or writing scratch/planning artifacts.
- ▌ Agentic Change Governance · liaoannAgent authority and scope-control principles. Use when deciding whether an agent is authorized to make or propose a change, especially design changes, ownership-boundary changes, convention changes, public-contract changes, opportunistic cleanup, or rule weakening outside the accepted request or plan.