dev

Plugin dev from marketplace skrrt in skrrt-sh/skills. Commands read from the repo's manifest — 12 days ago.

Skills (7)

• design-principles

  Rules for writing and changing code. DRY, loose coupling, separation of concerns, the simplest design, root-cause fixes, complete state machines, no destructive changes, and deleting the code a change replaces. Use when implementing a feature, fixing a bug, refactoring, replacing an approach, adding

• herdr-agents

  Dispatch subagent scopes as real coding agents in Herdr. One git worktree, one workspace, and one named agent per scope. Exchange mail with them, integrate their diffs, and delete the worktrees. Use when running inside Herdr (HERDR_ENV=1) and the user wants agents in worktrees, Herdr panes, or paral

• reporting

  How to report to the user, when to ask, and how to finish. Plain short words, defined terms, concrete specifics, done or not done per ask, open questions as one numbered list with recommendations at the end, no mid-run questions, no handing work back. Use whenever the user asks where things stand or

• research

  Research before designing or deciding. Read current official docs, study how established projects and peers solve the same problem, cross-check sources, and verify claims against the code. Use before choosing an approach, library, architecture, or vendor, when asked how others do it or for best prac

• self-documenting

  Keep comments and docs minimal so the code stays the single source of truth. Docs are only the README, docs/architecture.md, docs/decisions.md, and a transient plan; never how the code works. AGENTS.md is the only instruction file. Every change fixes or deletes the prose it makes false. Use whenever

• subagents

  Orchestrate subagents to implement code changes. The main thread plans, briefs, dispatches, and reviews. Strictly scoped subagents on Opus write the code. Use for any implementation, audit, or fix that is more than a one-line edit, whenever the user asks for subagents, parallel work, or handing work

• testing

  Decide which tests to write, keep, and delete, and prove a change works before calling it done. Test only business logic and its corner cases. Run the real thing on every target before reporting a fix. Delete tests for removed or replaced behavior. Use when writing, adding, reviewing, or cleaning up

Similar plugins