Verified:GitHub

architecture-reference

Document Shadow Master subsystem file locations, interfaces, and integration touchpoints.

1|1|Updated Nov 14, 2025

Search Tags:#architecture #documentation #reference #software-engineering #architecture-analysis #subsystems #Shadow Master

Ready to run

npx skills add https://github.com/Jasrags/ShadowMaster --skill architecture-reference-jasrags

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-reference
Source: https://github.com/Jasrags/ShadowMaster/tree/main/.claude/skills/architecture-reference
Command: npx skills add https://github.com/Jasrags/ShadowMaster --skill architecture-reference-jasrags

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a centralized, curated architecture reference for Shadow Master subsystems, helping developers quickly locate sources, interfaces, and responsibilities across Combat, Matrix, Rigging, Inventory, Contacts, Sync, and Security.

Core Features & Use Cases

Subsystem map: overview of major subsystems and their interactions.
File-location index: lists critical files and directories for quick navigation.
Usage guidance: recommended workflows for debugging, onboarding, and cross-team collaboration.

Quick Start

Use the architecture-reference skill to locate the source file for CombatSessionContext.tsx or to understand how matrix overwatch interacts with program management.

Frequently Asked Questions about architecture-reference

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

FAQPage Schema

How do I locate source files for Shadow Master subsystems like Combat and Matrix?▼

Architecture reference provides a centralized file-location index to quickly locate source files, interfaces, and responsibilities across Shadow Master subsystems like Combat and Matrix. It maps critical files and directories for fast navigation.

What is the best way to understand integration touchpoints between Rigging and Inventory?▼

The architecture reference details integration touchpoints and interfaces across subsystems like Rigging and Inventory. It provides a subsystem map overview showing interactions, file locations, and workflow guidelines for cross-team collaboration.

Can I use the architecture reference for onboarding new developers to Sync and Security workflows?▼

Yes, the architecture reference offers usage guidance and recommended workflows specifically designed for debugging, onboarding, and cross-team collaboration across Sync, Security, and other major subsystems.

Do I need a YAML frontmatter to set up the architecture reference documentation?▼

Yes, setting up the architecture reference requires a SKILL.md file with YAML frontmatter containing name and description fields, plus a populated references section describing critical files, workflows, and usage guidelines.

How does the architecture reference help with QA across Contacts and other subsystems?▼

The architecture reference supports QA by detailing file locations, interfaces, and integration touchpoints across Contacts and all major subsystems, enabling testers to quickly locate sources and understand subsystem interactions.