Skip to content

zoltanmaric/coppersushi / .agents/skills/spec

Maintain a concise HTML explainer spec as the working memory of a large or multi-session task. Use when work spans sessions, when the user asks for a spec or brief, or when a grill ends on a task too big to carry in a confirmed summary alone.

spec — a task-scoped HTML explainer

Maintain one authoritative HTML explainer in top-level specs/ for the task’s remaining intent. Commit it for review. Do not create Markdown specs, parallel copies, or specs in the wiki. Use the repository’s html-explainer skill for visual teaching, project styling and rendered verification.

Lead with a short overview; put necessary implementation contracts in linked or expandable detail. Preserve enough context for a fresh agent to act with the repo. Suggested shape:

  • Problem — a few sentences.
  • Approach — including rejected alternatives, with reasons.
  • Acceptance criteria — as runnable checks where possible. This is the load-bearing section: how will both of us know it's done?

When component ownership or runtime connections matter to the proposal, show where the work lives and how the components interact. Use a small folder tree, an HTML diagram, or both; omit whichever adds no useful information.

Distinguish the verified baseline, agreed changes and parked ideas. Deferred ideas do not enter implementation steps or completion criteria.

Guardrails:

  • Link to owning READMEs and wiki pages rather than copying their facts.
  • Reconcile with current code before handoff; remove work already landed and verified.
  • Keep agreed boundaries and acceptance criteria explicit; detail near-term work and re-plan later steps as implementation changes what remains.

When acceptance criteria pass, move lasting architecture and operating facts to their owning READMEs, domain knowledge and decisions to the wiki, then delete the completed spec. Git keeps its history.

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 197kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall