SkillsAdd

zernie/vigiles

code-quality

Improve the quality and type-safety of TypeScript/JavaScript being written or refactored — parse-don't-validate, make-illegal-states-irrepresentable, exhaustive matching, pure-function/IO separation, and public-API hygiene.

First seen Jul 15, 2026

Installation

$ npx skills add zernie/vigiles --skill code-quality
View on skills.sh ↗ GitHub repository ↗

Summary

  • Improve the quality and type-safety of TypeScript/JavaScript being written or refactored — parse-don't-validate, make-illegal-states-irrepresentable, exhaustive matching, pure-function/IO separation, and public-API hygiene.
  • Use when asked to refactor, clean up, improve, harden, or review the design/quality of code or an API.
  • NOT for hunting bugs (that's /code-review) and NOT for vigiles's own spec/lint rules.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from zernie/vigiles · top by installs.

npx skills add zernie/vigiles
strengthen 1.6K edit-spec 1.6K test-harness 1.6K linter-docs 1.5K adopt-spec 1.4K debug-my-harness 1.1K deep-research 685 review-docs 550 pr-to-lint-rule 361 audit-feedback-loop 360

Browse all from zernie/vigiles

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 15
License LICENSE
Default branch main
Open issues 17
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,248 B
  • docs SUMMARY.md 3,399 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 313 installs

SKILL.md

Apply a small set of type-driven quality techniques when writing or refactoring code. Each technique has its own reference — the principle, a real before/after from this repo, and the smells to grep for. Read the reference(s) that match the code in front of you; don't apply all five blindly.

When this fires

A request to refactor / clean up / improve / harden / tighten code or an API — or when you're about to write a new module/type/public export and want it right the first time. Not a bug hunt (use /code-review).

The techniques — read the matching reference

Smell in front of you Technique Reference
a magic 0 / "" / -1; the same primitive re-validated at many sites; "x" in obj repeated Parse, don't validate [references/parse-dont-validate.md](references/parse-dont-validate.md)
a field that's always ""; boolean-flag soup; a sentinel standing in for "absent"; an impossible combo that still compiles Make illegal states irrepresentable [references/make-illegal-states-irrepresentable.md](references/make-illegal-states-irrepresentable.md)
a switch/if-chain on a union with no exhaustiveness guard Exhaustive matching [references/exhaustive-matching.md](references/exhaustive-matching.md)
logic tangled with IO (spawn/fetch/fs); a function that's hard to test Pure functions + injected seams [references/pure-functions.md](references/pure-functions.md)
a public export with a fuzzy shape; a string that means an enum; a leaked internal helper Public-API quality [references/public-api-quality.md](references/public-api-quality.md)

How to apply

  1. Name the decision out loud before you change the shape — what illegal state it forbids, where the parse boundary sits (the surface-architecture-decisions reflex). A quality change the reviewer can't see is churn.
  2. One technique at a time, tests stay green. Change the type, let tsc show you every call site, fix them, run the tests. Never batch five refactors into one unreviewable diff.
  3. Don't over-abstract (rule-of-three / YAGNI). A tagged union for 3 real variants is good; an abstraction for a difference that doesn't exist yet is the bug this skill is supposed to prevent.
  4. Prefer the strongest option the DECIDABILITY allows — a type that can't express the bad state beats a runtime check that hopes to catch it; but a runtime guard at a boundary beats nothing when the input is genuinely dynamic.

Guardrails

  • Quality only, not correctness. This skill improves shape/design; it does not hunt for bugs — that's /code-review.
  • Every change removes a real failure mode. If you can't name the bug the new shape prevents, don't make the change.
  • Keep the public surface small. A new export is a contract (see the public-API reference); don't widen it to make a refactor convenient.