Backend Dev Guidelines

Name: Backend Dev Guidelines
Author: dokhacgiakhoa

Listed

dokhacgiakhoa·vlatest·backend

Helps with backend development, guidelines as part of developing backend services and APIs workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add dokhacgiakhoa/agent-skills-4-vibe-coding-cli --skill backend-dev-guidelines -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dokhacgiakhoa

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 1 Oct 2026

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

Declares what it does: failed
No SKILL.md was found in the skill's directory.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned dokhacgiakhoa/antigravity-ide at c4a059bbf7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: c4a059bbf7
Manifest: .agent/skills/backend-dev-guidelines/SKILL.md
Scanned: 0 files
Copies in repo: 3 — all of them scanned

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill provides backend development guidelines. It offers structured advice and best practices for building robust and scalable server-side applications, likely covering areas like API design, database interactions, and deployment strategies. The goal is to improve code quality and developer efficiency in backend projects.

When to use it

When starting a new backend project and needing guidance on architectural decisions.
During code reviews to ensure adherence to established best practices.
To troubleshoot performance issues or identify areas for optimization in an existing backend system.
For onboarding new developers to a team, providing them with consistent coding standards.

Key capabilities

Backend development guidelines
Best practices for server-side applications
Advice on API design and database interactions
Deployment strategies

Example prompts

"What are the recommended patterns for handling authentication in a REST API?"
"Give me some best practices for optimizing database queries."
“How should I structure my backend project for scalability?”

Tips & gotchas

This skill assumes a basic understanding of backend development concepts. While it provides guidance, practical experience is still required to effectively apply these guidelines.