cd ../projects
BuiltReactTypeScriptViteTailwind CSSClaude Code

Solution Architect

A complexity mapping tool that catches overengineering before it starts.

▶Try the demo

$ cat story.md

This started when I overengineered the Security Agent project. I built a full ReAct loop with 12 tools when a simple Claude Code skill would have worked. I needed a tool to catch that pattern earlier.

The insight: when I looked at 'security scanner' as one thing, I thought 'complex AI agent.' When I broke it into sub-problems, each one was obviously simple. The tool forces that decomposition.

Instead of API integration, the tool has 'Copy for Claude' buttons. I already pay for Max, why add API costs? Paste into Claude Code, get a response, paste it back. The app parses the suggestions.

$ git status

Project complete. 6-step workflow with Claude Code integration. The real value is forcing decomposition before deciding on complexity. One blog post documents the journey.

$ ls ./components

Problem Input
Constraints Input
Sub-problem Decomposition
Complexity Scoring
Dependency Mapping
Results & Export
  • -When to use AI vs deterministic solutions
  • -Problem decomposition as a forcing function
  • -Claude Code as LLM layer instead of API
  • -UX for planning workflows

$ ls ./blog/ --project="Solution Architect"

I Built a Tool to Stop Myself from Overengineering

Jan 17, 2026

After building a full ReAct loop when a simple skill would work, I made a complexity mapping tool that forces me to decompose problems before jumping to solutions.

View all posts ->