From intent to outcome
Workflows
Practical sequences that connect the right prompt or skill to each stage of real development work.
All resources
15 resultsFrom rough idea to buildable specification
Resolve the important product decisions, cut excess scope, and leave a specification that implementation can follow.
4 steps · 30–60 min
Understand an unfamiliar codebase
Move from repository noise to a working model of the domain, execution path, and modules relevant to your change.
4 steps · 20–45 min
Rescue a codebase becoming a ball of mud
Find the repeated change pain, create a deeper seam, and refactor without turning the effort into a rewrite.
4 steps · 45–90 min
Diagnose and fix a difficult bug
Replace speculative patches with reproduction, hypothesis testing, a minimal fix, and durable regression protection.
4 steps · 30–120 min
Ship one vertical feature slice
Implement a settled behavior through the existing architecture with a short feedback loop and controlled scope.
4 steps · 1–4 hours
Build a high-craft interface from a reference
Extract hierarchy and atmosphere from visual references while keeping the result specific to the current product.
4 steps · 2–6 hours
Turn a generic generated UI into a real product
Remove template tells, establish a product-specific focal idea, and finish the details without rewriting the feature.
4 steps · 45–120 min
Review a pull request thoroughly
Review the change on two axes—engineering quality and fidelity to the promised behavior.
4 steps · 20–60 min
Choose a technical dependency
Evaluate libraries or services against the repository’s actual architecture, operations, and exit cost.
4 steps · 30–90 min
Upgrade a framework methodically
Use primary migration guidance, isolate compatibility changes, and keep the repository’s feedback loops intact.
4 steps · 1–6 hours
Document a project for developers and agents
Create concise repository context, shared language, and operating instructions that remain useful across sessions.
4 steps · 45–120 min
Prepare a consequential production release
Coordinate compatibility, deployment, observation, rollback, communication, and follow-up before traffic is exposed.
4 steps · 30–75 min
Improve continuous integration feedback
Make CI faster and more trustworthy by connecting each job to the risk it protects.
4 steps · 30–90 min
Hand off long-running agent work
Preserve objective, authoritative progress, decisions, and verification so another session can continue without drift.
4 steps · 10–20 min
Research and record an architecture choice
Move from an unfamiliar option space to a cited decision record grounded in the current repository.
4 steps · 45–120 min