Backend Dev Guidelines
ListedHelps with backend development, guidelines as part of developing backend services and APIs workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add dojocodinglabs/claude-code-waypoint --skill backend-dev-guidelines -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
dojocodinglabs
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.
Automated safety checks
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.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: project.supabase.co.
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
project.supabase.coundeclaredWhat it found
- .claude/skills/backend-dev-guidelines/resources/architecture-overview.md:201contacts project.supabase.co
fetch('https://PROJECT.supabase.co/functions/v1/create-post', { - .claude/skills/backend-dev-guidelines/resources/architecture-overview.md:353contacts project.supabase.co
fetch('https://PROJECT.supabase.co/functions/v1/endpoint', {
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 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 dojocodinglabs/claude-code-waypoint at 2a94dda68a.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 2a94dda68a
- Scanned
- 14 files, 6,052 lines
About this skill
What it does
This skill provides guidelines for backend development, ensuring consistency and best practices across projects. It helps generate code that adheres to established standards, promotes maintainability, and reduces technical debt. The guidelines cover aspects of architecture, coding style, and testing procedures.
When to use it
- Generating new backend services or APIs.
- Refactoring existing backend codebases for improved quality.
- Creating automated tests for backend functionality.
- Ensuring consistency across multiple developers working on a project.
- Onboarding new team members and establishing coding standards.
Key capabilities
- Backend development guidelines
- Code generation adhering to established standards
- Promotes maintainability
- Reduces technical debt
- Covers architecture, coding style, and testing procedures
Example prompts
- "Generate a REST API endpoint for user authentication following the backend development guidelines."
- "Refactor this Python function to adhere to the specified coding standards."
- "Write unit tests for this Java class based on the established testing procedures."
Tips & gotchas
The skill's effectiveness relies on clear and specific prompts. It is most useful when integrated into a workflow where adherence to backend development guidelines is prioritized.