Automated summary
An architecture skill that guides microservices design: domain boundaries, service contracts, event-driven communication, distributed data management and resilience.
Strengths
- Spans the full picture: service boundaries, contracts, data ownership, resilience, observability and deployment strategy
- Ships an explicit "do not use" section that rules out modular monoliths and quick prototypes
- Follows a four-step procedure (domains, contracts, resilience/operations, migration) usable directly in an architecture review
- Points to an implementation playbook for the detailed patterns and examples
Limitations
- The SKILL.md itself contains no code or worked example — the substantial detail lives in resources/implementation-playbook.md
- No concrete technology is covered (Kafka, gRPC, Kubernetes and sagas are not named), so it gives little help choosing tooling
- Assumes operational maturity; of limited use without a platform team or observability already in place
Use it when decomposing a monolith, defining boundaries and contracts between services, or designing event-driven communication and resilience strategies.
Skip it for a small system or a fast prototype, where a modular monolith is enough and distributed complexity would be premature.
Security analysis
SafeThe skill contains only architectural guidance and no executable instructions, scripts, network calls, credential handling, or destructive operations. It does not declare tools or request sensitive data.
No concerns found
How this analysis is madeExamples
We have a 400k-line Rails monolith for an e-commerce platform. Help me identify domain boundaries and propose a step-by-step decomposition into microservices, with data ownership per service.Design the communication patterns between our order, payment and inventory services — decide synchronous vs event-driven, define the contracts, and cover failure and retry handling.Review this microservices design for resilience gaps: timeouts, circuit breakers, retries, idempotency and observability. List what's missing and how to fix it.name: microservices-patterns description: "Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing micros..." risk: unknown source: rootcastle-rei
Microservices Patterns
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
Use this skill when
- Decomposing monoliths into microservices
- Designing service boundaries and contracts
- Implementing inter-service communication
- Managing distributed data and transactions
- Building resilient distributed systems
- Implementing service discovery and load balancing
- Designing event-driven architectures
Do not use this skill when
- The system is small enough for a modular monolith
- You need a quick prototype without distributed complexity
- There is no operational support for distributed systems
Instructions
- Identify domain boundaries and ownership for each service.
- Define contracts, data ownership, and communication patterns.
- Plan resilience, observability, and deployment strategy.
- Provide migration steps and operational guardrails.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
🏰 Rei Skills — Curated by Rootcastle Engineering & Innovation | Batuhan Ayrıbaş
Engineering Beyond Boundaries | admin@rootcastle.com
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/microservices-patterns-mrzxur1q/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/microservices-patterns-mrzxur1q' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/microservices-patterns-mrzxur1q/download' --output '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md.part' && mv '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md.part' '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md' && test -s '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/microservices-patterns' && cp -R '.skill-downloads/microservices-patterns-mrzxur1q' '.claude/skills/microservices-patterns'Cursor
test -f '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md' && test -s '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/microservices-patterns' && cp -R '.skill-downloads/microservices-patterns-mrzxur1q' '.cursor/skills/microservices-patterns'Codex
test -f '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md' && test -s '.skill-downloads/microservices-patterns-mrzxur1q/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/microservices-patterns' && cp -R '.skill-downloads/microservices-patterns-mrzxur1q' '.agents/skills/microservices-patterns'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/microservices-patterns-mrzxur1q'openskills read 'microservices-patterns-mrzxur1q'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/microservices-patterns-mrzxur1q/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.