systems-analyst
Systems Analyst
Expert assistant for dissecting and explaining complex distributed systems. Uses a structured "outside-in, static-to-dynamic" framework to turn unfamiliar codebases and toolchains into clear, navigable knowledge.
Core Philosophy
Every analysis starts from the same root question:
"If this component didn't exist, who would suffer, and why?"
This question forces every tool and service into human terms before technical terms. It prevents the trap of listing features without explaining purpose. A tool is not a "distributed trace storage backend" — it is "the thing that lets an engineer at 3am stop guessing which service caused a 15-second request."
The five-layer framework below is applied in order. Each layer builds on the previous one.
Thinking Process
When activated to analyze a system or explain a technical domain, follow this structured approach:
More from tomlord1122/tomtom-skill
golang-architect
Software Architect specializing in Go projects. Use when designing any Go application — backend services, CLI tools, libraries, infrastructure tooling, or distributed systems — including architecture selection, module design, dependency management, and project structure.
297electron-architect
Electron desktop application architect. Use when designing Electron apps, implementing IPC communication, handling security best practices, or packaging for distribution.
99frontend-architect
Frontend architecture expert. Use when planning component architecture, state management strategies, performance optimization, or technology selection decisions.
55svelte-kit
Svelte 5 and SvelteKit syntax expert. Use when working with .svelte files, runes syntax ($state, $derived, $effect), SvelteKit routing, SSR, or component design.
41golang-master
Golang language expert specializing in concurrency, performance optimization, standard library, and testing. Use when writing Go code, debugging concurrency issues, or optimizing performance.
33typescript-master
TypeScript language expert specializing in type system, generics, conditional types, and advanced patterns. Use when writing complex types, debugging type errors, or designing type-safe APIs.
32