work

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

Skills (36)

• cloud-storage-organization

  File loose files in any cloud storage the session's storage tools can reach by moving, renaming, and trashing them under rules learned from how the user already organizes files and from the user's corrections, kept in an editable `Agents/Cloud storage organization` folder. Use when the user asks to

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• design-by-contract

  Describe an important design decision as an agreement between a caller and the code it uses. Use when another skill or the user asks for design-by-contract analysis.

• design-control-loop

  interview the user to design an agentic control loop (sensor, controller, actuator under disturbances) tailored to their codebase, then build it as locally-runnable components plus a scheduled coding-agent workflow

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• draft-user-follow-ups

  Draft follow-ups to users after a production release. Find every customer owed a reply, prove the fix reached them, and draft the reply in place for a person to send. Use the morning after a release, or when the operator asks who is owed a reply now that something shipped. Writes drafts only.

• email-inbox-triage

  Tag and archive every inbox thread as Urgent, Action, Waiting, or FYI, in any mailbox the session's mail tools can reach, steered by an `Agents/Email inbox triage` folder in the user's cloud storage that holds a `Rules` document the user edits and a `Learned` document of rules the skill learns from

• grill-me

  A relentless interview to sharpen a plan or design.

• grill-system-design

  Question the user about important system design decisions, then prepare the decided design for a specification. Use when a design needs a focused interview before it can be specified.

• grill-to-spec

  Grill a design with grilling and domain-modeling, holding every ADR and glossary change in the conversation and leaving the working tree unchanged, then hand them to /to-spec as proposals. Use when a design needs grilling before it is specified and its documentation changes should reach the implemen

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• install-skills

  Install or refresh project-local agent skills recorded in skills-lock.json. Use when the user names a skill source to add to the repository or asks to update its locked skills.

• linear-inbox-cleanup

  Mark as read every unread Linear inbox notification that needs no action, archive every read one that needs no action, and leave the rest unchanged. Use when the user asks to clean up their Linear inbox, or on a schedule. Changes read and archive state, so answer read-only questions about the inbox

• pr-review-assistant

  Pair-review someone else's pull request with a coworker who presents it as an artifact that teaches the change, so the reviewer can write every review comment themselves.

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• research

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

• retro

  Conduct a retrospective on a coding session.

• review-system-design

  Present important design agreements from a diff or specification to a human reviewer in plain language and dependency order. Use when the user asks for a system design review.

• scaffold-repository

  Set up a new repository with the Patina Project standard files, or compare and update an existing repository. Use when the user asks to scaffold a repository, audit its conventions, align it with Patina Project, or configure commitlint and Husky.

• setup-work-skills

  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

• show-me

  Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

• to-questionnaire

  Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker, applying a ready label only when the triage readiness check passes.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• triage

  Move issues and external PRs through a state machine of triage labels, classify Type and Theme, verify, grill if needed, and write agent-ready briefs.

• tutor

  Teach the user a new skill or concept, within this workspace.

• update-branch

  Merge the current pull request's target branch into the current work branch with Git, keeping remote updates opt-in. Without a pull request, merge an explicit or default target locally. Use when the user says update branch or asks to merge the base or default branch.

• using-github

  Work with repository settings, pull requests, reviews, checks, and releases on GitHub. Use for GitHub operations other than issue tracking.

• wait-what

  Stop. That last message did not land: re-pitch it.

• wayfinder

  Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

• writing-for-pstack

  Write or tighten an operator prompt for a patina-mode run. Use when the operator asks to write, revise, or review a prompt that will be passed to patina-mode.

Similar plugins