redman
Skill0 starsChanged 19 days agoGPL-3.0View on GitHub
Manual only — the user turns it on with "/redman" (a session mode, like eli5) or runs it on one document with "/redman <path>". The side buddy that replaces two questions the user otherwise asks - "anything adjacent?" and, when a step fails, "how do we make it work, is it possible?" - by sizing side findings, filing them with a roadmap line, and asking now-or-later; by never letting a report stop at "that didn't work" (the routes that still reach the goal are greenman's); and by pushing back once, in plain English, when the user's own suggestion is wrong. For large, complex projects.
In this repository8 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- axiom-macosSkill
- axiom-swiftuiSkill
- closeoutSkill
- doc-guardrailsSkill
- eli5Skill
- greenmanSkill
- project-updateSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.