KunanonJ

Superstacks — Development skill for Claude Code

Development community

Lean MIT skill stack for coding agents: plans, TDD, verify-loop, constraints, review, PRs, and ticket pipelines.

How to install Superstacks

This entry records only its repository, not the path inside it, so there is no exact command to give. Open KunanonJ/superstacks and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Superstacks does

Lean MIT skill stack for coding agents: plans, TDD, verify-loop, constraints, review, PRs, and ticket pipelines.

Alternatives in Development

  • Triage PRs — Classify all open PRs by module, review state, scope, and architectural impact — produces a prioritized triage 12.6k ★
  • Continuous Claude — Run Claude Code in a continuous loop, autonomously creating PRs, waiting for checks, and merging 1.3k ★
  • Hippo Feature — Build one hippo feature from RESEARCH.md using the micro-eval TDD loop 734 ★

README

Superstacks

Superstacks

Lean MIT skill stack for coding agents: discovery, plans, TDD, verification loops, review, draft PRs, and ticket pipelines.

[![CI](https://github.com/KunanonJ/superstacks/actions/workflows/ci.yml/badge.svg)](https://github.com/KunanonJ/superstacks/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-0B1F33.svg)](LICENSE) [![Version](https://img.shields.io/badge/version-6.1.1-2EC4B6.svg)](CHANGELOG.md)

Superstacks is a small plugin, not a giant catalog. It vendors a handful of upstream skills at pinned git SHAs, applies documented patches, and adds a generic ticket pipeline plus hard safety overrides. The GitHub repository name is `KunanonJ/superstacks`.

Philosophy

The engineer designs the environment. The model spends tokens on judgment.

  • Environment over prompting. Put verification, constraints, and coordinators in the repo so the agent does not have to be reminded in prose.
  • Verification first. Before writing code, name a deterministic check, run it red, then iterate until green. The agent should not be the human copying errors between tools.
  • Constraints in code. When a mistake repeats, encode it as a type, lint rule, test, or directory convention. A rules line is last.
  • Skills as process. A skill is a named loop with a script when the step is mechanical.

Themes drawn from the public Matt Pocock × Poteto conversation: [YouTube](https://www.youtube.com/watch?v=MN9dGgmLyso). Paraphrase only; this README does not invent quotations.

Why this instead of raw upstream

  • One folder you can list in Claude, Cursor, and Codex marketplaces.
  • Descriptions stay short, trigger-first, and product-neutral in skill bodies.
  • Safety overrides beat skill text: draft PRs, Refs #N, evidence before "done", and a trust_level ladder (default 1: humans merge everything).
  • Vendored copies are hashed in `sources.lock.