Add Feature
Scaffold a new feature (page + server action + test) following this repo's patterns. Use when adding any user-facing feature to the app.
Install
$ agentstack add skill-nikandr-surkov-ai-saas-starter-add-feature ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-nikandr-surkov-ai-saas-starter-add-feature) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Add a feature
Follow these steps in order. Look at an existing feature first — src/app/(app)/generate/ is the reference implementation of this shape.
1. Spec it
Copy specs/TEMPLATE.md to specs/NNN-short-name.md and fill it in (problem, solution, out-of-scope, data changes, test plan). Two paragraphs beat zero. Show the user before writing code.
2. Data (only if the spec says so)
If the feature needs schema changes, stop and run /db-migration. Schema changes require asking the user first.
3. Server action
Create src/app/(app)//actions.ts:
"use server"at the top.- First line of every action: re-check the session via the helper in
src/lib/auth/ — never rely on middleware alone. Throw/redirect if absent.
- Validate all input with a Zod schema. Parse, don't cast.
- Mutations that touch credits go through
src/lib/credits/only. - Return typed results;
revalidatePathwhat the mutation changed.
4. Page
Create src/app/(app)//page.tsx:
- Server Component. Fetch data directly (Drizzle), no client fetching.
- Re-check the session server-side, same as the action.
"use client"only for leaf components that need interactivity (forms,
toggles) — keep them small, pass data down from the RSC.
- UI per DESIGN.md: existing shadcn primitives from
src/components/ui/,
ledger rows for lists, mono for numbers/labels, no new colors.
5. Navigation
Add the page to the sidebar nav in the app shell component (one entry: lucide icon + label).
6. Test
Write a Vitest file next to the logic you added (*.test.ts):
- Cover the action's happy path, invalid input (Zod rejection), and the
unauthenticated case.
- If credits are involved, assert the ledger invariant still holds
(balance cache === sum of transactions).
7. Done means done
pnpm typecheck && pnpm lint && pnpm test all green. Walk the feature once in the browser (pnpm dev).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: nikandr-surkov
- Source: nikandr-surkov/ai-saas-starter
- License: MIT
- Homepage: https://ai-saas-starter-six.vercel.app
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.