skills.rest
YuriiYInno
YuriiYInnoCOMMUNITY
Explore all skills by this author →
GitHub

architect

Guides system architecture decisions for NestJS projects using layered architecture patterns.

Updated Oct 2, 2025
Search Tags:#planning#architecture#documentation#layered architecture#nestjs#design decisions#module structure
One-click install
npx skills add https://github.com/YuriiYInno/Innogram --skill architect-yuriiyinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/YuriiYInno/Innogram/tree/main/.codex/skills/architect
Command: npx skills add https://github.com/YuriiYInno/Innogram --skill architect-yuriiyinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Making consistent architecture decisions in NestJS projects is hard: where to place new code, which pattern to apply, how to model entity relationships, and how to document decisions over time. This Skill provides decision trees, dependency rules, and a living specification workflow to keep architecture coherent. ## Core Features & Use Cases - Decision Trees: Determine where new code belongs (modules, shared, integrations) and which pattern fits (Controller, Service, Repository). - Layered Architecture Rules: Enforce allowed dependencies (Controller → Service → Repository) and standard module structure with DTOs and entities. - Living Specification: Append task-scoped architecture sections to specs/architect-architecture.md and update specs/MANIFEST.md after each decision. - Use Case: When designing a new authentication feature, use this Skill to decide module placement, JWT pattern, entity relationships, and security/scalability considerations, then document them under a task number like [TASK-001]. ## Quick Start Ask the architect skill to design the architecture for a new user authentication feature in my NestJS project and document it in the specs folder.

Frequently Asked Questions about architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide where to place new code in a NestJS project?▼

Use the decision tree: business domain logic goes in modules/<module>/, cross-cutting infrastructure goes in shared/, and external service integrations go in shared/integrations/ or a module-specific location.

Which pattern should I use for business logic in NestJS?▼

Business logic belongs in a Service. HTTP request handling goes in Controllers, data access in Repositories, and helper functions become static utilities or shared services, following the layered architecture.

What dependency directions are allowed in layered architecture?▼

Controllers may call Services, Services may call Repositories, and any layer may use shared utilities. Repositories must not call Services, and Services must not call Controllers.

How does the skill document architecture decisions?▼

It appends task-numbered sections like [TASK-001] with dates to specs/architect-architecture.md, covering module placement, patterns, entities, security, and scalability, then updates the Last Updated date in specs/MANIFEST.md.

When should I use transactions in NestJS services?▼

Single writes need no explicit transaction since repository calls are implicit. Multiple related writes require a service method with @Transaction, while read operations need no transaction.

Related Skills

Explore More Software Engineering Skills→
arndvsarndvs

write-a-prd

Generates a structured Product Requirements Document from a rough feature idea through guided interviews.

Community
Intermediate
jakubciszakjakubciszak
1

api-design

Design REST APIs for Symfony backends with OpenAPI specifications and DTO-based contracts.

Community
Intermediate
peopleforresterpeopleforrester
3

security-auditor

Identify and remediate security vulnerabilities in code.

Community
Advanced
tak-brotak-bro

react-01-plan

Plan React project architecture with TanStack Query, Zustand, and Nx monorepo.

Community
Intermediate