backend-ai-guide
This skill fetches and synthesizes official Backend.AI documentation from the project's GitHub repository to answer technical questions about platform architecture, components, setup, APIs, and features. Use it when users inquire about Backend.AI's Manager, Agent, Storage Proxy, Webserver, App Proxy components, infrastructure requirements, REST or GraphQL APIs, session scheduling, resource allocation, container runtimes, or how the WebUI integrates with Backend.AI backends.
git clone --depth 1 https://github.com/Microck/ordinary-claude-skills /tmp/backend-ai-guide && cp -r /tmp/backend-ai-guide/skills_all/backend-ai-guide ~/.claude/skills/backend-ai-guideSKILL.md
# Backend.AI Guide Skill ## Purpose This skill provides expert-level information about the Backend.AI platform by: - Fetching official documentation from the Backend.AI GitHub repository - Recursively exploring Major Components documentation links - Following relevant links to gather comprehensive technical details - Providing accurate, source-backed answers about Backend.AI architecture and features ## When to Use Activate this skill when the user asks about: - Backend.AI platform overview or architecture - Backend.AI components (Manager, Agent, Storage Proxy, Webserver, App Proxy) - Backend.AI setup, requirements, or infrastructure - Backend.AI APIs (REST, GraphQL) - Backend.AI features (session scheduling, resource allocation, multi-tenancy) - Backend.AI kernels, containers, or runtime elements - How the WebUI connects to or interacts with Backend.AI backend - Differences between Backend.AI components ## Primary Documentation Sources 1. **Main README**: https://github.com/lablup/backend.ai/blob/main/README.md - Overview and architecture - Major Components section with component links - Requirements and setup information 2. **Major Component READMEs**: Follow links from the Major Components section - Manager component details - Agent component details - Storage Proxy details - Webserver details - App Proxy details - And other components 3. **Recursive Link Following**: When a component README references additional documentation, follow those links to gather comprehensive information ## Instructions ### Step 1: Identify the Question Scope - Determine what aspect of Backend.AI the user is asking about - Identify which components or features are relevant ### Step 2: Fetch the Main README - Always start by fetching: https://github.com/lablup/backend.ai/blob/main/README.md - Extract key information relevant to the question - Identify links to Major Components that need to be explored ### Step 3: Recursively Fetch Component Documentation - For questions about specific components, fetch their individual READMEs - Component README links are found in the "Major Components" section - Example component paths (adjust based on actual links): - Manager: `src/ai/backend/manager/README.md` - Agent: `src/ai/backend/agent/README.md` - Storage Proxy: `src/ai/backend/storage/README.md` - Webserver: `src/ai/backend/web/README.md` - App Proxy: `src/ai/backend/appproxy/README.md` ### Step 4: Follow Additional Links - If component READMEs reference additional documentation, follow those links - Common additional documentation types: - Architecture diagrams - API documentation - Configuration guides - Development guides - **Important**: Only follow links that are relevant to answering the user's question ### Step 5: Synthesize and Present Information - Combine information from all fetched sources - Structure the answer logically: 1. Direct answer to the user's question 2. Supporting details from official documentation 3. Related component interactions (if applicable) 4. Links to source documentation for further reading - Use clear headings and formatting - Include code examples or configuration snippets when relevant ## Best Practices 1. **Always Cite Sources** - Reference the specific documentation URLs you fetched - Help users find more detailed information 2. **Stay Current** - Fetch documentation fresh each time (don't rely on cached knowledge) - Note version requirements (Python, Docker, PostgreSQL, etc.) 3. **Explain Component Interactions** - Backend.AI is a distributed system - explain how components work together - Clarify the relationship between WebUI (this project) and Backend.AI backend 4. **Be Precise with Technical Details** - Include version numbers, requirements, and configuration details - Distinguish between different API types (REST vs GraphQL) 5. **Limit Recursion Depth** - Fetch main README + relevant component READMEs - Only follow 1-2 additional link levels unless user needs deep details - Balance thoroughness with response time ## Example Question Types **Architecture Questions** - "How does Backend.AI work?" - "What is the architecture of Backend.AI?" - "What are the main components of Backend.AI?" **Component Questions** - "What does the Backend.AI Manager do?" - "How does the Agent component work?" - "What is the Storage Proxy?" **Integration Questions** - "How does this WebUI connect to Backend.AI?" - "What APIs does Backend.AI expose?" - "How do I authenticate with Backend.AI?" **Setup Questions** - "What are the requirements for Backend.AI?" - "How do I set up Backend.AI?" - "What infrastructure does Backend.AI need?" ## Response Format Structure answers as follows: ```markdown ## [Direct Answer to Question] [Concise, direct answer based on official documentation] ## Details [Supporting information from fetched documentation] ### Component Interactions (if applicable) [How different components work together] ## Technical Specifications (if applicable) - Requirements: [versions, dependencies] - Configuration: [relevant settings] - APIs: [REST/GraphQL endpoints] ## Source Documentation - Main: [URL to main README] - Component: [URLs to component READMEs] - Additional: [URLs to other relevant docs] ``` ## Notes - Backend.AI is the **backend platform** that this WebUI project connects to - This WebUI (backend.ai-webui) is a **client application** that uses Backend.AI's APIs - When users ask about "the backend" in this project context, they likely mean Backend.AI - Distinguish between WebUI code (this project) and Backend.AI platform code (separate repo) ## Limitations - This skill only fetches publicly available GitHub documentation - For questions requiring internal documentation or specific deployment details, direct users to Backend.AI team - Cannot access private repositories or non-public documentation
Testing patterns for PHPUnit and Playwright E2E tests. Use when writing tests, debugging test failures, setting up test coverage, or implementing test patterns for ActivityPub features.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
Master advanced AgentDB features including QUIC synchronization, multi-database management, custom distance metrics, hybrid search, and distributed systems integration. Use when building distributed AI systems, multi-agent coordination, or advanced vector search applications.
Create and train AI learning plugins with AgentDB's 9 reinforcement learning algorithms. Includes Decision Transformer, Q-Learning, SARSA, Actor-Critic, and more. Use when building self-learning agents, implementing RL, or optimizing agent behavior through experience.
Implement persistent memory patterns for AI agents using AgentDB. Includes session memory, long-term storage, pattern learning, and context management. Use when building stateful agents, chat systems, or intelligent assistants.
Optimize AgentDB performance with quantization (4-32x memory reduction), HNSW indexing (150x faster search), caching, and batch operations. Use when optimizing memory usage, improving search speed, or scaling to millions of vectors.