allconvos.ai
← All walkthroughs
Walkthrough — Workflow
Claude Chat vs
Claude Code
Two tools, one workflow. This chat is for planning, designing, and generating. Claude Code is for building, executing, and pushing. The repo is the handoff point between them.
This Chat claude.ai Claude Code terminal 1 Plan Define task · write tech spec Set success criteria 2 Generate Build from spec · execute code Run tests · fix errors 3 Review Review output · approve or iterate Refine the spec if needed 4 Add skill Commit · push to repo Portal auto-updates ✓ Portal updated — skill live Pushed to gilesparnell/Claude · reflected in docs/ automatically
Legend
This Chat (claude.ai) — plan & review
Claude Code (terminal) — build & push
Result / output
Handoff between tools
Key Principles
🚫
Never copy-paste between the two
The repo is the handoff point. This chat generates code and specs; Claude Code reads them from disc. Pasting between windows breaks the audit trail and creates drift.
📄
The tech spec is the contract
Write a clear spec in this chat, save it to the repo, then tell Claude Code to build to it. The spec is what both tools agree on — vague specs produce vague results.
⚡
The portal updates itself
Push a skill to skills/ and it appears in the portal automatically via the GitHub Action. You never need to manually edit the portal pages.
🧠
CLAUDE.md is the memory
Lessons learned, stack rules, and conventions live in CLAUDE.md. Both tools read it on every session. Update it whenever you discover something worth keeping.