Full Cycle
Official@devfullcycle · Brazil
Offers structured technical implementation planning, architectural enforcement for NestJS, and standardized testing methodologies for enterprise-grade backend development.
Agent Skills by Full Cycle
Showing 7 vetted skills indexed across 1 GitHub repositories.
devfullcycleresearch
Generate a structured decisions document comparing technical options for a project phase.
devfullcycleimplement-phase
Execute phase plans SI by SI with tests and user confirmation.
devfullcycleplan-phase
Generate technical implementation plans with steps, dependencies, tests, and acceptance criteria.
devfullcyclegenerate-test-guide
Analyze a project's tech stack to generate a tailored testing guide.
devfullcycletypeorm
Enforce TypeORM data access patterns with entities, repositories, and migrations.
devfullcyclenestjs-best-practices
Implement NestJS architectural best practices for modules, DI, guards, and testing.
devfullcycletesting-guide-nestjs-project
Guide NestJS testing across unit, integration, and end-to-end levels.
Frequently Asked Questions About Full Cycle
FAQPage SchemaWhat specific technical tasks does Full Cycle enable?▼
Full Cycle enables the generation of structured technical decision documents, the creation of detailed implementation roadmaps, and the enforcement of architectural standards within NestJS environments. It further facilitates the production of tailored testing guides to ensure code quality across unit, integration, and end-to-end layers.
Which engineering personas benefit from these capabilities?▼
These capabilities are designed for backend engineers, software architects, and technical leads working within the NestJS ecosystem. It is particularly useful for teams aiming to standardize repository patterns, enforce dependency injection best practices, and maintain rigorous testing coverage across complex project phases.
What are the prerequisites for implementing these architectural patterns?▼
Implementation requires an existing NestJS project structure and a foundational understanding of TypeORM data access patterns. Users should have their project environment configured to support modular architecture, as the provided guidance relies on standard NestJS dependency injection and module-based organization to function effectively.