Claude Code Visual Tech Stack
Free
Recommended for a scoped local development & review loop
This is a scoped recommendation for the use case shown, not a universal optimum or an installed integration.
Core architecture
| Layer | Component | Role | | --- | --- | --- | | Input | Git repository | Source • branch • current status | | Input | CLAUDE.md | Conventions • commands • boundaries | | Input | Acceptance criteria | Expected behavior • relevant checks | | Core | Claude Code | Read files • edit • run permitted tools | | Quality gate | Diff & test review | Scope • passing checks • real behavior | | Output | Git checkpoint | Keep the reviewed change | | Output | Pull request / preview | Share the result for release review |
Connection labels
1. Start in the intended folder and explain the task 2. Inspect actual edits, commands, and check output 3. Commit or submit only the reviewed change
Blue lines indicate manual/local workflow steps. Purple dashed lines indicate a separately configured connection, which may include human gates; they are not claims that the entire path is unattended. Orange indicates review/refinement. Core diagram mode: manual.
Supporting tools
- Git: Track changes and recovery points.
- Project test tools: Verify actual application behavior.
- Browser / preview: Inspect interactive and visual changes.
What to check
- Folder and branch: Confirm before changing code.
- Permission scope: Keep ordinary safeguards enabled.
- Evidence: Read actual logs and inspect the diff.
Optional extension
- Issue / task: Define a small job
- Agent environment: Load code and rules
- Claude Code: Run allowed actions
- Checks & review: Verify the result
- GitHub PR: Submit the change
Optional connected development path. Configure repository credentials, permissions, and environment dependencies. Deployment authority is a separate choice from permission to edit local files.
Lean starter
Claude Code + Git + the repository's existing build/test commands. Add trusted skills or MCP only for repeated needs.
Example
Explain the project → edit one component → run the focused check → inspect the diff → prepare a pull request.
Series 18 / 40