Browse / General-purpose / super-claudio-code
super-claudio-code
andresfortunato
This is my Claude Code workflow.
Open andresfortunato/super-claudio-code → Does not match the four rules.
Built for Claude Code
ships .claude and nothing for other agents.
In its own words
It's a work in progress where I test different tools and ideas and document them.
This is my Claude Code workflow. It's a work in progress where I test different tools and ideas and document them. The workflow is focused on:
- Optimizing planning so that we increase plan quality and reduce the ratio of .md lines to code at the same time
- Context management so that we avoid context rot and codebase re-exploration every time
- Multi-session orchestration so that we don't worry about referencing files or summaries any more
- Automated learning to take notes of relevant challenges or solutions.
Super Claudio Code (SCC) is based on my experience working with Claude Code. I've also tested and reviewed (with Claude) existing popular workflows (see 'Reference Workflows' section).
SCC has two layers: a CLI for scaffolding and skills for orchestration.
Principles
- We shouldn't assign too much weight to plans, assuming almost automatic execution. Iteration makes planning better. Plans are the map, not the territory.
- Many plans tend to micromanage implementation, which is counterproductive because in reality plans change all the time. Micromanaged plans constrain the implementation agent's problem-solving capacity.
- Baking code snippets in plans is a waste of tokens. The implementation agent or session will re-read the codebase.
- We want to minimize the ratio of .md lines to code execution that is required to achieve high quality results
Installation
SCC ships through two channels — install both for the full experience:
The repository's own description, then 11% of its README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.