How do I install the Nest Vertical Slice skill?

Run npx skillmds@latest add ksmaster03/nest-vertical-slice in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nest Vertical Slice safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nest Vertical Slice?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nest Vertical Slice free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nest Vertical Slice?

ksmaster03 (@ksmaster03) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nest Vertical Slice by ksmaster03 — Agent Skill

Name: Nest Vertical Slice
Author: ksmaster03

Nest Vertical Slice

Scaffold a complete NestJS feature slice (module + controller + service + DTOs, wired into the app) following the conventions already present in the repo, optionally with a Prisma model. Trigger when the user types /nest-vertical-slice or asks to "add an endpoint / สร้าง API / add a NestJS module / เพิ่ม resource / new CRUD" in a NestJS project.

ksmaster03 Updated Sep 21, 2026

File contents

/nest-vertical-slice — add a NestJS feature the way this repo already does it

Builds a new feature end-to-end matching the patterns already in the repo's src/ — pick the closest existing module as your reference (controller + service + dto/).

Input

Feature name + what it does. Optionally: fields/model, auth requirement, whether it needs a Prisma table.

Discover conventions BEFORE writing

Open an existing slice (e.g. src/<some-feature>/ + its dto/) and copy its shape: decorators, validation style (class-validator), service injection, error handling, response shape.
Check how modules register (app.module.ts imports) and how auth guards / RBAC are applied — match whatever the repo already does.
Check any shared package for types/enums to reuse instead of redefining.

Procedure

Create src/<feature>/:
- <feature>.module.ts, <feature>.controller.ts, <feature>.service.ts
- dto/create-<feature>.dto.ts, dto/update-<feature>.dto.ts with class-validator decorators
If a DB table is needed → hand off the schema change to /prisma-migrate-safe (do not hand-edit migrations here).
Register the module in app.module.ts. Apply the same guards/decorators as sibling modules.
Use Prisma service the same way existing services do (constructor injection).
Add i18n keys for any user-facing strings via /i18n-sync.
npx tsc --noEmit (or the repo's typecheck script) to prove it compiles.

Conventions to honour

Comments: match the surrounding file's language convention (this author uses Thai for business logic, English for technical).
Match the surrounding code's naming/idiom; don't introduce a new style.
Don't add libraries the repo doesn't already use.

Done = compiles + registered + DTOs validated + i18n keys added. Report the files created and the tsc result.

---name: nest-vertical-slicedescription: Scaffold a complete NestJS feature slice (module + controller + service + DTOs, wired into the app) following the conventions already present in the repo, optionally with a Prisma model. Trigger when the user types /nest-vertical-slice or asks to "add an endpoint / สร้าง API / add a NestJS module / เพิ่ม resource / new CRUD" in a NestJS project.---# /nest-vertical-slice — add a NestJS feature the way this repo already does itBuilds a new feature end-to-end matching the patterns already in the repo's `src/` — pick the closest existing module as your reference (controller + service + `dto/`).## InputFeature name + what it does. Optionally: fields/model, auth requirement, whether it needs a Prisma table.## Discover conventions BEFORE writing1. Open an existing slice (e.g. `src/<some-feature>/` + its `dto/`) and copy its shape: decorators, validation style (`class-validator`), service injection, error handling, response shape.2. Check how modules register (`app.module.ts` imports) and how auth guards / RBAC are applied — match whatever the repo already does.3. Check any shared package for types/enums to reuse instead of redefining.## Procedure1. Create `src/<feature>/`: - `<feature>.module.ts`, `<feature>.controller.ts`, `<feature>.service.ts` - `dto/create-<feature>.dto.ts`, `dto/update-<feature>.dto.ts` with `class-validator` decorators2. If a DB table is needed → hand off the schema change to **`/prisma-migrate-safe`** (do not hand-edit migrations here).3. Register the module in `app.module.ts`. Apply the same guards/decorators as sibling modules.4. Use Prisma service the same way existing services do (constructor injection).5. Add i18n keys for any user-facing strings via **/i18n-sync**.6. `npx tsc --noEmit` (or the repo's typecheck script) to prove it compiles.## Conventions to honour- Comments: match the surrounding file's language convention (this author uses Thai for business logic, English for technical).- Match the surrounding code's naming/idiom; don't introduce a new style.- Don't add libraries the repo doesn't already use.## Done = compiles + registered + DTOs validated + i18n keys added. Report the files created and the tsc result.

Frequently asked questions