스킬 nestjs-oop-design-patterns

📦

nestjs-oop-design-patterns

Name: nestjs-oop-design-patterns
Author: amirtaherkhani

v1.0.2 콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어

Refactor NestJS Code with Pragmatic Design Patterns

Unclear responsibilities and unnecessary abstractions make NestJS code difficult to change and test. This skill guides evidence-based object design, pattern selection, and behavior-preserving refactoring.

지원: Claude Codex Code(CC)

🥉 79 브론즈

Maintain this Skill? Claim it 🥉 79 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "nestjs-oop-design-patterns" from https://skillstore.io/skills/amirtaherkhani-nestjs-oop-design-patterns.md and its manifest at https://skillstore.io/api/skills/amirtaherkhani-nestjs-oop-design-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/amirtaherkhani-nestjs-oop-design-patterns.md 서명된 manifest GET /api/skills/amirtaherkhani-nestjs-oop-design-patterns/manifest 서명된 lockfile GET /api/skills/amirtaherkhani-nestjs-oop-design-patterns/lockfile

테스트해 보기

"nestjs-oop-design-patterns" 사용 중입니다. A checkout service validates orders, calls a payment SDK, and maps database rows.

예상 결과:

Role: The checkout use case coordinates order placement.
Evidence: Vendor payment details and persistence mapping change for different reasons.
Recommendation: Keep coordination in the use case and move vendor translation into an application-owned payment adapter.
Trade-off: The adapter adds a boundary and requires contract tests.
Verification: Preserve payment errors, order invariants, and provider wiring with focused tests.

"nestjs-oop-design-patterns" 사용 중입니다. Should a service with one stable pricing rule use Strategy?

예상 결과:

Evidence: Only one pricing algorithm exists, with no accepted requirement for another.
Recommendation: Keep the direct implementation rather than adding interchangeable policy classes.
Verification: Test pricing behavior and invariants through the public operation.

"nestjs-oop-design-patterns" 사용 중입니다. Does an in-process event guarantee publication after a database commit?

예상 결과:

Finding: In-process notification does not provide durable delivery across crashes or replicas.
Recommendation: Consider a transactional outbox when external consumers must reliably observe committed changes.
Trade-off: A relay requires retries, retention, ordering decisions, and idempotent consumers.

보안 감사

안전

v1 • 2026. 10. 4. 버전별 보고서 열기

All 25 static findings are false positives involving ordinary design guidance, Markdown identifiers, or headings. Backticks mark inline code, and the reconnaissance matches contain no system enumeration instructions. No evidence found of prompt injection, credential theft, unauthorized execution, or data exfiltration in the reviewed passages and surrounding files.

스캔된 파일

904

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

⚙️ 외부 명령어 (10)

SKILL.md:26 SKILL.md:27 SKILL.md:28 SKILL.md:29 SKILL.md:30 SKILL.md:31 SKILL.md:78 SKILL.md:122 SKILL.md:131 SKILL.md:140

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/amirtaherkhani-nestjs-oop-design-patterns/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/amirtaherkhani-nestjs-oop-design-patterns/security.svg)](https://skillstore.io/skills/amirtaherkhani-nestjs-oop-design-patterns?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/amirtaherkhani-nestjs-oop-design-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/amirtaherkhani-nestjs-oop-design-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/amirtaherkhani-nestjs-oop-design-patterns.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-oop-design-patterns security audit report (audit version 1) [Author version 1.0.2]. Skillstore. https://skillstore.io/skills/amirtaherkhani-nestjs-oop-design-patterns/audits/1

BibTeX 인용

@techreport{amirtaherkhani-amirtaherkhani-nestjs-oop-design-patterns-2026,
  author = {amirtaherkhani},
  title = {nestjs-oop-design-patterns security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/amirtaherkhani-nestjs-oop-design-patterns/audits/1},
  note = {Author version 1.0.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-oop-design-patterns security audit report (audit version 1)"
version: "1.0.2"
type: report
authors:
  - name: "amirtaherkhani"
date-released: "2026-10-04"
url: "https://skillstore.io/skills/amirtaherkhani-nestjs-oop-design-patterns/audits/1"
identifiers:
  - type: other
    value: "skillstore:amirtaherkhani-nestjs-oop-design-patterns:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

100

유지보수성

콘텐츠

커뮤니티

100

사양 준수

만들 수 있는 것

Review an overloaded service

Identify unrelated responsibilities and propose a small refactor that preserves behavior and public contracts.

Choose a provider integration pattern

Compare direct integration, Adapter, and Strategy using vendor coupling, variation, and substitution requirements.

Plan contract-focused verification

Define tests for invariants, adapter substitution, Nest provider wiring, and transport behavior before refactoring.

이 프롬프트를 사용해 보세요

Understand one object

Review [class] and its callers. Explain its role, responsibilities, and one concrete design concern without editing files.

Select the smallest design

Compare a direct solution, Strategy, and Factory for [observed variation]. Recommend one using repository evidence and explain its testing cost.

Refactor a service safely

Refactor [service] to separate [misplaced responsibility]. Preserve public behavior and user changes, add focused tests, and verify Nest provider wiring.

Review consistency and substitution

Review [workflow] for adapter substitution, transaction boundaries, and event delivery guarantees. Compare direct coordination with outbox or saga designs and specify contract tests.

모범 사례

Inspect callers, tests, module wiring, and repository conventions before selecting a pattern.
State the concrete problem, simpler alternative, and added cost before introducing an abstraction.
Preserve behavior with focused tests and verify contracts and provider wiring after refactoring.

피하기

Adding interfaces, factories, repositories, or class hierarchies without real variation or a useful boundary.
Judging design only by line counts or applying fixed size limits as mandatory rules.
Assuming CQRS dispatch, in-process events, or pattern names provide durability or scalability.