← all skills

zernie

@zernie seed · attribution · source repo

0 followers · 22 skills

1. ▌
   Pr To Lint Rule · zernie bundle

   Convert a recurring PR review comment into an automated lint rule with tests and CLAUDE.md annotation
   0
   installs
2. ▌
   Ship Pr · zernie bundle

   Run the project checks and open a pull request once they pass
   0
   installs
3. ▌
   Edit Spec · zernie

   Edit a vigiles .spec.ts to change a compiled instruction file (CLAUDE.md / AGENTS.md) — add, modify, or remove a rule, section, command, or key file. Use whenever you need to change a CLAUDE.md/AGENTS.md that carries a vigiles hash (edit the spec, never the artifact), including adding a new enforce()/check()/guidance() rule.
   0
   installs
4. ▌
   Adopt Spec · zernie

   Adopt a typed .spec.ts for an existing hand-written CLAUDE.md — start from the file you already have, non-destructively
   0
   installs
5. ▌
   Strengthen · zernie

   Upgrade a vigiles spec's guidance() rules to enforce() — scan the guidance rules in a CLAUDE.md/AGENTS.md spec and find existing linter rules (ESLint, Ruff, Clippy, Pylint, RuboCop, Stylelint) that back them. Use when asked to strengthen, harden, or make vigiles rules enforceable; NOT for general linting or fixing lint errors.
   0
   installs
6. ▌
   Test Harness · zernie bundle

   Install vigiles and test a Claude Code harness — hooks, skills, agents, settings, CLAUDE.md — by picking the right tier (unit / deterministic / eval) and writing a test that passes. Use to check that a hook fires or blocks, that a skill triggers, that injected context lands; or to observe a run — which tools it called, whether it stayed inside its declared allowed-tools, what files and side effects it produced, how to intercept a call without executing it.
   0
   installs
7. ▌
   Debug My Harness · zernie

   Diagnose why an agent harness misbehaved by reading the local flight-recorder ledger (.vigiles/runs.jsonl) — which skills fired or got hijacked, which hooks blocked or wrongly allowed, which subagent tool-contract violations happened, and how a skill's trigger rate moved. Use when asked why a skill stopped firing, why a hook didn't block, why the wrong skill ran, or to debug/investigate what the harness actually did. NOT for writing new rules (use strengthen) or editing the spec (use edit-spec).
   0
   installs
8. ▌
   Screenshot · zernie bundle

   Render a local web page / built site and capture full-page screenshots (desktop + mobile) using the pre-installed Chromium. Use when asked to screenshot, render, or "see how it looks" for the vigiles landing site (site/), the audit report (report/), or any local HTML/dev server. Handles the scroll-reveal gotcha (below-the-fold cards captured blank) automatically.
   0
   installs
9. ▌
   Dogfood CLI · zernie

   Hunt for real bugs in the vigiles CLI/codebase with a parallel expert fan-out, then FIX them directly — source-trace each defect to file:line, add a regression test, commit per theme. Use when asked to dogfood vigiles, find/fix bugs across the CLI the source-traced way, or fan out agents to audit the tool on itself.
   0
   installs
10. ▌
    Review Docs · zernie

    Review the README or a documentation page from several real reader points of view at once. Fans out one parallel reviewer per audience — Claude Code newcomer, power user, plugin/skill author, skeptical senior engineer, non-running decision-maker — each scoring it x/5 and naming concrete, line-level fixes. Use when asked to review, critique, grade, or "get to N/5" the README or any front-door doc, or to check how a doc reads for real users. Not for code review (use /code-review for that).
    0
    installs
11. ▌
    Add A Linter · zernie

    Add a new linter to vigiles's cross-referencing engine as one cohesive, type-enforced unit — a LinterAdapter in the LINTERS registry, with the conformance test enforcing docs + site parity so no site is forgotten
    0
    installs
12. ▌
    Code Quality · zernie bundle

    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.
    0
    installs
13. ▌
    Landing Site · zernie

    The purpose, UX flow, and modern-minimalist design bar for the vigiles.sh landing site (site/). Use whenever designing, editing, adding to, or reviewing any site/ component, hero, section, or marketing copy — read it BEFORE touching site/, and hold every change against it. Not for docs/ or the app itself.
    0
    installs
14. ▌
    Deep Research · zernie

    Use when the user asks to research a topic in depth, map a competitive/market landscape, run a multi-source investigation, or "fan out" parallel research agents — anything where many findings must be gathered and then NOT lost. Enforces durable, detail-preserving research (write full findings to disk; keep a full appendix beside the synthesis).
    0
    installs
15. ▌
    Generate Logo · zernie

    Generate or iterate on the vigiles logo using ImageRouter API
    0
    installs
16. ▌
    Audience Check · zernie

    Read the README (or any front-door doc) through the eyes of several distinct audience personas and report what each would think, miss, or bounce on
    0
    installs
17. ▌
    Ship A Feature · zernie bundle

    Ship a NEW capability to vigiles so it actually reaches a user — a new export, public function, subpath, CLI flag, or hook-vocabulary word. Use when about to add, or having just added, a feature / export / public API to this repo. Runs the executable checks a green `npm run check` does NOT make — reachable from a public door, API-surface diff READ, a public doc home, the experimental_ decision, a gate on a frozen tree. NOT for bug fixes, refactors, doc-only or test-only edits.
    0
    installs
18. ▌
    Audit Feedback Loop · zernie

    Scan the current repo and score its feedback loop maturity for AI-assisted development
    0
    installs
19. ▌
    Enforce Rules Format · zernie

    Validate that all rules have proper enforcement classification (enforce/check/guidance)
    0
    installs
20. ▌
    Verify Docs Findable · zernie

    Audit whether a repo's docs actually ANSWER the questions a reader has — by spawning fresh, cheap (Haiku) agents that cold-read ONLY the docs and measuring how fast they reach the answer, whether they hit dead-ends, whether they fall back to source code, and whether they cite docs that contradict each other. Use after a doc reorg, when docs "feel scattered," or when the same confusion keeps recurring. Surfaces findability gaps (a corpus can be COMPLETE — every doc indexed — yet not FINDABLE) plus a prioritized fix list. Works on any repo's docs, not just this one.
    0
    installs
21. ▌
    Ask · zernie

    Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
    0
    installs
22. ▌
    Flow Define · zernie

    Multi-AI requirements scoping using available external providers (Double Diamond Define phase)
    0
    installs