Agent Dev Backend Api
Invoke a specialized backend agent to design and implement REST or GraphQL endpoints, routes, controllers, and related tests within bounded repo paths.
Overview
Agent Dev Backend API is an agent skill for the Build phase that implements and optimizes backend APIs—REST and GraphQL endpoints, routes, and controllers—within guarded repository paths.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-dev-backend-apiWhat is this skill?
- Triggers on api, endpoint, rest, graphql, backend, and server keywords plus routes/controllers file patterns
- Allowed tools: Read, Write, Edit, MultiEdit, Bash, Grep, Glob, Task with WebSearch restricted
- Path constraints focus edits on src, api, routes, controllers, models, middleware, and tests
- v2 capabilities: self_learning, context_enhancement, fast_processing, smart_coordination
- Autonomous development agent profile (complexity moderate, up to 100 file ops, 600s execution budget)
- v2.0.0-alpha with 4 declared v2 capabilities
- Up to 100 file operations and 600 second execution budget
Adoption & trust: 652 installs on skills.sh; 58.5k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need new API surfaces fast but want an agent that stays in backend folders, respects route/controller conventions, and does not wander into unrelated repos or web distraction.
Who is it for?
Solo builders on JavaScript/Node-style backends who routinely say create endpoint, implement API, or add route and want a dedicated backend dev agent profile.
Skip if: Frontend-only changes, infrastructure-only deploys, or greenfield framework picks with zero existing api/ or routes/ layout.
When should I use this skill?
Keywords api, endpoint, rest, graphql, backend, server; file patterns under api/, routes/, controllers/; tasks like create endpoint, implement API, add route—invoke with $agent-dev-backend-api.
What do I get? / Deliverables
You get implemented or extended API layers—routes, controllers, models, middleware, and tests—edited autonomously under the skill’s allowed paths and tool limits.
- New or updated API endpoints, routes, and controllers
- Supporting models, middleware, and test changes within allowed paths
Recommended Skills
Journey fit
Backend API work is core Build activity once scope is set and before ship-time hardening. Backend subphase covers routes, controllers, models, and middleware—the surfaces this skill’s triggers and allowed paths target.
How it compares
Specialized backend implementation agent—not a OpenAPI linter skill and not a one-shot snippet generator without repo write access.
Common Questions / FAQ
Who is agent-dev-backend-api for?
Indie developers and agentic coders using Ruflo/Claude Code who want autonomous backend API work scoped to api, routes, and controller directories.
When should I use agent-dev-backend-api?
During build backend work when adding REST or GraphQL endpoints, wiring routes and controllers, or extending models and middleware after you have a rough API shape.
Is agent-dev-backend-api safe to install?
It grants Write, Edit, Bash, and broad src access within constraints—treat it as high-trust; review the Security Audits panel on this Prism page and use version control before autonomous runs.
SKILL.md
READMESKILL.md - Agent Dev Backend Api
--- name: "backend-dev" description: "Specialized agent for backend API development with self-learning and pattern recognition" color: "blue" type: "development" version: "2.0.0-alpha" created: "2025-07-25" updated: "2025-12-03" author: "Claude Code" metadata: specialization: "API design, implementation, optimization, and continuous improvement" complexity: "moderate" autonomous: true v2_capabilities: - "self_learning" - "context_enhancement" - "fast_processing" - "smart_coordination" triggers: keywords: - "api" - "endpoint" - "rest" - "graphql" - "backend" - "server" file_patterns: - "**$api/**/*.js" - "**$routes/**/*.js" - "**$controllers/**/*.js" - "*.resolver.js" task_patterns: - "create * endpoint" - "implement * api" - "add * route" domains: - "backend" - "api" capabilities: allowed_tools: - Read - Write - Edit - MultiEdit - Bash - Grep - Glob - Task restricted_tools: - WebSearch # Focus on code, not web searches max_file_operations: 100 max_execution_time: 600 memory_access: "both" constraints: allowed_paths: - "src/**" - "api/**" - "routes/**" - "controllers/**" - "models/**" - "middleware/**" - "tests/**" forbidden_paths: - "node_modules/**" - ".git/**" - "dist/**" - "build/**" max_file_size: 2097152 # 2MB allowed_file_types: - ".js" - ".ts" - ".json" - ".yaml" - ".yml" behavior: error_handling: "strict" confirmation_required: - "database migrations" - "breaking API changes" - "authentication changes" auto_rollback: true logging_level: "debug" communication: style: "technical" update_frequency: "batch" include_code_snippets: true emoji_usage: "none" integration: can_spawn: - "test-unit" - "test-integration" - "docs-api" can_delegate_to: - "arch-database" - "analyze-security" requires_approval_from: - "architecture" shares_context_with: - "dev-backend-db" - "test-integration" optimization: parallel_operations: true batch_size: 20 cache_results: true memory_limit: "512MB" hooks: pre_execution: | echo "🔧 Backend API Developer agent starting..." echo "📋 Analyzing existing API structure..." find . -name "*.route.js" -o -name "*.controller.js" | head -20 # 🧠 v2.0.0-alpha: Learn from past API implementations echo "🧠 Learning from past API patterns..." SIMILAR_PATTERNS=$(npx claude-flow@alpha memory search-patterns "API implementation: $TASK" --k=5 --min-reward=0.85 2>$dev$null || echo "") if [ -n "$SIMILAR_PATTERNS" ]; then echo "📚 Found similar successful API patterns" npx claude-flow@alpha memory get-pattern-stats "API implementation" --k=5 2>$dev$null || true fi # Store task start for learning npx claude-flow@alpha memory store-pattern \ --session-id "backend-dev-$(date +%s)" \ --task "API: $TASK" \ --input "$TASK_CONTEXT" \ --status "started" 2>$dev$null || true post_execution: | echo "✅ API development completed" echo "📊 Running API tests..." npm run test:api 2>$dev$null || echo "No API tests configured" # 🧠 v2.0.0-alpha: Store learning patterns echo "🧠 Storing API pattern for future learning..." REWARD=$(if npm run test:api 2>$dev$null; then echo "0.95"; else echo "0.7"; fi) SUCCESS=$(if npm run test:api 2>$dev$null; then echo "true"; else echo "false"; fi) npx claude-flow@alpha memory store-pattern \ --session-id "backend-dev-$(date +%s)" \ --task "API: $TASK" \ --output "$TASK_OUTPUT" \ --reward "$REWARD" \ --success "$SUCCESS" \ --critique "API implementation with $(find . -name '*.route.js' -o -name '*.controller.js' | wc -l) endpoints" 2>$dev$null || true