flowmaster-overview

Document FlowMaster system architecture across 29 services on a K3S cluster.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/eron1703/claude-config-loader --skill flowmaster-overview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowmaster-overview
Source: https://github.com/eron1703/claude-config-loader/tree/main/skills/flowmaster-overview
Command: npx skills add https://github.com/eron1703/claude-config-loader --skill flowmaster-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a concise, high-level overview of FlowMaster's architecture to help engineers and stakeholders understand system topology and deployment details.

Core Features & Use Cases

  • Architecture overview: outlines the 29 running services, core business logic, and new services in the FlowMaster stack.
  • Deployment patterns: documents how FlowMaster is deployed on K3S, including service topology, gateways, and data stores.
  • Decision context: explains key architectural decisions and how components interact for planning and onboarding.

Quick Start

Generate a high-level FlowMaster architecture summary for the current deployment.

Frequently Asked Questions about flowmaster-overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document microservices architecture for a K3S cluster deployment?

To generate a microservices architecture overview, use this Skill to document 29 running services, core business logic, and deployment patterns on a K3S cluster. It validates service mapping and architectural decisions for system topology explanations.

How do I map system topology for 29 services in a microservices deployment?

Mapping system topology for 29 services requires documenting core and new services alongside frontend components and deployment servers. This Skill validates service mapping and deployment topology to explain how components interact for planning and onboarding.

Can I use this to validate architectural decisions for high-level system design explanations?

Yes, you can validate architectural decisions for high-level system design explanations. The Skill documents FlowMaster system architecture, covering decision context and explaining how components interact to support planning and onboarding.

What's the best way to understand deployment patterns on a K3S cluster?

Understanding deployment patterns on a K3S cluster is best achieved by documenting service topology, gateways, and data stores. This Skill provides a concise overview of FlowMaster's deployment details to help engineers and stakeholders understand the system.

Does documenting architecture decisions require prerequisite knowledge of the service stack?

Documenting architecture decisions does not require prerequisite knowledge of the service stack. The Skill provides a concise, high-level overview of FlowMaster's 29 services and core business logic to help engineers and stakeholders understand system topology.