backend-architecture

스타6

포크1

업데이트2026년 7월 30일 03:03

Backend architecture reference for the TeensyROM .NET 9 Web API. Use when working on the backend/API, understanding RadEndpoints structure, MediatR CQRS pipeline behaviors, serial device communication protocol, storage/caching (indexing, favorites, StorageCache), device connection management, or backend operational concerns (configuration, error handling, retries, observability, logging). Covers Clean Architecture layering, key components, endpoint patterns, MediatR flow diagrams, dependency map, and architecture patterns/anti-patterns to follow or avoid.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

MetalHexx

MetalHexx/TeensyROM-Web

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Backend Architecture Skill

Reference for the TeensyROM .NET 9 backend: a layered Web API managing physical TeensyROM devices over serial ports, with CQRS via MediatR, storage indexing/caching, and real-time SignalR streaming to the frontend.

When to Use This Skill

Working on the .NET API/backend (apps/api/src/TeensyRom.*)
Understanding endpoint structure (RadEndpoints) or adding new endpoints
Tracing the MediatR pipeline (LoggingBehavior, ExceptionBehavior, SerialBehavior) or command/handler flow
Understanding serial device communication (state machine, ACK/NAK protocol, reconnection logic)
Working with storage/indexing/caching (StorageService, StorageCache, favorites, metadata enrichment)
Investigating backend operational concerns: configuration, error handling, retries/timeouts, health checks, logging/observability
Reviewing architecture patterns to follow or anti-patterns to avoid in backend code

Overview

Core Responsibilities:

Device discovery, connection, and health monitoring over serial ports
Serial protocol command execution with state management and error recovery
Storage indexing/search/caching of device SD/USB contents
File launching (transfer + execute on Commodore 64 via TeensyROM cartridge)
Real-time log/event streaming to the frontend via SignalR
RESTful API surface via RadEndpoints with auto-generated OpenAPI specs

Layering: TeensyRom.Api → TeensyRom.Core.Device → TeensyRom.Core.Serial / TeensyRom.Core.Storage → TeensyRom.Core (domain entities, contracts, shared utilities — referenced by all other projects).

Critical pattern: all device operations flow through MediatR with pipeline behaviors (logging, exception handling, serial locking/state transitions) before reaching handlers that execute serial/storage operations.

Full Reference

See references/BACKEND_ARCHITECTURE.md for the complete architecture document, including:

System architecture diagram and key components per layer (API, Device, Serial, Storage)
Endpoint organization, versioning/validation conventions, and a typical endpoint code example
Serial pipeline behaviors, command protocol (ACK/NAK), error handling/reconnection logic
MediatR sequence diagrams for serial commands and storage indexing
Storage/indexing deep dive: cache file structure, indexing strategies, read/write paths, metadata enrichment
Major dependencies and dependency flow between projects
Operational concerns: configuration, error handling layers, retries/timeouts, health checks, logging/observability
Architecture patterns to embrace and anti-patterns to avoid
Integration seams (frontend↔backend, backend↔hardware, storage↔serial)

For OpenAPI spec generation and consuming the generated TypeScript client, see the api-client-generation skill.

이 저장소의 다른 Skills

같은 저장소

chrome-devtools-mcp

MetalHexx/TeensyROM-Web

Visual UI verification workflow using Chrome DevTools MCP. Use when validating component rendering, CSS/styling changes, layout regressions, interactive UI behavior, screenshots, and post-change visual checks. Use this skill when the user is having trouble with styling or UI work or is trying to change the visual appearance of the app.

2026-08-016

make-skill-template

MetalHexx/TeensyROM-Web

Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders.

2026-08-016

backend-domain

MetalHexx/TeensyROM-Web

TeensyROM .NET backend domain knowledge — architecture, MediatR CQRS, serial protocol, storage systems, RadEndpoints, and testing patterns. Use when working on backend code, adding endpoints, modifying serial commands, updating storage/caching logic, writing backend tests, or understanding backend architecture. Covers .NET 9 API, pipeline behaviors, state machines, and multi-device orchestration.

2026-08-016

frontend-domain

MetalHexx/TeensyROM-Web

TeensyROM Angular 19 frontend domain knowledge — Clean Architecture, Nx monorepo, NgRx Signal Store, component patterns, testing standards, and coding conventions. Use when working on Angular components, stores, services, infrastructure, features, UI components, writing frontend tests, or understanding frontend architecture. Covers dependency injection, layer boundaries, ESLint enforcement, and modern Angular patterns.

2026-08-016

make-agent

MetalHexx/TeensyROM-Web

Create custom GitHub Copilot agents (.agent.md files) with interactive configuration. Use when asked to "create an agent", "make an agent", "new agent", "scaffold an agent", "build a custom agent", or when building specialized AI personas for VS Code. Guides users through every frontmatter option with ask_questions tool, then generates a complete .agent.md file.

2026-08-016

subagent-execute

MetalHexx/TeensyROM-Web

Executes a pre-planned subagent orchestration project by handing off tasks to specialized worker agents, monitoring reports, and adapting the plan. Use when asked to "execute a plan", "run subagents", "start execution", "hand off tasks", or when given a project name to execute against an existing docs/projects/<PROJECT-NAME>/ plan folder.

2026-08-016

name

backend-architecture

description

Backend Architecture Skill

When to Use This Skill

Working on the .NET API/backend (apps/api/src/TeensyRom.*)
Understanding endpoint structure (RadEndpoints) or adding new endpoints
Tracing the MediatR pipeline (LoggingBehavior, ExceptionBehavior, SerialBehavior) or command/handler flow
Understanding serial device communication (state machine, ACK/NAK protocol, reconnection logic)
Working with storage/indexing/caching (StorageService, StorageCache, favorites, metadata enrichment)
Investigating backend operational concerns: configuration, error handling, retries/timeouts, health checks, logging/observability
Reviewing architecture patterns to follow or anti-patterns to avoid in backend code

Overview

Core Responsibilities:

Device discovery, connection, and health monitoring over serial ports
Serial protocol command execution with state management and error recovery
Storage indexing/search/caching of device SD/USB contents
File launching (transfer + execute on Commodore 64 via TeensyROM cartridge)
Real-time log/event streaming to the frontend via SignalR
RESTful API surface via RadEndpoints with auto-generated OpenAPI specs

Full Reference

See references/BACKEND_ARCHITECTURE.md for the complete architecture document, including:

System architecture diagram and key components per layer (API, Device, Serial, Storage)
Endpoint organization, versioning/validation conventions, and a typical endpoint code example
Serial pipeline behaviors, command protocol (ACK/NAK), error handling/reconnection logic
MediatR sequence diagrams for serial commands and storage indexing
Storage/indexing deep dive: cache file structure, indexing strategies, read/write paths, metadata enrichment
Major dependencies and dependency flow between projects
Operational concerns: configuration, error handling layers, retries/timeouts, health checks, logging/observability
Architecture patterns to embrace and anti-patterns to avoid
Integration seams (frontend↔backend, backend↔hardware, storage↔serial)

For OpenAPI spec generation and consuming the generated TypeScript client, see the api-client-generation skill.