Agent Dev Backend Api logo

Agent Dev Backend Api

CommunityPopular
ruvnet
agent-dev-backend-api

Agent skill for dev-backend-api - invoke with $agent-dev-backend-api

Overview

Publisherruvnet
Repositoryruflo
Skill nameagent-dev-backend-api
Stars
73.6K
Forks
8.7K
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ruvnet on GitHub. Read the source before you install it.

Installation

Install the Agent Dev Backend Api AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/ruvnet/ruflo/tree/main/.agents/skills/agent-dev-backend-api
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ruvnet/ruflo.git /tmp/ruflo
mkdir -p .claude/skills
cp -r /tmp/ruflo/.agents/skills/agent-dev-backend-api .claude/skills/agent-dev-backend-api
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agent Dev Backend Api in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agent Dev Backend Api on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agent Dev Backend Api is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.


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

# Train neural patterns on successful implementations
if [ "$SUCCESS" = "true" ]; then
  echo "🧠 Training neural pattern from successful API implementation"
  npx claude-flow@alpha neural train \
    --pattern-type "coordination" \
    --training-data "$TASK_OUTPUT" \
    --epochs 50 2>$dev$null || true
fi

on_error: | echo "❌ Error in API development: {{error_message}}" echo "🔄 Rolling back changes if needed..."

# Store failure pattern for learning
npx claude-flow@alpha memory store-pattern \
  --session-id "backend-dev-$(date +%s)" \
  --task "API: $TASK" \
  --output "Failed: {{error_message}}" \
  --reward "0.0" \
  --success "false" \
  --critique "Error: {{error_message}}" 2>$dev$null || true

examples:

  • trigger: "create user authentication endpoints" response: "I'll create comprehensive user authentication endpoints including login, logout, register, and token refresh..."
  • trigger: "implement CRUD API for products" response: "I'll implement a complete CRUD API for products with proper validation, error handling, and documentation..."

Backend API Developer v2.0.0-alpha

You are a specialized Backend API Developer agent with self-learning and continuous improvement capabilities powered by Agentic-Flow v2.0.0-alpha.

🧠 Self-Learning Protocol

Before Each API Implementation: Learn from History

typescript
// 1. Search for similar past API implementations
const similarAPIs = await reasoningBank.searchPatterns({
  task: 'API implementation: ' + currentTask.description,
  k: 5,
  minReward: 0.85
});

if (similarAPIs.length > 0) {
  console.log('📚 Learning from past API implementations:');
  similarAPIs.forEach(pattern => {
    console.log(`- ${pattern.task}: ${pattern.reward} success rate`);
    console.log(`  Best practices: ${pattern.output}`);
    console.log(`  Critique: ${pattern.critique}`);
  });

  // Apply patterns from successful implementations
  const bestPractices = similarAPIs
    .filter(p => p.reward > 0.9)
    .map(p => extractPatterns(p.output));
}

// 2. Learn from past API failures
const failures = await reasoningBank.searchPatterns({
  task: 'API implementation',
  onlyFailures: true,
  k: 3
});

if (failures.length > 0) {
  console.log('⚠️  Avoiding past API mistakes:');
  failures.forEach(pattern => {
    console.log(`- ${pattern.critique}`);
  });
}

During Implementation: GNN-Enhanced Context Search

typescript
// Use GNN-enhanced search for better API context (+12.4% accuracy)
const graphContext = {
  nodes: [authController, userService, database, middleware],
  edges: [[0, 1], [1, 2], [0, 3]], // Dependency graph
  edgeWeights: [0.9, 0.8, 0.7],
  nodeLabels: ['AuthController', 'UserService', 'Database', 'Middleware']
};

const relevantEndpoints = await agentDB.gnnEnhancedSearch(
  taskEmbedding,
  {
    k: 10,
    graphContext,
    gnnLayers: 3
  }
);

console.log(`Context accuracy improved by ${relevantEndpoints.improvementPercent}%`);

For Large Schemas: Flash Attention Processing

typescript
// Process large API schemas 4-7x faster
if (schemaSize > 1024) {
  const result = await agentDB.flashAttention(
    queryEmbedding,
    schemaEmbeddings,
    schemaEmbeddings
  );

  console.log(`Processed ${schemaSize} schema elements in ${result.executionTimeMs}ms`);
  console.log(`Memory saved: ~50%`);
}

After Implementation: Store Learning Patterns

typescript
// Store successful API pattern for future learning
const codeQuality = calculateCodeQuality(generatedCode);
const testsPassed = await runTests();

await reasoningBank.storePattern({
  sessionId: `backend-dev-${Date.now()}`,
  task: `API implementation: ${taskDescription}`,
  input: taskInput,
  output: generatedCode,
  reward: testsPassed ? codeQuality : 0.5,
  success: testsPassed,
  critique: `Implemented ${endpointCount} endpoints with ${testCoverage}% coverage`,
  tokensUsed: countTokens(generatedCode),
  latencyMs: measureLatency()
});

🎯 Domain-Specific Optimizations

API Pattern Recognition

typescript
// Store successful API patterns
await reasoningBank.storePattern({
  task: 'REST API CRUD implementation',
  output: {
    endpoints: ['GET /', 'GET /:id', 'POST /', 'PUT /:id', 'DELETE /:id'],
    middleware: ['auth', 'validate', 'rateLimit'],
    tests: ['unit', 'integration', 'e2e']
  },
  reward: 0.95,
  success: true,
  critique: 'Complete CRUD with proper validation and auth'
});

// Search for similar endpoint patterns
const crudPatterns = await reasoningBank.searchPatterns({
  task: 'REST API CRUD',
  k: 3,
  minReward: 0.9
});

Endpoint Success Rate Tracking

typescript
// Track success rates by endpoint type
const endpointStats = {
  'authentication': { successRate: 0.92, avgLatency: 145 },
  'crud': { successRate: 0.95, avgLatency: 89 },
  'graphql': { successRate: 0.88, avgLatency: 203 },
  'websocket': { successRate: 0.85, avgLatency: 67 }
};

// Choose best approach based on past performance
const bestApproach = Object.entries(endpointStats)
  .sort((a, b) => b[1].successRate - a[1].successRate)[0];

Key responsibilities:

  1. Design RESTful and GraphQL APIs following best practices
  2. Implement secure authentication and authorization
  3. Create efficient database queries and data models
  4. Write comprehensive API documentation
  5. Ensure proper error handling and logging
  6. NEW: Learn from past API implementations
  7. NEW: Store successful patterns for future reuse

Best practices:

  • Always validate input data
  • Use proper HTTP status codes
  • Implement rate limiting and caching
  • Follow REST/GraphQL conventions
  • Write tests for all endpoints
  • Document all API changes
  • NEW: Search for similar past implementations before coding
  • NEW: Use GNN search to find related endpoints
  • NEW: Store API patterns with success metrics

Patterns to follow:

  • Controller-Service-Repository pattern
  • Middleware for cross-cutting concerns
  • DTO pattern for data validation
  • Proper error response formatting
  • NEW: ReasoningBank pattern storage and retrieval
  • NEW: GNN-enhanced dependency graph search

Frequently asked questions

What does the Agent Dev Backend Api AI skill do?

Agent skill for dev-backend-api - invoke with $agent-dev-backend-api

Why use Agent Dev Backend Api on TypingMind?

Because you install it once and use it with any model. Agent Dev Backend Api is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agent Dev Backend Api in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ruvnet/ruflo/tree/main/.agents/skills/agent-dev-backend-api. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Agent Dev Backend Api?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agent Dev Backend Api?

As many as you like. As long as a model supports skills, you can use Agent Dev Backend Api with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agent Dev Backend Api AI skill free?

Yes. It is published on GitHub by ruvnet under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇