菜单
Decouples modules using ports, adapters, and a DI container (tsyringe / inversify / NestJS). Use when wiring services, removing direct imports of concrete classes, or breaking circular dependencies.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | decoupling-with-di |
| description | Decouples modules using ports, adapters, and a DI container (tsyringe / inversify / NestJS). Use when wiring services, removing direct imports of concrete classes, or breaking circular dependencies. |
| license | MIT |
infrastructure → application → domain// src/application/ports/user.repository.ts
export interface UserRepository {
findById(id: string): Promise<User | null>;
save(user: User): Promise<User>;
}
// src/infrastructure/repositories/typeorm-user.repository.ts
@injectable()
export class TypeOrmUserRepository implements UserRepository {
constructor(private ormRepo: Repository<UserOrmEntity>) {}
async findById(id: string): Promise<User | null> { /* ... */ }
async save(user: User): Promise<User> { /* ... */ }
}
// src/application/use-cases/create-user.use-case.ts
@injectable()
export class CreateUserUseCase {
constructor(@inject('UserRepository') private readonly repo: UserRepository) {}
}
// Decoupled: depends on interface
class OrderService {
constructor(private readonly repo: OrderRepository) {}
}
// ❌ Direct import of concrete class
import { TypeOrmOrderRepository } from '../infrastructure/typeorm-order.repository';
class OrderService {
private repo = new TypeOrmOrderRepository(); // Hard-wired
}
See reference/di-patterns.md for full patterns.
Defines the rule base every skill in this pack obeys: file layout, frontmatter, vocabulary, OOP/typing/decoupling axioms, and anti-patterns. Load FIRST before authoring or applying any other skill in this pack.
Designs NestJS feature modules with clean dependency boundaries, provider scopes, and dynamic modules. Use when adding a new feature module, splitting a monolithic AppModule, or fixing tangled imports between modules.
Builds thin NestJS controllers that parse input, invoke a single use case, and map the Result to ApiResponse<T>. Use when adding HTTP endpoints, refactoring fat controllers, or applying API versioning.
Prepares a NestJS service for production: graceful shutdown, health/readiness, structured logs, config, Dockerfile, CI gates, and rollout safety. Use when promoting a service to staging/production or auditing readiness.
Designs NestJS application services as use-case classes that orchestrate domain logic and ports without leaking the framework. Use when creating new use cases, refactoring services that mix HTTP/DB/domain, or moving from anemic services to OOP.
Maps internal AppError hierarchy to HTTP responses through a single global exception filter and a Result-to-HttpException helper. Use when adding new error types, fixing inconsistent error responses, or removing scattered try/catch in controllers.