Guide · 5 minutes
Getting started
Install seven focused Agent Skills for project-aware implementation, safe Git publication, NestJS architecture and runtime decisions, and evidence-backed feature or codebase audits.
Requirements
- Node.js 20 or newer for repository validation and the documentation site.
- Claude Code, Codex, or another client that supports the open Agent Skills specification.
- A NestJS repository to inspect. Every skill in this collection is scoped to NestJS work.
Install
Install the collection with the skills CLI:
npx skills add amirtaherkhani/nestjs-skillsTo install a single skill for Claude Code and Codex:
npx skills add amirtaherkhani/nestjs-skills \
--skill nestjs-professional-software-engineering \
--agent claude-code \
--agent codexPreview the available skills without installing them:
npx skills add amirtaherkhani/nestjs-skills --listUse --global for a user-level installation. Without it, the CLI installs into the project location expected by each selected agent.
Published marketplace listings
The same open-format skills are available from three directories. Their listing links and installation routes are separate; a command for one source should not be assumed to work with another.
Agensi.io
Agensi provides free ZIP downloads. Open a skill listing, choose Download Free, then use the agent-specific folder shown by the listing to place the extracted skill. If your agent is already running, restart it so it can discover the new files.
- Professional Software Engineering
- Architecture and Principles
- OOP and Design Patterns
- Features, Scaling and Performance
- Code Audit
- Feature Audit
- Git Commit and PR Messages
Skills.sh
Browse the NestJS Skills collection on Skills.sh. Skills.sh uses the Skills CLI with the GitHub repository as its source:
npx skills add amirtaherkhani/nestjs-skillsFor one skill, choose the supported agent IDs explicitly. For example, to install Professional Software Engineering for Claude Code and Codex:
npx skills add amirtaherkhani/nestjs-skills \
--skill nestjs-professional-software-engineering \
--agent claude-code \
--agent codexFor other compatible harnesses, use a target ID supported by the Skills CLI, or follow that harness's documented manual skill-folder instructions. The project-level folders used by the CLI include .claude/skills/ for Claude Code and .agents/skills/ for Codex; do not assume the same folder applies to every harness.
Skillstore
Skillstore listings provide Ask an Agent, CLI, and Manual install choices. Follow the options shown on the specific listing you select: use its generated agent request, its displayed CLI command, or download the skill and place it in the selected agent's documented skills folder. These Skillstore choices are distinct from the GitHub-source command above.
- nestjs-professional-software-engineering
- nestjs-architecture-principles
- nestjs-oop-design-patterns
- nestjs-features-performance
- nestjs-code-audit
- nestjs-feature-audit
- nestjs-git-commit-pr-message
See public listings and posts for publication links and their current verification status.
Current release
v2.5.0 adds 15 collection checks and 17 operations, DI and performance checks, with a research record mapping 13 selected upstream rules to the seven existing skills. The collection also includes the 19 executable pattern examples, focused four-axis boundary checks, and documentation entry pages in five languages. See examples and evaluation for scope and verification limits.
Version 2 migration
professional-software-engineering was renamed to nestjs-professional-software-engineering, and git-commit-pr-message was renamed to nestjs-git-commit-pr-message. Reinstall the renamed skills and update explicit commands.
Invoke a skill
The descriptions are written for automatic activation, so a concrete request is usually enough:
Implement this feature using the clearest syntax supported by the current project, then verify it.You can also name a skill explicitly:
# Claude Code
/nestjs-professional-software-engineering
# Codex
$nestjs-professional-software-engineeringThe other skill names are:
nestjs-git-commit-pr-messagenestjs-architecture-principlesnestjs-code-auditnestjs-feature-auditnestjs-oop-design-patternsnestjs-features-performance
Add client engineering rules
The portable skill works in both clients. Optional repository-level templates make it the default engineering workflow. From this repository checkout:
# Codex
cp integrations/codex/AGENTS.md ./AGENTS.md
# Claude Code
cp integrations/claude/CLAUDE.md ./CLAUDE.mdMerge rather than overwrite when the project already has AGENTS.md or CLAUDE.md; the nearest project instructions must remain authoritative.
For a new feature, ask:
Implement this feature using the clearest syntax supported by the current project.
Compare any syntactic sugar with the explicit form, preserve compatibility,
and run the relevant tests, type-check, lint, and build.When the change is verified, publish it explicitly:
$nestjs-git-commit-pr-message
Commit and push this NestJS change, open a draft PR, and verify the
matching CI and GitHub Pages workflow without merging.The public documentation workflow deploys after every push to main. A feature-branch push runs validation but does not replace the production GitHub Pages site; the agent reports that merge or a main-branch push is still required.
Audit a current project
From a NestJS project root, invoke the portable audit skill:
$nestjs-code-audit
$nestjs-code-audit full src/payments
$nestjs-code-audit static
$nestjs-code-audit security src/authIt runs a read-only workflow and returns one report covering safe syntax/TypeScript/lint checks plus verified architecture, object-design, security, testing, runtime, and delivery findings. It does not install dependencies or fix code.
Codex does not support arbitrary bare custom commands such as /Nestjs audit. Custom prompts are deprecated in favor of skills, but Codex CLI and the IDE extension still support them as explicit local aliases. Copy integrations/codex/prompts/nestjs-audit.md into ~/.codex/prompts/, then use:
/prompts:nestjs-audit
/prompts:nestjs-audit full src/paymentsAudit one feature against its roadmap
Use Feature Audit when the expected state is a documented roadmap rather than general code quality:
$nestjs-feature-audit "payments"
$nestjs-feature-audit "payments" --branch "release/2026-q3"The skill defaults to main, preserves dirty work, allows only fast-forward branch updates, and stops before comparison when docs/ has no clear feature roadmap. A roadmap supplied by the user can satisfy that gate.
For Codex compatibility, copy integrations/codex/prompts/audit_feature.md into ~/.codex/prompts/, then use:
/prompts:audit_feature payments
/prompts:audit_feature payments on branch release/2026-q3Bare /audit_feature is client-specific and works only when the host routes it to nestjs-feature-audit.
Continue with the Feature Audit workflow guide for the roadmap gate, branch-safety rules, evidence categories, and exact report contract.
Give the agent evidence
The skills deliberately begin with repository inspection. Better prompts identify the goal and constraints while leaving the agent access to the relevant code, configuration, tests, and runtime evidence.
This endpoint misses its p95 latency target under the attached load test.
Trace the request, identify the limiting resource, and propose the smallest measured fix.
Preserve the public API and PostgreSQL transaction behavior.Avoid prescribing a fashionable solution before diagnosis. “Add Redis,” “use microservices,” or “apply Clean Architecture” may hide the actual constraint.
Validate a local checkout
npm install
npm test
npx skills add . --listnpm test validates skill metadata, links, and evaluation files, then builds every documentation route from the canonical skill sources.
Next steps
- Use Choose a skill to route work and understand intentional overlap.
- Read Request lifecycle before selecting middleware, guards, pipes, interceptors, or filters.
- Open the complete Architecture & Principles skill reference.