all publishers

Calvin-LLC

@calvin-llc source repo

33 published skills

  1. ▌
    Technical Writing · calvin-llc bundle
    Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, commit messages, or any prose the reader must understand on first read: Diátaxis modes, Google developer style, STE, Global English.
    0 installs
  2. ▌
    Writing For Agents · calvin-llc
    Use when authoring or pruning the content of a skill, AGENTS.md, SOUL.md, or a brief. Not for installing or syncing skills, nor for prose style edits.
    0 installs
  3. ▌
    Benchmark Checklist · calvin-llc
    Vet a performance measurement (limiter, tuning, limits, errors, repeatability, relevance, whether the work ran) before reporting a speedup or regression. Use when you run a benchmark or report a number you measured.
    0 installs
  4. ▌
    Improve Codebase Architecture · calvin-llc bundle
    Use when asked to improve a codebase's architecture or find what to refactor. Scans for deepening opportunities, presents them as a visual HTML report, then grills through whichever one you pick.
    0 installs
  5. ▌
    Readme Clean · calvin-llc bundle
    Use when asked to clean up, optimize, rewrite, or de-slop a README: rewrites it plain and concise, checks every claim against the repo, and proves no technical fact was dropped.
    0 installs
  6. ▌
    Figure It Out · calvin-llc
    Use for /figure-it-out, 'figure it out', a large migration, an ambitious multi-part change, work a human reviews after stepping away, or when no narrower playbook fits. Designs an auditable bespoke playbook with rigor scaled to the task.
    0 installs
  7. ▌
    Gemini Vision · calvin-llc bundle
    Use when inspecting or reviewing UI screenshots, mockups, diagrams, or wireframes for layout, hierarchy, readability, or visual bugs. Not for pixel or color analysis of camera or capture images, nor for routine text edits.
    0 installs
  8. ▌
    Writing Plans · calvin-llc
    Write an implementation plan from a spec or when the user asked for a plan, before touching code.
    0 installs
  9. ▌
    Diagnosing Bugs · calvin-llc
    Diagnose a hard bug or performance regression by first building one command that reproduces the exact symptom. Use when something is broken, throwing, failing, flaky or slow and the cause is not obvious. Use how for how code works, why for history.
    0 installs
  10. ▌
    Reference Mining · calvin-llc bundle
    Use when checking whether a reference project already solves a problem ("do the references do this", prior art, a mechanism hunt) or when improving a target repo from one. Evidence, not a template; not for copying code or reviewing one repo alone.
    0 installs
  11. ▌
    To Questionnaire · calvin-llc
    Turn a decision you can't resolve alone into a questionnaire someone else fills in. Use when blocked on knowledge another person holds (a lead, a client, a reviewer) and you need it pulled out of them async. Do not use for questions you can answer by running or reading something.
    0 installs
  12. ▌
    Poteto Mode · calvin-llc bundle
    Use for poteto, /poteto-mode, or requests to work in this style. Playbook-routed tasks, deliberate subagents, verified work, simple code, concise unslopped replies.
    0 installs
  13. ▌
    Blast Radius · calvin-llc
    Find what a change could break outside the diff and prove the one fact it is safe because of by running real code. Use for 'blast radius of X', 'what could this break', or a small diff you do not trust. Use how for what code does, why for motivation.
    0 installs
  14. ▌
    Repo Retro · calvin-llc bundle
    Review recent agent sessions in this repo for wasted navigation, failed searches, stale docs and command loops. Ranks findings by cost and logs metrics so the next run shows whether fixes worked. Proposes only; edits nothing until approved.
    0 installs
  15. ▌
    Arch Export · calvin-llc bundle
    Use when the user wants a sanitized architecture brief, or a prompt to paste into an outside model (Perplexity, ChatGPT, Claude) with no repo access, to review a design, defect, or finished artifact.
    0 installs
  16. ▌
    Arch Import · calvin-llc
    Use after pasting an outside reviewer's reply to an `arch-export` brief; adjudicates it against the real code, applies cheap safe wins, and ends with a decision ledger and build order.
    0 installs
  17. ▌
    No Comments · calvin-llc bundle
    Use when asked to strip, audit, or clean up code comments: deletes unproven, narrating, and stale comments from a diff or file set, in the current session.
    0 installs
  18. ▌
    Impeccable · calvin-llc bundle
    Use when designing, critiquing, or improving a frontend or native UI: pages, dashboards, components, forms, layout, typography, color, motion, UX copy, design systems. Not for backend-only or non-UI tasks.
    0 installs
  19. ▌
    Sharpen · calvin-llc
    Use for /sharpen, or before starting a task that is vague, over-specified, or open-ended: find the expert approach, what the user is really after, and the right level of specification.
    0 installs
  20. ▌
    Grill Me · calvin-llc bundle
    Use for grill me, interrogate, which approach, challenge this, stress-test this plan, steer. Asks one non-jargon fork question, grills a plan's hidden decisions, or runs a multi-model design review. Not for rewording or explaining.
    0 installs
  21. ▌
    Architect · calvin-llc bundle
    Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape: sketch types, signatures, and module structure before code, then implement against the agreed sketch.
    0 installs
  22. ▌
    Declauding · calvin-llc bundle
    Load at the start of any task whose deliverable is prose another person will read — a PR description, commit message, README, doc, postmortem, blog post, issue or review comment, report, release note or essay — before drafting it, whether the result is pushed, posted, published or saved to a file, without being asked. Draft, then run this pass on the draft before handing it over. Also use when someone says "de-claude", "de-slop", "humanize this", "this reads like AI", "make it sound human", or asks for a voice, tone or register edit. Rewrites the constructions that mark prose as model-written (staged reveals, verdict headers, aphoristic closers, "it's not X, it's Y", em-dash drama, forced triads, flat-certainty adverbs, noun stacks, dropped 'that') into plain technical prose and checks the rewrite kept every claim. Not for fiction, poetry, code, or quoted text; for a full adversarial review of a deliverable use challenging.
    0 installs
  23. ▌
    Deslop · calvin-llc
    Use for a code hygiene or cleanup audit that measures complexity, nesting, file length, duplicates, dead code, type escapes, and coverage against numeric ceilings; not for subjective style review.
    0 installs
  24. ▌
    Recall · calvin-llc bundle
    Reconstruct your recent working context from agent session history and live git state, then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
    0 installs
  25. ▌
    Unslop · calvin-llc
    Use when writing or editing text a person will read (docs, READMEs, replies, commit messages): cuts AI tells (puffery, filler, em dashes, jargon) and adds a human voice.
    0 installs
  26. ▌
    Babysit · calvin-llc bundle
    Use when asked to babysit a PR or stack, get it green, address review comments, or push to main and watch CI and the deploy until live; drives a PR to merge-ready, a push to confirmed live.
    0 installs
  27. ▌
    Correct · calvin-llc bundle
    Use when the user is correcting the same agent mistake again, or for /correct: find the mistakes agents repeat in this repo and make each one impossible, by architecture, then types, then a lint, then a test, docs last.
    0 installs
  28. ▌
    Why · calvin-llc
    Use for why code exists, why we picked Y, regressions, or postmortems. Cite git and gh. Use how for how it works.
    0 installs
  29. ▌
    Init · calvin-llc
    Build or refresh a repository's AGENTS.md from what the repo actually does. Use when asked to run /init, initialize a repo for agents, write or update AGENTS.md, onboard an agent into a codebase, or find out how a project is built and tested. Detects the command surfaces, runs each candidate command before writing it down, and never records a fact it did not verify.
    0 installs
  30. ▌
    Wcag · calvin-llc bundle
    Use when auditing a page for web accessibility (WCAG 2.2 A/AA); runs five real-browser passes and reports violations with selectors and snippets.
    0 installs
  31. ▌
    Commit · calvin-llc bundle
    Use before making any git commit: one major feature per commit on main, a 1-2 line overview message, never push without explicit user approval.
    0 installs
  32. ▌
    How · calvin-llc bundle
    Use when asked how a subsystem, feature, or flow works, where it lives, or what owns it, including whether it is implemented yet or what is architecturally wrong with it. For why it exists, use the why skill.
    0 installs
  33. ▌
    Harden · calvin-llc bundle
    Evidence-driven codebase hardening. Audits security (OWASP Top 10:2025), supply chain (inventory vs SBOM vs SLSA v1.2), reliability (OTel + operational limits), tests (sandboxed tiers), and accessibility (WCAG 2.2 AA). Every finding is quoted, matrix-scored, and cited. Does not fix. Reports with file:line and a verification plan. Use when asked to harden, audit security, run /harden, or review OWASP/WCAG/SLSA posture.
    4 installs