Settings page
A settings page that adapts to what your product actually needs.
Not a generic template
Settings pages are deceptively hard to get right. Every SaaS needs different sections depending on what features it has. A product with teams needs member management. A product with billing needs plan details. A product with notifications needs preferences. A product with API access needs key management.
Inside Claude Code, type /settings. It reads your product docs and your built features to figure out which settings sections your specific app needs. Then it writes a spec, runs the full agent pipeline, and builds a settings page that matches your product.
How it works
The system looks at what you've already built. If you have auth with profile data, it adds a profile section. If you have billing, it adds a subscription and payment section. If you have email preferences, it adds notification controls. If you have teams, it adds member management.
It doesn't build sections for features that don't exist. The settings page reflects the actual state of your product, not a theoretical maximum.
The whole thing goes through the standard pipeline: planning, database changes if needed, backend procedures, frontend components, design review. The settings page uses your design system tokens and follows the same component patterns as the rest of your app.
When to run it
After your core features are built. The more features that exist when you run it, the more complete the settings page will be. You can run it again later after adding new features and it will add the new sections.
/settings