Kratos Development
aide-family/moon
Develops Go microservices with Kratos v2 following official design philosophy, DDD/Clean Architecture layout, Protobuf API, error/config/middleware patterns, and observability.
A full pipeline for designing, decomposing, communicating, and monitoring microservice architectures.
Install Microservice Designer
$ npx skills add revfactory/harness-100 --skill microservice-designer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 microservice-designer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/microservice-designer .claude/skills/microservice-designer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "microservice-designer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/microservice-designer into .claude/skills/microservice-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microservice-designer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/microservice-designerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add revfactory/harness-100 --skill microservice-designer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 microservice-designer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/microservice-designer .agents/skills/microservice-designer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "microservice-designer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/microservice-designer into .agents/skills/microservice-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microservice-designer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill microservice-designer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 microservice-designer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/microservice-designer .cursor/skills/microservice-designer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "microservice-designer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/microservice-designer into .cursor/skills/microservice-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microservice-designer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/revfactory/harness-100.git --path en/23-microservice-designer/.claude/skills/microservice-designer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add revfactory/harness-100 --skill microservice-designer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 microservice-designer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/microservice-designer .gemini/skills/microservice-designer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "microservice-designer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/microservice-designer into .gemini/skills/microservice-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microservice-designer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install revfactory/harness-100 microservice-designerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add revfactory/harness-100 --skill microservice-designer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/microservice-designer .github/skills/microservice-designer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "microservice-designer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/microservice-designer into .github/skills/microservice-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microservice-designer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill microservice-designer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 microservice-designer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/microservice-designer .opencode/skills/microservice-designer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "microservice-designer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/microservice-designer into .opencode/skills/microservice-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microservice-designer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
microservice-designer- GitHub stars
- 1.3k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 646 words
- Files
- 1
- Skills in repo
- 464
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A full pipeline for designing, decomposing, communicating, and monitoring microservice architectures.
- Works in 3 steps: Preparation (Performed directly by… → Team Assembly and Execution → Integration and Final Deliverables
- Requests like design a microservice architecture
- SKILL.md covers Execution Mode, Agent Composition, Workflow and Modes by Task Scale, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Microservice Designer is an agent skill from revfactory/harness-100. A full pipeline for designing, decomposing, communicating, and monitoring microservice architectures. An agent team collaborates to perform domain analysis, service design, communication patterns, and observability. Use this skill for requests like 'design a microservice architecture', 'decompose services', 'MSA design', 'domain analysis', 'event-driven architecture', 'inter-service communication design', 'distributed system design', 'API gateway design', and other microservice design tasks. Also supports…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Microservices. It works with Kubernetes. The licence is Apache-2.0.
When your agent uses it
- Requests like design a microservice architecture
- Decompose services
- Domain analysis
- Event-driven architecture
Example prompts
- “design a microservice architecture”
- “decompose services”
- “MSA design”
- “/microservice-designer”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8e8d35c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Microservice Designer loads about 1.8k tokens when it runs. Until then it costs about 175 tokens; SKILL.md has 646 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 646 words, ~1,775 tokens.
Download SKILL.mdSave it as
.claude/skills/microservice-designer/SKILL.md (or your agent's skills folder).- name
- microservice-designer
- description
- A full pipeline for designing, decomposing, communicating, and monitoring microservice architectures. An agent team collaborates to perform domain analysis, service design, communication patterns, and observability. Use this skill for requests like 'design a microservice architecture', 'decompose services', 'MSA design', 'domain analysis', 'event-driven architecture', 'inter-service communication design', 'distributed system design', 'API gateway design', and other microservice design tasks. Also supports transitioning from an existing monolith to MSA. Note: actual infrastructure setup, Kubernetes deployment, and code implementation are outside the scope of this skill.
Microservice Designer — Microservice Architecture Design Pipeline
An agent team collaborates to perform domain analysis -> service design -> communication design -> observability design.
Execution Mode
Agent Team — 5 members communicate directly via SendMessage and cross-validate each other.
Agent Composition
| Agent | File | Role | Type |
|---|---|---|---|
| domain-analyst | .claude/agents/domain-analyst.md | Bounded contexts, event storming | general-purpose |
| service-architect | .claude/agents/service-architect.md | API contracts, data ownership, deployment units | general-purpose |
| communication-designer | .claude/agents/communication-designer.md | Sync/async, event bus, Saga | general-purpose |
| observability-engineer | .claude/agents/observability-engineer.md | Metrics, logging, tracing, alerting | general-purpose |
| architecture-reviewer | .claude/agents/architecture-reviewer.md | Cross-validation, anti-pattern detection | general-purpose |
Workflow
Phase 1: Preparation (Performed directly by Orchestrator)
- Extract from user input:
- Business Domain: What system/service is being designed
- Current State (optional): Whether this is a monolith migration or a greenfield design
- Scale/Constraints (optional): Expected traffic, team size, technology stack limitations
- Existing Documentation (optional): ERD, architecture documents, API documentation, etc.
- Create
_workspace/directory at the project root - Organize input and save to
_workspace/00_input.md - If existing files are available, skip the corresponding Phase
Phase 2: Team Assembly and Execution
| Order | Task | Assignee | Dependencies | Deliverable |
|---|---|---|---|---|
| 1 | Domain Analysis | analyst | None | _workspace/01_domain_analysis.md |
| 2 | Service Design | architect | Task 1 | _workspace/02_service_design.md |
| 3a | Communication Design | comm-designer | Tasks 1, 2 | _workspace/03_communication_design.md |
| 3b | Observability Design | obs-engineer | Task 2 | _workspace/04_observability_design.md |
| 4 | Architecture Review | reviewer | Tasks 1-3b | _workspace/05_review_report.md |
Tasks 3a (communication) and 3b (observability) can be executed in parallel.
Inter-team Communication Flow:
- analyst completes -> delivers bounded contexts and aggregates to architect; delivers domain events to comm-designer
- architect completes -> delivers service catalog and API contracts to comm-designer; delivers service list and dependencies to obs-engineer
- comm-designer completes -> delivers communication matrix and Saga flows to obs-engineer
- reviewer cross-validates all deliverables. When RED Must Fix items are found, requests fixes from the relevant agent -> rework -> re-verification (up to 2 times)
Phase 3: Integration and Final Deliverables
- Check all files in
_workspace/ - Verify that all RED Must Fix items from the review report have been addressed
- Report the final summary to the user
Modes by Task Scale
| User Request Pattern | Execution Mode | Deployed Agents |
|---|---|---|
| "Design a microservice architecture" | Full Pipeline | All 5 agents |
| "Analyze the domain", "Event storming" | Domain Mode | analyst + reviewer |
| "Decompose services" (domain analysis exists) | Service Mode | architect + reviewer |
| "Design inter-service communication" | Communication Mode | comm-designer + reviewer |
| "Design monitoring/observability" | Observability Mode | obs-engineer + reviewer |
Data Transfer Protocol
| Strategy | Method | Purpose |
|---|---|---|
| File-based | _workspace/ directory | Store and share main deliverables |
| Message-based | SendMessage | Real-time delivery of key information, fix requests |
| Task-based | TaskCreate/TaskUpdate | Progress tracking, dependency management |
Show full SKILL.md (255 more words)Show less
Error Handling
| Error Type | Strategy |
|---|---|
| Insufficient domain information | Draft using similar domain reference patterns, request user validation |
| Too many services | Suggest modular monolith -> gradual decomposition roadmap |
| Agent failure | Retry once -> if fails, proceed without that deliverable, note omission in review |
| RED found in review | Request fix from relevant agent -> rework -> re-verify (up to 2 times) |
| Distributed monolith signs | Request service boundary readjustment from architect |
Test Scenarios
Normal Flow
Prompt: "Design an e-commerce platform with microservice architecture. Order, payment, shipping, inventory, and user management are the core features." Expected Result:
- Domain: 5 bounded contexts, context map, event storming results
- Service: 5-7 service catalog, API contracts, data ownership mapping
- Communication: Order-Payment-Shipping Saga, event bus topic design, circuit breaker configuration
- Observability: SLI/SLO definitions, distributed tracing design, alerting system
- Review: Full consistency verification across all items, distributed system anti-pattern checks
Existing File Utilization Flow
Prompt: "I want to migrate a Django monolith to MSA. I have ERD and API documentation." + file attachments Expected Result:
- Reverse-extract bounded contexts from the existing ERD
- Include Strangler Fig pattern-based gradual migration roadmap
- Include existing API backward compatibility maintenance strategy
Error Flow
Prompt: "Build a chat app with microservices" Expected Result:
- Distinguish between "design" and "implementation," performing only design
- Include communication design specialized for real-time communication (WebSocket/SSE)
- Inform that implementation is outside the scope of this skill
Agent Extension Skills
| Skill | Path | Enhanced Agent | Role |
|---|---|---|---|
| ddd-context-mapping | .claude/skills/ddd-context-mapping/skill.md | domain-analyst, service-architect | Bounded context identification, event storming, context map relationship types, aggregate design |
| distributed-patterns | .claude/skills/distributed-patterns/skill.md | communication-designer, service-architect | Distributed transaction (Saga), CQRS, Circuit Breaker, Event Sourcing implementation patterns |
© revfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in en/23-microservice-designer/.claude/skills/microservice-designer of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Compare with similar skills
Microservice Designer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Microservice Designer this skillrevfactory/harness-100 | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Kratos Developmentaide-family/moon | 253 | — | ~1.5k | Automated safety check: Pass | None | |
| Configuring Service Meshesjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ak Cloud Deployyaalalabs/agent-kernel | 192 | — | ~14k | Automated safety check: Pass | Apache-2.0 | |
| K8s Istio Bypasswgpsec/AboutSecurity | 1.8k | — | ~727 | Automated safety check: Pass | None | |
| K8e Sandboxxiaods/k8e | 500 | — | ~6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Configuring Service Meshes
jeremylongshore/tons-of-skills-marketplace
Configure this skill configures service meshes like istio and linkerd for microservices.
Ak Cloud Deploy
yaalalabs/agent-kernel
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart.
K8s Istio Bypass
wgpsec/AboutSecurity
Istio Service Mesh 安全策略绕过。当目标 K8s 集群使用 Istio、请求被 AuthorizationPolicy 拒绝（403 RBAC denied）、或发现 Envoy sidecar 时使用。核心手法：UID 1337 绕过 Envoy。任何在 K8s 中遇到 Istio 策略阻拦、Service Mesh 限制、或 Envoy 相关安全控制的场景都应使用此技能
K8e Sandbox
xiaods/k8e
Run a goal end to end inside an isolated K8E sandbox pod (gVisor / Kata / Firecracker) instead of on the host: exec bash / Python / Node / TypeScript, install packages, move files in and out, reuse…
Intrinsic Core Service Authoring
intrinsic-ai/intrinsic-core
Intrinsic Core microservice authoring, ServiceManifest definitions (realspec vs simspec), RuntimeContext port bindings (gRPC port 1 vs HTTP port 7), SIGTERM lifecycle handling, and .binpb sideloading.
More from revfactory/harness-100
All 464 skills in this repoAnti Bot Analyzer
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
API Security Checklist
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
Arg Parser Generator
revfactory/harness-100
Methodology for systematically designing and generating CLI tool argument parser structures.
Audience Segmentation
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
Audio Storytelling
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
Related
Works with
Categories
Questions about Microservice Designer
What does Microservice Designer do?
A full pipeline for designing, decomposing, communicating, and monitoring microservice architectures. Microservice Designer is an agent skill from revfactory/harness-100. A full pipeline for designing, decomposing, communicating, and monitoring microservice architectures.
When should I use Microservice Designer?
Microservice Designer fits situations like: requests like design a microservice architecture; decompose services; domain analysis; event-driven architecture.
How do I install Microservice Designer in Claude Code?
Run `npx skills add revfactory/harness-100 --skill microservice-designer -a claude-code`. Or copy the skill folder (en/23-microservice-designer/.claude/skills/microservice-designer in revfactory/harness-100) into .claude/skills/microservice-designer in your project. Claude Code loads it when a task matches its description.
How do I install Microservice Designer in Codex?
Run `npx skills add revfactory/harness-100 --skill microservice-designer -a codex`. Or copy the skill folder (en/23-microservice-designer/.claude/skills/microservice-designer in revfactory/harness-100) into .agents/skills/microservice-designer in your project. Codex loads it when a task matches its description.
Can I use Microservice Designer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add revfactory/harness-100 --skill microservice-designer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/microservice-designer, .gemini/skills/microservice-designer, .github/skills/microservice-designer and .opencode/skills/microservice-designer in your project.
What does Microservice Designer need to run?
SKILL.md names no scripts, command-line tools or credentials: Microservice Designer is instructions for the agent only.
Does Microservice Designer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Microservice Designer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Microservice Designer use?
Microservice Designer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Microservice Designer use?
About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Microservice Designer?
Skills that share tags, products or a category with Microservice Designer: Kratos Development (aide-family/moon, 253 stars), Configuring Service Meshes (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Ak Cloud Deploy (yaalalabs/agent-kernel, 192 stars) and K8s Istio Bypass (wgpsec/AboutSecurity, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Microservice Designer?
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,295 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.