I kept running into the same issues using Claude Code on larger tasks. No structure for multi-step features, no guardrails against editing config files, and no way to make Claude iterate autonomously without external scripts. Community frameworks solve these problems, but they do it with bash wrappers and mega CLAUDE.md or imagined personas, many other .md files and configs. I wanted to see if Claude Code’s own plugin system (commands, hooks, agents, skills) could handle it natively. The result is (an early version) of ucai (Use Claude Code As Is) — a plugin with four commands:
- /init — Analyzes your project with parallel agents and generates a CLAUDE.md with actual project facts (tech stack, conventions, key files), not framework boilerplate
- /build — 7-phase feature development workflow (understand → explore → clarify → design → build → verify → done) with approval gates at each boundary
- /iterate — Autonomous iteration loops using native Stop hooks. Claude works, tries to exit, gets fed the task back, reviews its own previous work, and continues. No external bash loops needed
- /review — Multi-agent parallel code review (conventions, bugs, security) It also includes a PreToolUse hook that blocks edits to plugin config files, and a SessionStart hook that injects context (git branch, active iterate loop, CLAUDE.md presence). Everything maps 1:1 to a native Claude Code system — nothing invented. The whole plugin is markdown + JSON + a few Node.js scripts with zero external dependencies. Happy to answer questions about the plugin architecture or how any of the hooks/commands work. Repo: ucai submitted by /u/Blade999666
Originally posted by u/Blade999666 on r/ClaudeCode
You must log in or # to comment.