whoislewys-skills

Plugin whoislewys-skills from marketplace whoislewys in whoislewys/skills. Commands read from the repo's manifest — yesterday.

Skills (10)

• c4-architecture

  Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "

• explain-diff-html

  Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

• fix-dep-audit

  Resolve dependency security audit findings by preferring minor version upgrades to base packages first, then targeted fixes, verifying with pnpm audit after each change. Use when fixing dependency vulnerabilities or remediating a dependency audit.

• improve-readability

  Code readability principles from John Ousterhout's A Philosophy of Software Design, drawing on Ch. 2 (Nature of Complexity), 4 (Modules Should Be Deep), 10 (Define Errors Out of Existence), 13 (Comments Describe What Isn't Obvious), 14 (Choosing Names), 17 (Consistency), and 18 (Code Should Be Obvio

• prove-it

  Works? Prove.

• unit-test

  Guidance for writing unit tests that verify observable behavior and public contracts rather than internal implementation. Use when writing, reviewing, or refactoring unit tests, deciding whether to mock or stub, or when tests are brittle and break on refactors.

• write-good-comments

  Write and review code comments using Ousterhout's rule from A Philosophy of Software Design (Ch. 12-13) — a comment must carry what the code next to it cannot. Covers interface vs implementation comments, precision comments on declarations, intuition comments on blocks, and cross-module design notes

• task-diagram

  use when user asks for a "task diagram", or asks for help in performing "Applied Cognitive Task Analysis

• simple-english

  Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simpl

• simpler-english

  Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simpl

Similar plugins