Skip to content
TrustedSkillsbeta
Back to all skills

Backend Dev Guidelines

Checked
microck·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.

  1. 1

    Run this in your project

    terminal
    $ npx skills add microck/ordinary-claude-skills --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

microck

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

    Only contacts known or declared hosts: github.com.

    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.

    Hosts contacted

    github.comsource host

  • 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 microck/ordinary-claude-skills at 1056d293d4.

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

Commit
1056d293d4
Manifest
skills_all/backend-dev-guidelines/SKILL.md
Scanned
4 files, 1,104 lines
Copies in repo
2 — 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 guidance and best practices for backend development, specifically tailored to ensure code quality, maintainability, and adherence to common architectural patterns. It helps developers write robust and scalable backend systems by offering advice on topics like API design, database interactions, and error handling. The skill aims to improve the overall reliability and performance of backend applications.

When to use it

  • Designing a new API: Get recommendations for endpoint structure, request/response formats, and authentication methods.
  • Refactoring existing code: Receive suggestions on how to improve code readability, modularity, and testability.
  • Troubleshooting performance issues: Identify potential bottlenecks in backend logic and receive advice on optimization strategies.
  • Ensuring code consistency across a team: Establish common coding standards and patterns for all developers working on the project.

Key capabilities

  • API design recommendations
  • Database interaction best practices
  • Error handling guidelines
  • Code quality suggestions
  • Architectural pattern advice

Example prompts

  • "Suggest an API endpoint for retrieving user profiles."
  • "How can I improve the performance of this database query?"
  • "What are some common error-handling strategies in backend development?"
  • “Review my code and suggest ways to make it more readable.”

Tips & gotchas

This skill assumes a basic understanding of backend development concepts. For optimal results, provide specific code snippets or scenarios for review and guidance.