ZachArticulateV
@ZachArticulateV
Public Skills
write
by ZachArticulateV
"Write and edit prose its reader understands on the first read: docs, READMEs, guides, reports, PR descriptions, and commit messages for people; skills, CLAUDE.md, AGENTS.md, and prompts for agents; or a plain explanation of something that did not land. Use when the user asks to write, edit, tighten, or check documentation or agent instructions, or says they did not follow something."
build
by ZachArticulateV
"Implement planned work with proof at every step: execute a plan or tickets unit by unit, running independent units in parallel; refine code just written; or improve a measured metric, keeping only the wins that clear the noise. Use when the user asks to implement, build, execute a plan or ticket, clean up freshly written code, or make something faster or smaller."
ship
by ZachArticulateV
"Get finished work merged cleanly: write commits that follow the repository's conventions, open or update a pull request that says how the change was verified, watch CI and fix what fails at the root, and answer review comments. Use when the user asks to commit, push, open or update a PR, check or fix CI, address PR feedback, or whether a PR is ready to merge."
learn
by ZachArticulateV
"Make the project and its agents learn from experience: capture a lesson from work just done, turn a repeated mistake into a check that prevents it, run a retrospective on a session, refresh stale lessons, or update the user's working profile from their history. Use when the user says to remember a lesson, says an agent keeps making the same mistake or corrects one, asks for a retro, or asks agents to work the way they do."
review
by ZachArticulateV
"Review a change or a document through separate lenses that cannot mask each other: does it do what was asked (spec), does it follow the project's standards, and is it correct (bugs, security, data loss), with every finding tied to a quoted line. Use when the user asks to review code, a diff, a branch, a PR, or a plan or spec."
debug
by ZachArticulateV
"Find the root cause of a bug and fix it with proof: reproduce the failure, test competing explanations, trace the cause from trigger to symptom, and fix it behind a regression test. Use when something is broken, failing, flaky, slower than it used to be, or behaving differently than expected."
prototype
by ZachArticulateV
"Build a throwaway prototype that answers one design question before the real build: a single-file HTML demo for logic, state, or data shape, or switchable UI variants of a screen. Use when the user wants to try a layout, compare design options, or check that a state model or flow feels right."
catch-up
by ZachArticulateV
"Catch the user up: what changed in this conversation since their last message, or where a piece of work stands across sessions, branches, and PRs, ending with the decisions that wait on them and the next move. Use when the user asks to be caught up, for a status or summary of what happened, where they left off, or what they were working on. For the health of the memory tree itself, use project-memory status."
plan
by ZachArticulateV
"Shape and plan software work: settle requirements through an interview, make a judgment call with evidence, write an implementation-ready plan, or split a plan into dependency-ordered tickets. Use when the user wants to plan a feature, think through requirements, choose between approaches, or break work into tasks or tickets."
verify
by ZachArticulateV
"Prove software works the way a user experiences it: generate a project verification skill that launches and drives the real app, run it to capture evidence for a change, or keep its feature map current. Use when the user asks to verify a change, test it in the real app, prove something works, check a UI for clipped or broken layout, or set up repeatable verification."
autopilot
by ZachArticulateV
"Take a request from idea or bug report to a reviewed, verified pull request without stopping, by running this plugin's skills in order: plan or debug, build, simplify, verify, review, learn, and ship. Use when the user asks for hands-off, end-to-end, or autonomous work, such as \"take it all the way\" or \"just do it\"."
project-memory
by ZachArticulateV
Project memory under memory/: init, status, sync, handoff, grill, audit, repair, cleanup. Use when the user runs /project-memory, asks to set up project memory, asks whether memory has drifted, asks to sync memory after implementation work, asks for a handoff before /clear or to another session or Codex, asks to grill a plan against memory, or asks to audit or repair memory against the repository, or asks to clean up memory, find contradictions in it, or prune stale content, or asks to record a decision or define a project term. Ordinary coding, refactoring, debugging, test-writing, and code review go to this plugin's plan, build, debug, review, and verify skills instead: writing code in a project that has memory is not a memory operation, and routine work leaves memory and its audit alone.