microservices
Skill275 starsChanged 34 days agoApache-2.0View on GitHub
Guidelines for building production-grade microservices with FastAPI/Python and Go, covering serverless patterns, clean architecture, observability, and resilience.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- turkeryildirim/ai-skillstheir own version, first seen Nov 1, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- kid-sid/claude-spellbooktheir own version, first seen Oct 9, 2026
- cohen-liel/hivemindtheir own version, first seen Mar 17, 2026
- ffsshhttiikk/opencode-agents-skillstheir own version, first seen Feb 28, 2026
Used with
Projects with it also use api-design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillapi-design
Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- kid-sid/claude-spellbook★ 190same name
- cohen-liel/hivemind★ 108same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- G1Joshi/Agent-Skills★ 15same name
- pluginagentmarketplace/custom-plugin-backend★ 4same name
- turkeryildirim/ai-skills★ 4same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- harrissohail6/claude-code-config★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository264 other files it gives its agents.
- accessibility-a11ySkill
- alpine-jsSkill
- analytics-data-analysisSkill
- android-developmentSkill
- angular-developmentSkill
- angularSkill
- anime-jsSkill
- anthropic-claude-developmentSkill
- api-developmentSkill
- apollo-graphqlSkill
- aspnet-coreSkill
- astroSkill
- auth0-authenticationSkill
- autogen-developmentSkill
- automl-hyperparameter-optimizationSkill
- aws-developmentSkill
- azureSkill
- backend-developmentSkill
- bash-scriptingSkill
- beautifulsoup-parsingSkill
- bitbucket-workflowSkill
- blazorSkill
- blender-python-addonSkill
- blockchainSkill
- bootstrapSkill
- business-central-developmentSkill
- cheerio-parsingSkill
- chrome-extension-developmentSkill
- ci-cd-best-practicesSkill
- clean-architectureSkill
- clean-codeSkill
- clerk-authenticationSkill
- cloudflare-developmentSkill
- computer-vision-opencvSkill
- convexSkill
- cppSkill
- c-sharpSkill
- cssSkill
- cypressSkill
- data-analysis-jupyterSkill
- data-analystSkill
- data-jupyter-pythonSkill
- deep-learning-pythonSkill
- deep-learning-pytorchSkill
- deep-learningSkill
- deno-typescriptSkill
- design-systemsSkill
- devopsSkill
- django-pythonSkill
- django-rest-api-developmentSkill
- dockerSkill
- dotnetSkill
- drizzle-ormSkill
- drupal-developmentSkill
- elasticsearch-best-practicesSkill
- electron-developmentSkill
- elixirSkill
- embedded-stm32Skill
- esbuild-bundlerSkill
- ethereumSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 13 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use circuit breakers and retry patterns for resilience
- Distinctive: line 28
Use OpenTelemetry for distributed tracing
- Distinctive: line 31
Ensure correlation IDs propagate across service boundaries
- Distinctive: line 36
Use Redis or Memcached for caching layers
- Distinctive: line 42
Follow Clean Architecture pattern separating handlers, services, repositories, and domain models
- Distinctive: line 44
Use interface-driven development with dependency injection
- Distinctive: line 45
Keep business logic in the domain layer, not in handlers
- Distinctive: line 59
Use explicit error handling with context wrapping
- Distinctive: line 62
Never ignore errors silently
- Distinctive: line 67
Use channels appropriately for communication
- Distinctive: line 71
Write comprehensive unit tests with table-driven patterns
- Distinctive: line 72
Use mocks for external dependencies
- Distinctive: line 78
Use circuit breakers to prevent cascade failures
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Microservices Development
You are an expert in microservices architecture with FastAPI/Python and Go.
Core Principles
- Design stateless services with external storage and caches (Redis)
- Implement API gateway patterns using NGINX, Traefik, or Kong
- Use circuit breakers and retry patterns for resilience
- Optimize for serverless deployment on AWS Lambda and Azure Functions
FastAPI Python Microservices
Asynchronous Processing
- Handle asynchronous tasks with Celery or RQ
- Implement proper task queuing and worker management
- Design for eventual consistency in distributed systems
Observability
- Use OpenTelemetry for distributed tracing
- Implement structured logging with ELK Stack integration
- Set up Prometheus and Grafana for monitoring and alerting
- Ensure correlation IDs propagate across service boundaries
Security
- Implement OAuth2 for authentication and authorization
- Apply rate limiting and DDoS protection
- Use Redis or Memcached for caching layers
- Validate all inputs at service boundaries
Go Backend Development for Microservices
Architecture
- Follow Clean Architecture pattern separating handlers, services, repositories, and domain models
- Apply domain-driven design principles
- Use interface-driven development with dependency injection
- Keep business logic in the domain layer, not in handlers
Project Structure
project/
cmd/ # Application entry points
internal/ # Private application code
pkg/ # Public libraries
api/ # API definitions (OpenAPI, protobuf)
configs/ # Configuration files
test/ # Additional test utilitiesError Handling
- Use explicit error handling with context wrapping
- Return errors with sufficient context for debugging
- Implement custom error types for domain-specific failures
- Never ignore errors silently
Concurrency
- Manage goroutines safely with proper lifecycle management
- Propagate context through all function calls
- Use channels appropriately for communication
- Implement graceful shutdown patterns
Testing
- Write comprehensive unit tests with table-driven patterns
- Use mocks for external dependencies
- Separate fast unit tests from integration tests
- Implement end-to-end tests for critical paths
Resilience
- Implement retries with exponential backoff
- Use circuit breakers to prevent cascade failures
- Design for graceful degradation
- Handle partial failures appropriately
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

