skills.rest
GolferGeek
GolferGeekCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Back-End Structure

Automate kebab-case NestJS backend architecture with modules, services, and controllers.

Updated May 13, 2025
Search Tags:#architecture#API#TypeScript#backend#microservices#NestJS#A2A protocol
One-click install
npx skills add https://github.com/GolferGeek/orchestrator-ai --skill back-end-structure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Back-End Structure
Source: https://github.com/GolferGeek/orchestrator-ai/tree/main/.claude/skills/back-end-structure-skill
Command: npx skills add https://github.com/GolferGeek/orchestrator-ai --skill back-end-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the pitfalls of inconsistent backend development, which can result in unmaintainable APIs, non-compliant services, and difficult integration within the Orchestrator AI ecosystem.

Core Features & Use Cases

  • NestJS Patterns: Enforces standard NestJS module, service, and controller patterns for clear code organization.
  • Kebab-Case Naming: Mandates consistent kebab-case file naming conventions across the backend codebase.
  • A2A Protocol Compliance: Guides the implementation of Agent-to-Agent (A2A) protocol endpoints for seamless inter-agent communication.
  • Use Case: When developing a new API endpoint, use this skill to ensure your controller and service files are correctly named, structured, and adhere to A2A protocol for agent interaction.

Quick Start

Help me create a new NestJS module for user authentication, ensuring it follows the backend structure guidelines for controllers, services, and A2A compliance.

Frequently Asked Questions about Back-End Structure

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

FAQPage Schema
How do I structure a NestJS backend with consistent naming conventions?▼

NestJS backend structure enforces kebab-case file naming and separates modules, services, and controllers into distinct files. This standardization prevents inconsistent organization and makes codebases maintainable across teams and integrations.

What is A2A protocol compliance and why does it matter for NestJS APIs?▼

A2A (Agent-to-Agent) protocol compliance enables seamless inter-agent communication within the Orchestrator AI ecosystem. Implementing it ensures your NestJS endpoints can reliably exchange messages with other agents following a standardized contract.

How do I create a new NestJS module that follows backend architecture best practices?▼

Create a new NestJS module by applying standard module, service, and controller patterns with kebab-case naming. This approach ensures consistent file organization, proper separation of concerns, and alignment with A2A protocol requirements for agent interaction.

Can I enforce consistent error handling across my NestJS codebase?▼

Yes, standardized error handling is enforced across the backend architecture. Consistent error patterns prevent integration failures and make debugging predictable when APIs interact with other services in the ecosystem.

What transport types does this architecture support for NestJS APIs?▼

The backend structure guides implementation of A2A protocol endpoints using specified transport types. This ensures your NestJS services communicate reliably with agents using the correct protocol and message format.

Related Skills

Explore More Software Engineering Skills→
himanshu231204himanshu231204
2

nestjs-patterns

Scaffold NestJS modules with validation, guards, and environment configuration.

Community
Advanced
steedossteedos
1.6k

steedos-server-moleculer

Embed a Moleculer broker in NestJS to orchestrate Steedos microservice communication.

Official
Advanced
ai-enhanced-engineerai-enhanced-engineer
3

azure-service-bus-messaging

Implement Azure Service Bus messaging with async producers, consumers, and dead-letter routing.

Official
Advanced
chestnut0698chestnut0698

backend-architect

Provide expert backend architecture advice for scalable, resilient, and maintainable systems.

Community
Advanced