backend-app

Bootstrap Drumr backend App.ts entry points with lifecycle hooks.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-app-slingr-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-app
Source: https://github.com/slingr-stack/qa-test-drumr/tree/main/project-management-app/.agents/skills/backend-app
Command: npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-app-slingr-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you create the backend application entry point and keep startup behavior organized, so Drumr backends are configured consistently instead of being wired together ad hoc.

Core Features & Use Cases

  • Bootstraps a single app class with BaseApp and the App decorator.
  • Centralizes runtime settings in src/config/config.json and reads them through ConfigService.
  • Supports lifecycle hooks for pre-start overrides, startup logging, shutdown cleanup, and error handling.
  • Use it when you need to register a mock service before startup, read environment-driven GraphQL or auth settings, or resolve a service after the app is running.

Quick Start

Ask the assistant to create or update backend/src/App.ts for a Drumr backend using a single App class, ConfigService, and beforeStart overrides only.

Frequently Asked Questions about backend-app

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

FAQPage Schema
How do I bootstrap a Drumr backend application entry point with lifecycle hooks?

Bootstrap a Drumr backend by creating a single @App() class extending BaseApp in backend/src/App.ts, then implement beforeStart, afterStart, beforeStop, and onError hooks to manage startup behavior and shutdown cleanup consistently.

What is the best way to configure runtime settings for a Drumr backend application?

Centralize runtime settings in src/config/config.json and read them through ConfigService access within your BaseApp class to manage environment-driven GraphQL or auth configurations consistently.

Can I resolve a service after the Drumr backend app has already started running?

Use App.resolve for late binding to resolve services dynamically after the Drumr backend application is running, allowing flexible dependency resolution without requiring startup-time registration.

How do I register a mock service override before a Drumr backend starts?

Register pre-start service overrides inside the beforeStart lifecycle hook of your @App() class to inject mock services or modify configuration before the Drumr backend application fully initializes.

Do I need a single app class to configure a Drumr backend startup?

Yes, Drumr backend configuration requires a single @App() class extending BaseApp to handle dependency injection, lifecycle hooks, and ConfigService access for consistent startup behavior.

Why does my Drumr backend need centralized configuration instead of ad hoc wiring?

Centralized configuration through ConfigService and lifecycle hooks prevents ad hoc wiring, ensuring Drumr backends start consistently with manageable runtime settings, error handling, and pre-start service overrides.