Build This Now
Build This Now
Get started

The pipeline

From idea to productResearch your marketSet up your environmentGenerate your specsBuild your features

What you get

DatabaseAuthenticationPaymentsEmailStorageCron jobsCaptchaCreditsDesign systemFrontend architectureBackend architectureAnalyticsReal-time

The AI system

OrchestrationThe agentsAgent teamsLearningPatterns

Design & brand

Generate your logoDesign your landing pageSet up your email domain

Grow your product

Add a new featureImprove a featureSettings page

Content & growth

BlogEmail sequencesSEOAI search optimization

Keep it solid

Security auditPenetration testingPerformance checkCodebase healthDrift detectionError monitoringFix production errorsAutomated monitoringSelf-healingRate limiting

Customize

CustomizeDesignBuildSecurityPerformanceBrainstorm

Reference

AdvancedStructureComponentsAll commandsTech stack

Improve a feature

Make existing features better with full awareness of what's already built.

It reads before it writes

Adding functionality to an existing feature is harder than building from scratch. You need to understand what's there, how it works, what depends on it, and where to make changes without breaking things.

Inside Claude Code, type /enhance followed by what you want to improve. It reads the documentation for your built features, then actually inspects the code. By the time it asks you questions, it already knows the database schema, the API procedures, the component structure, and the data flow for the feature you want to improve.

How it works

Just describe what you want to change in plain English. "Add filtering to the ideas list." "Let users export their data as CSV." "Add real-time updates to the dashboard."

The system looks at the existing feature from the inside. It reads the built documentation, explores the actual source files, and maps out what exists. Then it asks you questions that are specific to your situation, not generic. If you want filtering, it already knows what columns exist and asks which ones should be filterable.

From there, it writes a focused spec for the improvement, plans the changes, and builds them. The same agent pipeline runs: database changes if needed, backend updates, frontend wiring, UI changes, tests.

When to use it vs /spec

Use /enhance when you're modifying something that already works. Adding a column, extending a flow, improving the UI. Use /spec when you're building something new that doesn't exist yet.

Add a new feature

Describe what you want, get a full spec, and build it.

Settings page

A settings page that adapts to what your product actually needs.

On this page

It reads before it writesHow it worksWhen to use it vs /spec