Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
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 9/19/2026
ai-agentsphpnoderefactoringgitapidatabasefrontendbackendperformance

Works with

api

Security Analysis

A100/100

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

Scanned 9/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 automatically 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
Files
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.

Attribution

rogue-dev-studiorogue-dev-studio
View sourceSee grades on GitHubMore from rogue-dev-studio →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →