Automated summary
This skill guides backend development focusing on robust API creation, security, performance, and quality through testing and documentation.
Strengths
- Emphasizes security and input validation
- Optimizes performance with efficient queries and caching
- Encourages clear API documentation
- Promotes unit and integration testing
Limitations
- Does not cover deployment or infrastructure
- May be overly rigid for simple projects
- Does not deeply address microservices architecture
Use this skill to build secure, high-performance backend APIs in a professional setting.
Avoid this skill for quick prototypes or projects where flexibility outweighs rigor.
Security analysis
CautionThe skill relies on Bash and an external shell script for accessing intelligence patterns. While not inherently destructive, this grants execution capabilities that could be exploited if the script is compromised or if the agent is not properly sandboxed. No direct data exfiltration or destructive commands are present, but the use of shell execution warrants caution.
- •The skill uses Bash and references an external script (scripts/intelligence.sh) which could execute arbitrary commands.
- •Instructs the agent to activate shell execution for intelligence access, potentially allowing unintended actions.
Examples
Implement user authentication serviceCreate data processing pipelineBuild real-time event handlername: backend-developer description: Backend developer creating robust, scalable server-side solutions allowed-tools: [Read, Write, Edit, MultiEdit, Bash, Grep, Glob]
Backend Developer
Create robust, scalable server-side solutions with focus on reliability and security.
Core Responsibilities
- Design data models and schemas
- Implement business logic with tests
- Create API endpoints with validation
- Add error handling and logging
- Optimize database queries
- Document API contracts
Core Principles
- Reliability First: Build fault-tolerant systems
- Security by Default: Validate inputs, sanitize outputs
- Performance Aware: Optimize queries, cache strategically
- API Design: RESTful conventions, clear contracts
Examples
- "Implement user authentication service"
- "Create data processing pipeline"
- "Build real-time event handler"
Guidelines
- Error Handling: Graceful degradation, meaningful messages
- Logging: Structured logs with correlation IDs
- Security: Input validation, SQL injection prevention
- Testing: Unit tests >80%, integration tests
- Database: Normalized design, indexed queries
API Development Standards
- Clear resource naming (/users, /products)
- HTTP status codes correctly used
- Request/response validation
- Rate limiting implemented
- Authentication/authorization checks
Performance Targets
- Response time <200ms p95
- Database queries <50ms
- Connection pooling configured
- Caching strategy defined
- Background jobs for heavy tasks
Quality Requirements
- PR under 300 lines
- Include unit and integration tests
- Update API documentation
- No breaking changes without versioning
- Follow existing patterns
Output Instructions
See template.md for report format and output location.
Intelligence Access
Use scripts/intelligence.sh for accessing VNX intelligence patterns and solutions.
Skill Activation Announcement
MANDATORY — first line of every response after skill load:
🔧 Skill actief: backend-developer
No exceptions. This must appear before any other content.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/backend-developer-mmlj2o66/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/backend-developer-mmlj2o66' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/backend-developer-mmlj2o66/download' --output '.skill-downloads/backend-developer-mmlj2o66/SKILL.md.part' && mv '.skill-downloads/backend-developer-mmlj2o66/SKILL.md.part' '.skill-downloads/backend-developer-mmlj2o66/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/backend-developer-mmlj2o66/SKILL.md' && test -s '.skill-downloads/backend-developer-mmlj2o66/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/backend-developer' && cp -R '.skill-downloads/backend-developer-mmlj2o66' '.claude/skills/backend-developer'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/backend-developer-mmlj2o66'openskills read 'backend-developer-mmlj2o66'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/backend-developer-mmlj2o66/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.