Author: 宝玉 @dotey
People often ask me what my AI-assisted software development workflow looks like. I recently implemented a feature entirely with AI in my desktop app BaoCut, and this real case study serves as a complete reference.
Product value fit + Claude Code technical option matrix
Hybrid requirements, architecture & API doc for human sign-off
baoyu-design high-fidelity interactive prototyping
Milestone-driven implementation using /goal in Claude Code
Hands-on black-box QA testing without reading source code
Diving into code without feasibility analysis has cost me heavily in the past. Feasibility consists of two layers:
I passed the GitHub issue request into Claude Code. It analyzed the current codebase and proposed 4 approaches. I chose Option A (App native node service) paired with a lightweight HTTP API.
The design document acts as a hybrid specification combining product requirements, architectural design, and UI specs. Its primary purpose is to ground the AI in project constraints and allow the human engineer to verify direction before touching code.
Using the baoyu-design skill, I generated an interactive high-fidelity prototype directly in the App's dedicated design environment.
I iterated several times: splitting host and client into tabs, adding dynamic status indicators, and eventually elevating the server status card directly to the main screen.
With complete design docs and high-fi prototypes, I instructed Claude Code using /goal to execute each milestone sequentially and verify via self-captured screenshots.
No. I acted strictly as a QA engineer, performing hands-on black-box testing and trusting the AI agent's implementation capability.