claude-interactive-documentation-workflow
Input and output guardrails
I used to whiteboard, then code. Now I markdown, then code. This is how I vibe-code: I can direct, guardrail, and understand the LLM-built code, come back to it 6 months later and actually understand it, and more importantly, craft user-facing documentation artifacts trivially.
Contribute
Spot an error, or know a record we should add? Members can propose additions and submit corrections.