System Architecture Translator
Explain how invisible system behavior shaped the interface. Read references/system-to-ux-map.md.
Workflow
- Inspect architecture diagrams, code paths, API contracts, schemas, traces, logs, incidents, and product states.
- Map the end-to-end flow: input, validation, work initiation, intermediate states, persistence, delivery, and recovery.
- Identify nonfunctional constraints that a user can feel:
- latency distribution and long tails;
- availability and partial failure;
- stale, replicated, or conflicting data;
- throughput, load, or rate limits;
- schema and workflow evolution;
- retries, duplication, ordering, and idempotency;
- permission, privacy, and audit boundaries.
- For each constraint, connect the system condition to:
- the user-visible signal;
- the available control;
- the recovery path;
- the evidence that the design worked.
- Separate operational telemetry from user-facing explanation.
- Mark any inferred architecture-to-UX relationship as a hypothesis until supported.
For AI systems, pair this skill with ai-agent-case-study to cover autonomy, uncertainty, and human intervention.
Required sections
Return:
- a system boundary and data-flow summary;
- a System→UX translation map;
- state, latency, and progress behavior;
- failure, retry, rollback, and recovery behavior;
- telemetry and audit design;
- architectural trade-offs and unresolved evidence.
Example
Input:
Jobs fan out across three APIs. Completion ranges from 8 seconds to 4 minutes.
Retries can duplicate a downstream write unless the request key is preserved.
Expected outcome: a state model with queued/running/partial/failed/complete states, durable background progress, cancellability, an idempotency requirement, visible partial results, and a recovery path—without claiming those controls shipped unless artifacts prove it.
1---2name: system-architecture-translator3description: Translate data flows, services, queues, workflows, storage, consistency, latency, failures, retries, and distributed-system constraints into visible product and UX decisions for a case study. Use for AI agents, desktop tools, data products, scraping engines, background jobs, cloud systems, or any portfolio story where architecture determines telemetry, state management, loading, recovery, permissions, or user control.4---56# System Architecture Translator78Explain how invisible system behavior shaped the interface. Read `references/system-to-ux-map.md`.910## Workflow11121. Inspect architecture diagrams, code paths, API contracts, schemas, traces, logs, incidents, and product states.132. Map the end-to-end flow: input, validation, work initiation, intermediate states, persistence, delivery, and recovery.143. Identify nonfunctional constraints that a user can feel:15 - latency distribution and long tails;16 - availability and partial failure;17 - stale, replicated, or conflicting data;18 - throughput, load, or rate limits;19 - schema and workflow evolution;20 - retries, duplication, ordering, and idempotency;21 - permission, privacy, and audit boundaries.224. For each constraint, connect the system condition to:23 - the user-visible signal;24 - the available control;25 - the recovery path;26 - the evidence that the design worked.275. Separate operational telemetry from user-facing explanation.286. Mark any inferred architecture-to-UX relationship as a hypothesis until supported.2930For AI systems, pair this skill with `ai-agent-case-study` to cover autonomy, uncertainty, and human intervention.3132## Required sections3334Return:35361. a system boundary and data-flow summary;372. a System→UX translation map;383. state, latency, and progress behavior;394. failure, retry, rollback, and recovery behavior;405. telemetry and audit design;416. architectural trade-offs and unresolved evidence.4243## Example4445Input:4647```text48Jobs fan out across three APIs. Completion ranges from 8 seconds to 4 minutes.49Retries can duplicate a downstream write unless the request key is preserved.50```5152Expected outcome: a state model with queued/running/partial/failed/complete states, durable background progress, cancellability, an idempotency requirement, visible partial results, and a recovery path—without claiming those controls shipped unless artifacts prove it.
jpoindexter