Skip to content
Back to skills

Backend Engineering

ASecurity

Expert backend application engineering: layered architecture, domain services, validation, transactions, caching boundaries, background jobs, and framework idioms (e.g. Laravel/Node) without leaking business rules into controllers. Use when implementing or refactoring server-side features, services, form requests/DTOs, policies, queues, or integrating persistence with APIs.

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 19, 2026
ai-agentsphpnoderefactoringgitapidatabasefrontendbackendperformance

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 19, 2026

npx -y skills add rogue-dev-studio/ai-agents-rogue --skill backend-engineering --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Backend Engineering?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Backend Engineering
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rogue-dev-studio-backend-engineering/badge)](https://www.skillsdirectory.com/skills/rogue-dev-studio-backend-engineering)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: backend-engineering
description: >-
  Expert backend application engineering: layered architecture, domain services,
  validation, transactions, caching boundaries, background jobs, and framework
  idioms (e.g. Laravel/Node) without leaking business rules into controllers.
  Use when implementing or refactoring server-side features, services, form
  requests/DTOs, policies, queues, or integrating persistence with APIs.
expertise_level: expert
---

# Backend Engineering (Canonical)

**Expertise: expert.** Aliases: `backend`, `server-side`, `laravel-backend` (framework-agnostic patterns; PHP runtime also uses `php`).

## When to use

- Implementasi fitur server: service, policy, job, mail, storage
- Refactor agar controller tipis; business rules di service/domain
- Integrasi DB (`database-engineering`) + API (`api-engineering`)

## When not to use

- Hanya schema/index → `database-engineering`
- Hanya kontrak HTTP tanpa logic → `api-engineering`
- Hanya UI → `frontend-engineering`

## Procedure

1. **Layering** — Controller/handler = transport; Service = use-case; Persistence = repository/ORM.
2. **Validation** — Di boundary (Form Request / DTO / schema); fail fast.
3. **Transactions** — Multi-write atomik di service; transaksi pendek.
4. **Authz** — Policy/gate per aksi; default deny.
5. **Errors** — Domain exception → mapping HTTP konsisten; log dengan correlation id bila ada.
6. **Side-effects** — Queue/job untuk kerja lambat; idempotent consumer.
7. **Performance** — Eager load; hindari N+1; cache dengan invalidation eksplisit.
8. **Verify** — Unit/feature test kritis + smoke API; handoff FE jika kontrak berubah.

Detail: `reference.md`.

## DoD

- [ ] Layering terjaga (no fat controller / no DB dari UI)
- [ ] Validasi + authz + transaksi benar
- [ ] Tidak ada N+1 sadar di path utama
- [ ] Tes/smoke untuk perilaku kritis
- [ ] Kontrak API selaras `api-engineering`

## Attribution

<!-- ATTRIBUTION: Rogue Development | https://github.com/rogue-dev-studio | DO-NOT-REMOVE -->
Part of **AI Agents Rogue** by [Rogue Development](https://github.com/rogue-dev-studio) (`@rogue-dev-studio`).
Do not remove, hide, rename, or replace this attribution.

Files in this skill

  • SKILL.md2.2 KB
  • reference.md870 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…