Skip to content
TrustedSkillsbeta
Back to all skills

Backend Dev Guidelines

Checked
davila7·vlatest·backend·MIT

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.

  1. 1

    Run this in your project

    terminal
    $ npx skills add davila7/claude-code-templates --skill backend-dev-guidelines -a claude-code

  2. 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

davila7

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

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    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 davila7/claude-code-templates at 79182c51fb.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79182c51fb
Manifest
cli-tool/components/skills/development/backend-dev-guidelines/SKILL.md
Scanned
12 files, 4,998 lines
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 a set of guidelines and best practices for backend development, focusing on code structure, API design, database interactions, and security considerations. It helps developers build scalable, maintainable, and secure backend systems.

When to use it

  • When designing RESTful or GraphQL APIs for web applications
  • When setting up new backend projects and need a structured approach
  • When improving the architecture of an existing backend system
  • When ensuring compliance with industry-standard security practices

Key capabilities

  • Code structure recommendations
  • API design patterns
  • Database schema best practices
  • Security guidelines (e.g., authentication, input validation)
  • Error handling and logging strategies

Example prompts

  • "How should I structure my backend project for scalability?"
  • "What are the best practices for designing a RESTful API?"
  • "Can you provide guidelines on securing a Node.js backend application?"

Tips & gotchas

  • This skill assumes a basic understanding of backend development concepts. Review the documentation for specific frameworks or languages if needed.
  • While it provides general guidance, implementation details may vary depending on your tech stack and project requirements.