faion-backend-systems
Systems backends: Go, Rust, databases, caching.
Best use case
faion-backend-systems is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Systems backends: Go, Rust, databases, caching.
Teams using faion-backend-systems should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/faion-backend-systems/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How faion-backend-systems Compares
| Feature / Agent | faion-backend-systems | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Systems backends: Go, Rust, databases, caching.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
> **Entry point:** `/faion-net` — invoke this skill for automatic routing to the appropriate domain.
# Backend Developer: Systems
Systems-level backend development in Go and Rust, plus database design and infrastructure patterns.
## Purpose
Handles high-performance backend services using Go and Rust, database design, caching strategies, and backend infrastructure.
---
## Context Discovery
### Auto-Investigation
| Signal | How to Check | What It Tells Us |
|--------|--------------|------------------|
| `go.mod` | `Read("go.mod")` | Go module, dependencies |
| `Cargo.toml` | `Read("Cargo.toml")` | Rust crate, dependencies |
| `cmd/` or `internal/` | `Glob("**/cmd/*")` | Go standard layout |
| `src/main.rs` | `Glob("**/src/main.rs")` | Rust binary |
| Web framework | `Grep("gin\|echo\|fiber", "go.mod")` | Go web framework |
| Async runtime | `Grep("tokio\|actix", "Cargo.toml")` | Rust async framework |
| Database driver | `Grep("sqlx\|gorm\|diesel", "**/*")` | Database library |
### Discovery Questions
#### Q1: Systems Language (if not detected)
```yaml
question: "Which language for this backend?"
header: "Language"
multiSelect: false
options:
- label: "Go"
description: "Simple concurrency, fast compile"
- label: "Rust"
description: "Memory safety, maximum performance"
```
#### Q2: Service Type
```yaml
question: "What type of service?"
header: "Service"
multiSelect: false
options:
- label: "HTTP API"
description: "REST or GraphQL endpoints"
- label: "gRPC service"
description: "High-performance internal API"
- label: "Worker/processor"
description: "Background job processing"
- label: "CLI tool"
description: "Command-line application"
```
#### Q3: Concurrency Needs
```yaml
question: "What are your concurrency requirements?"
header: "Concurrency"
multiSelect: false
options:
- label: "High concurrency (1000s of connections)"
description: "Need goroutines/async"
- label: "Moderate (standard web traffic)"
description: "Standard patterns"
- label: "CPU-bound processing"
description: "Parallel computation"
- label: "Simple sequential"
description: "Minimal concurrency"
```
---
## When to Use
- Go microservices and HTTP APIs
- Rust backend services
- Database design and optimization
- Caching strategies
- Message queues
- Error handling patterns
## Methodologies (22 files)
**Go (10):** go-backend, go-channels, go-concurrency-patterns, go-error-handling, go-error-handling-patterns, go-goroutines, go-http-handlers, go-project-structure, go-standard-layout
**Rust (7):** rust-backend, rust-error-handling, rust-http-handlers, rust-ownership, rust-project-structure, rust-testing, rust-tokio-async
**Database (3):** database-design, nosql-patterns, sql-optimization
**Infrastructure (4):** caching-strategy, error-handling, message-queues
## Tools
**Go:** Standard library, Gin, Echo, GORM, sqlx
**Rust:** Actix-web, Rocket, Tokio, Diesel, sqlx
**Database:** PostgreSQL, MySQL, MongoDB, Redis
**Queues:** RabbitMQ, Kafka, Redis
## Related Sub-Skills
| Sub-skill | Relationship |
|-----------|--------------|
| faion-backend-developer:enterprise | Enterprise web frameworks (Java, C#, PHP, Ruby) |
| faion-python-developer | Python backends (Django, FastAPI) |
| faion-javascript-developer | Node.js backends |
| faion-api-developer | API design patterns |
## Integration
Invoked by parent skill `faion-backend-developer` for Go/Rust/database work.
---
*faion-backend-developer:systems v1.0 | 22 methodologies*Related Skills
fastapi-sqlmodel-arq-backend
构建或改造基于 FastAPI + SQLModel(异步 SQLAlchemy) + Arq + Redis 的后端系统。用于新增/重构 RESTful API、实现异步数据库访问、编写服务层与依赖注入、配置 OAuth2 + JWT(Argon2) 认证、生成 Alembic 迁移建议、统一 loguru 日志规范等后端任务;不用于纯前端页面样式开发或仅做 OpenAPI 客户端同步的任务。
faion-software-developer
Full-stack development: Python, JavaScript, Go, APIs, testing, frontend.
faion-python-skill
No description provided.
faion-python-developer
Python development: Django, FastAPI, async patterns, testing, type hints.
faion-landing-page
High-converting landing pages. Copy + design + implementation. Triggers: landing page, conversion page.
faion-backend-enterprise
Enterprise backends: Java, C#, PHP, Ruby.
faion-api-skill
No description provided.
faion-api-developer
API development: REST, GraphQL, OpenAPI, versioning, auth, rate limiting.
dotnet-backend-patterns
Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuratio...
developing-backend-services
Backend service development best practices. Use when designing, building, or reviewing backend services, REST APIs, gRPC services, microservices, webhooks, message queues, or server-side applications regardless of language or framework.
design-layered-backend-architecture
Design or review a layered backend architecture (routes, controllers, services, repositories) for HTTP APIs and microservices.
data-engineering-backend-architect
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs. Use when: the task directly matches backend architect responsibilities within plugin data-engineering. Do not use when: a more specific framework or task-focused skill is clearly a better match.