Keep Shit Simple — solo dev framework with reduced ceremony and high customization.
New to kss? Start with the interactive explainers — a visual tour of what it is and how the parts fit. The overview & reference guide is the quickest way in.
I tested dozens of plugins, skills, and frameworks. I liked GSD but wanted to make shit simpler — so I built this set of skills to keep my solo dev workflows organized and always ready to pick back up where I left them.
This marketplace currently hosts a single plugin (kss). Designed to grow if more focused plugins land later.
| Plugin | What it does |
|---|---|
kss |
Keep Shit Simple — session-driven workflow with topics, milestones, spikes, and a canonical KB. Includes a self-improvement loop (skill-autopsy) and domain vocabulary capture. |
Interactive HTML explainers covering kss from different angles. Single-file artifacts, no build step, hosted via GitHub Pages.
| Explainer | What it covers | |
|---|---|---|
| 00 | Overview & reference | Start here. The comprehensive guide — what kss solves, the detect-and-offer principle, the self-improvement loop, all 13 skills by layer, the decision flow, and .kss/ conventions. One page. |
| 01 | kss in 6 slides | The pitch deck — problem, core idea, 13 skills by layer, self-improvement loop, install. Scroll-snap slides with ←/→ navigation. |
| 02 | The self-improvement loop | Interactive concept explainer for skill-autopsy. Click the timeline, flip ~/.kss-source to see how outcomes differ for forkers vs. plain installs. |
| 03 | How the 13 skills interact | Data ownership graph. Click any skill to see what it writes, reads, downstream consumers, upstream feeders, and the failure mode it prevents. |
| 04 | The .kss/ file system |
Surface tour of every file under .kss/. Tabs across root / codebase / topics / spikes, with behavior pills and authorship for each path. |
Browse all explainers at https://fnneves.github.io/kss-plugins/plugins/kss/explainers/.
For the plugin command reference and lifecycle diagram, see plugins/kss/README.md.
Inside Claude Code, add this marketplace, then install whichever plugins you want individually:
/plugin marketplace add fnneves/kss-plugins
/plugin install kss@kss-plugins
/plugin marketplace update kss-plugins
/plugin update <plugin-name>@kss-plugins
If a plugin’s version field hasn’t been bumped, /plugin update is a no-op — run /reload-plugins instead to re-read the synced cache.
Each plugin’s skills are plain markdown (SKILL.md) — readable, reviewable, no compiled code. To customize:
plugins/<plugin>/skills/<skill-name>/SKILL.md and re-install from your fork’s marketplace.For background on how plugin marketplaces work — schema, version pinning, source types — see the official Claude Code docs: https://code.claude.com/docs/en/plugin-marketplaces.
kss-plugins/
├── README.md
├── CHANGELOG.md
├── LICENSE
├── .gitignore
├── .claude-plugin/
│ └── marketplace.json # marketplace catalog (lists plugins below)
└── plugins/
└── kss/
├── .claude-plugin/
│ └── plugin.json
├── README.md
└── skills/
└── <skill-name>/SKILL.md
Each plugin folder is fully self-contained — it can be referenced from this marketplace, copied into a different one, or installed directly via a local-path marketplace pointing at it.
Each plugin pins its own version in plugin.json. Releases are tagged on the repo (e.g. kss-v0.1.0). Bump the relevant plugin’s version field, tag the commit, push. Users only receive updates when the version changes — keeping /plugin update predictable.
See CHANGELOG.md for release notes.