技能 nestjs-architecture-principles
📦
nestjs-architecture-principles
v1.1.2 内容修订 r1 安全 🔑 环境变量⚙️ 外部命令
Design and Review NestJS Architecture
Unclear module boundaries make NestJS changes harder to test and coordinate. This skill guides evidence-based architecture decisions, explicit ownership, and incremental boundary repairs.
支持: Claude Codex Code(CC)
使用我的智能体安装
将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。
智能体请求
Review the Skillstore skill "nestjs-architecture-principles" from https://skillstore.io/skills/amirtaherkhani-nestjs-architecture-principles.md and its manifest at https://skillstore.io/api/skills/amirtaherkhani-nestjs-architecture-principles/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“nestjs-architecture-principles”。 A small team needs one NestJS deployment for an order-management API.
预期结果:
- Decision: use a modular monolith with cohesive Orders, Catalog, and Billing capabilities.
- Boundaries: each capability owns its writes and exposes only required application operations.
- Trade-off: keep simple CRUD compact and layer only features with meaningful domain or integration complexity.
- Validation: test public operations, module wiring, and forbidden cross-feature persistence imports.
正在使用“nestjs-architecture-principles”。 Orders and Payments have a circular dependency and both use forwardRef.
预期结果:
- Baseline: trace the shared workflow and establish which capability owns its invariant.
- Decision: consider an owning coordinator or narrow port before asynchronous events.
- Migration: characterize behavior, move callers incrementally, then remove temporary circular wiring.
- Validation: compile affected modules and verify payment failures preserve the required order invariant.
正在使用“nestjs-architecture-principles”。 A CPU-heavy report generator needs more capacity than the rest of the application.
预期结果:
- Decision: evaluate a separately scaled worker before creating a business microservice.
- Boundary: define job identity, idempotency, retry limits, payload bounds, and data access ownership.
- Extraction gate: require evidence of independent operation and account for contract and failure costs.
- Validation: test duplicate jobs, partial failures, backlog limits, and shutdown behavior.
安全审计
安全v1 • 2026/10/4 打开版本化报告
All 19 static findings are false positives involving architecture guidance, Markdown formatting, or illustrative configuration access. The payment example passes configuration to an adapter without logging or exporting credentials. No evidence found of malicious intent, prompt injection, reconnaissance, or shell execution in the reviewed files.
10
已扫描文件
1,031
分析行数
0
复核项
0
已忽略误报
风险因素
最新一次完成的静态与语义审计未检测到已确认的安全发现。这并不能证明该 Skill 没有副作用。
审计者: codex
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/amirtaherkhani-nestjs-architecture-principles/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/amirtaherkhani-nestjs-architecture-principles?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/amirtaherkhani-nestjs-architecture-principles?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/amirtaherkhani-nestjs-architecture-principles/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/amirtaherkhani-nestjs-architecture-principles.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学术引用 (APA · BibTeX · CFF)
APA 引用
amirtaherkhani. (2026). nestjs-architecture-principles security audit report (audit version 1) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/amirtaherkhani-nestjs-architecture-principles/audits/1BibTeX 引用
@techreport{amirtaherkhani-amirtaherkhani-nestjs-architecture-principles-2026,
author = {amirtaherkhani},
title = {nestjs-architecture-principles security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/amirtaherkhani-nestjs-architecture-principles/audits/1},
note = {Author version 1.1.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nestjs-architecture-principles security audit report (audit version 1)"
version: "1.1.2"
type: report
authors:
- name: "amirtaherkhani"
date-released: "2026-10-04"
url: "https://skillstore.io/skills/amirtaherkhani-nestjs-architecture-principles/audits/1"
identifiers:
- type: other
value: "skillstore:amirtaherkhani-nestjs-architecture-principles:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据 证据置信度: 中 45
架构
100
可维护性
87
内容
65
社区
100
规范符合性
你能构建什么
Plan a new backend
Choose cohesive feature modules, public operations, and data owners before adding layers or separate services.
Review an existing system
Identify cross-feature write leaks, broad exports, and dependency cycles, then recommend focused repairs with regression checks.
Evaluate service extraction
Compare worker scaling with business-service extraction and define ownership, contracts, consistency, and operational requirements.
试试这些提示
Plan feature modules
Design a NestJS order-management API for one team and one deployment. Recommend module boundaries, public APIs, data ownership, and validation.
Review module boundaries
Review this NestJS repository without editing files. Map imports and exports, identify ownership violations, and report evidence, impact, minimal remedies, and tests.
Plan a cycle repair
OrdersModule and PaymentsModule depend on each other. Trace the workflow and propose an incremental cycle repair that preserves contracts and required consistency.
Evaluate distributed boundaries
Evaluate extracting reporting from our NestJS monolith. Compare worker deployment and microservices using ownership, scaling, data, failure, contracts, migration, and validation.
最佳实践
- Inspect installed versions, module wiring, callers, tests, and concrete change pressures before choosing an architecture.
- Assign clear capability and write ownership, then add only boundaries justified by current requirements.
- Make changes incrementally, preserve public contracts, and verify boundaries with existing lint, module, integration, or contract tests.
避免
- Introduce CQRS, microservices, or strict layering only to match a preferred diagram.
- Export every provider or let features directly write another capability's tables.
- Treat forwardRef as the default cycle repair or create interfaces for every stable local helper.
常见问题
What does this skill help with?
It guides NestJS architecture selection, module boundaries, dependency injection, data ownership, and evidence-based reviews.
Does every NestJS application need Clean Architecture?
No. It starts with cohesive feature modules and recommends selective layers only when domain complexity or infrastructure changes justify them.
Does it require other NestJS skills?
No. Related skills are optional coordination partners with distinct ownership boundaries.
Can it fix circular dependencies?
It guides ownership analysis and incremental repairs using coordinators, narrow ports, or events when consistency requirements permit.
Does it automatically run migrations or verify performance?
No. It provides guidance and validation plans; real database behavior and performance require appropriate tests and measurements.
When does it recommend microservices?
Only when concrete deployment, ownership, scaling, data, or failure boundaries justify independent operation and its added costs.
开发者详情
许可证
MIT
作者版本
v1.1.2
Skillstore 修订
r1
引用
c97a1862d1bc82763903ee068cd15acab35d638c
维护新鲜度
2026/10/5
使用量
0 次下载 · 0 次浏览