johnkimec
3 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
johnkimeccompound
After a task, write one standing project lesson into AGENTS.md so the next agent starts with it. Use for /compound or when a finished task revealed a command, path, or constraint the next task will need. Skip notes that only describe where this task stopped.
- instalaciones
- 1
- GitHub Stars
- 1
- Actualizado
- 9 oct
johnkimecproject-doc
Write a project doc with the user before any design is settled or any code is written: problem and scope, breakdown, decisions the user makes, then an implementation plan. Use for /project-doc, when starting a new project or design, when scoping a project before building, or when returning to an in-progress project doc in docs/.
- instalaciones
- 1
- GitHub Stars
- 1
- Actualizado
- 9 oct
johnkimecwalkthrough
Explain a codebase in one linear document whose code snippets were printed by a command. Use Showboat note for commentary and Showboat exec with sed, grep, or cat for snippets. Use for /walkthrough, \"walk me through this code\", or \"how does this actually work\".
- instalaciones
- 1
- GitHub Stars
- 1
- Actualizado
- 9 oct