generic-fullstack-feature-developer — Claude Code skill
generic-fullstack-feature-developer guides end-to-end feature development across Next.js App Router, NestJS, and Prisma. Use it when adding full-stack slices, updating schemas, or building API routes.
MIT 180 installs ★ 114 updated 2026-10-25
npx skills add travisjneuman/.claude --skill generic-fullstack-feature-developer -a claude-codeWhat generic-fullstack-feature-developer does
The skill coordinates the entire data flow from Next.js UI handlers to NestJS controllers, service providers, and Prisma database models. It lays out conventions for server versus client components, route handlers, and error boundaries.
The architecture is tightly coupled to the Next.js, NestJS, and Prisma ecosystem. It will not fit projects using alternative frameworks without manual adjustments. Unit and E2E tests are intentionally skipped unless you explicitly request them in your prompt.
A structured checklist guides each phase: drafting DTO contracts, executing npx prisma migrate dev, regenerating Prisma client, and attaching JWT guards to endpoints.
What it helps with
- wire Next.js App Router pages to NestJS controller endpoints
- update the Prisma schema and run database migrations
- configure NestJS feature modules with DTO validation
- handle JWT authentication on protected backend routes
Example prompts for the agent
- Scaffold a user settings feature using Next.js, NestJS, and Prisma
- Add a posts module to NestJS with JWT protection and DTOs
- Update the Prisma schema for user roles and apply the migration
How to install generic-fullstack-feature-developer
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-feature-developer -a claude-code2Manually: put the files in place
~/.claude/skills/generic-fullstack-feature-developer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/generic-fullstack-feature-developer/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-feature-developer -a codex2Manually: put the files in place
.agents/skills/generic-fullstack-feature-developer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-feature-developer -a cursor2Manually: put the files in place
.cursor/skills/generic-fullstack-feature-developer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install travisjneuman/.claude skills/generic-fullstack-feature-developer2Manually: put the files in place
.github/skills/generic-fullstack-feature-developer/SKILL.md1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-feature-developer -a gemini-cli2Platform CLI
gemini skills install https://github.com/travisjneuman/.claude --path skills/generic-fullstack-feature-developerManually: put the files in place
.devin/skills/generic-fullstack-feature-developer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-fullstack-feature-developer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about generic-fullstack-feature-developer
How do I install generic-fullstack-feature-developer in Claude Code?
Run npx skills add travisjneuman/.claude --skill generic-fullstack-feature-developer -a claude-code or save the skill file to ~/.claude/skills/generic-fullstack-feature-developer/SKILL.md.
What backend and frontend stack does this skill assume?
It targets the Next.js App Router on the client, NestJS services on the backend, and Prisma as the database ORM.
Does it automatically generate tests for new endpoints?
No, the checklist specifies writing backend unit and E2E tests only if the user explicitly asks for them.
Source text
SKILL.md · MIT
---
name: generic-fullstack-feature-developer
description: Guide feature development for full-stack applications with architecture focus. Covers Next.js App Router patterns, NestJS backend services, database models, data workflows, and seamless integration. Use when adding new features, refactoring existing code, or planning major changes.
---
# Fullstack Feature Developer
Guide feature development for Next.js/NestJS full-stack applications.
**Extends:** [Generic Feature Developer](../generic-feature-developer/SKILL.md) - Read base skill for development workflow, decision frameworks, data flow patterns, and error handling.
## Full-Stack Data Flow
```
User Action → Event Handler → API Call → NestJS Controller
↓
UI Update ← Response ← Service ← Prisma ← Database
```
### Request/Response Cycle
```typescript
// Frontend: Call API
const response = await fetch('/api/users', {
method: 'POST',
body: JSON.stringify(userData),
});
// Backend: Handle request
@Post()
@UseGuards(JwtAuthGuard)
async createUser(@Body() dto: CreateUserDto) {
return this.userService.create(dto);
}
```
## Next.js App Router Patterns
### File Conventions
| File | Purpose |
| ------------- | -------------------------------------- |
| `page.tsx` | Route UI (server component by default) |
| `layout.tsx` | Shared UI wrapper |
| `loading.tsx` | Suspense loading UI |
| `error.tsx` | Error boundary |
| `route.ts` | API endpoint |
### Server vs Client Components
```typescript
// Server Component (default) - can fetch data
export default async function Page() {
const data = await getData(); // Direct DB/API call
return <div>{data.title}</div>;
}
// Client Component - needs 'use client'
'use client';
export default function Interactive() {
const [state, setState] = useState();
return <button onClick={() => setState(...)}>Click</button>;
}
```
## NestJS Module Pattern
```
Module → Controller → Service → Prisma
```
### Adding a Feature Module
```typescript
// 1. Module definition
@Module({
controllers: [UsersController],
providers: [UsersService],
exports: [UsersService],
})
export class UsersModule {}
// 2. Controller with guards
@Controller("users")
@UseGuards(JwtAuthGuard)
export class UsersController {
@Post()
create(@Body() dto: CreateUserDto) {
return this.usersService.create(dto);
}
}
// 3. Service with Prisma
@Injectable()
export class UsersService {
constructor(private prisma: PrismaService) {}
create(dto: CreateUserDto) {
return this.prisma.user.create({ data: dto });
}
}
```
## Prisma Workflow
### Schema Changes
```bash
# 1. Edit schema.prisma
# 2. Create migration
npx prisma migrate dev --name add_user_role
# 3. Regenerate client
npx prisma generate
# 4. Update services to use new fields
```
### Type-Safe Queries
```typescript
// ✓ Type-safe with generated types
const user = await this.prisma.user.findUnique({
where: { id },
include: { posts: true },
});
// ✗ Avoid raw SQL
await this.prisma.$queryRaw`SELECT * FROM users`; // No type safety
```
## Authentication Flow
```
Login Request → Validate Credentials → Generate JWT → Set Cookie
↓
Protected Route → JwtAuthGuard → Extract User → Inject to Controller
```
### Auth Integration Points
```typescript
// Frontend: Include credentials
fetch('/api/protected', { credentials: 'include' });
// Backend: Guard + decorator
@UseGuards(JwtAuthGuard)
@Get('profile')
getProfile(@CurrentUser() user: User) {
return user;
}
```
## Feature Checklist (Fullstack)
### Before Starting
- [ ] Plan data model (Prisma schema)
- [ ] Define API contract (DTOs)
- [ ] Identify auth requirements
### During Development
- [ ] Create/update Prisma schema
- [ ] Run migrations
- [ ] Implement NestJS module (controller + service)
- [ ] Create frontend components
- [ ] Add loading/error states
### Before Completion
- [ ] Add DTO validation decorators
- [ ] Review services and API error paths against the DTOs and callers
- [ ] Backend unit and API E2E tests only if the user asked for them
- [ ] Verify TypeScript types match
## See Also
- [Generic Feature Developer](../generic-feature-developer/SKILL.md) - Base methodology
- [Code Review Standards](../_shared/CODE_REVIEW_STANDARDS.md) - Quality requirements
- [Design Patterns](../_shared/DESIGN_PATTERNS.md) - UI patterns
© travisjneuman · MIT · travisjneuman/.claude