ersatztv-knowledge

Explain ErsatzTV architecture and repository layout across Legacy and Next stacks.

Updated Aug 27, 2026

Search Tags:#architecture #debugging #documentation #knowledge #repo-layout #ersatztv #legacy-vs-next

Ready to run

npx skills add https://github.com/MeridianVega/claude-marketplace --skill ersatztv-knowledge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ersatztv-knowledge
Source: https://github.com/MeridianVega/claude-marketplace/tree/main/plugins/ersatztv-programmer/skills/knowledge
Command: npx skills add https://github.com/MeridianVega/claude-marketplace --skill ersatztv-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This knowledge skill provides a senior ErsatzTV engineer's mental model to answer questions about where components live, why issues occur, and how the Legacy and Next projects differ. It grounds discussions in sourced facts and project history.

Core Features & Use Cases

Establishes a two-stack reality (Legacy vs Next) and links to their repositories and scope.
Documents architectural conventions, file layout, and common debugging paths to reduce context-switching.
Guides how to reference upstream sources and migrate workflows using the CLAUDE.md and READMEs.

Quick Start

Ask for the exact location and lifecycle of a component in the ErsatzTV codebase, including differences between Legacy and Next, with sourced explanations.

Frequently Asked Questions about ersatztv-knowledge

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

FAQPage Schema

How does the ErsatzTV Legacy and Next bifurcation affect repository layout?▼

The ErsatzTV Legacy and Next bifurcation splits the codebase into two distinct stacks with separate repositories and scopes, dictating where components live on disk and how modules interact during debugging or migration.

How do I locate where a specific file lives in the ErsatzTV codebase?▼

To locate a file in the ErsatzTV codebase, reference the architectural conventions and repository layout documentation, which map component organization on disk and trace entry points using CLAUDE.md and upstream schemas.

What is the best way to debug ErsatzTV module interactions and entry points?▼

The best way to debug ErsatzTV module interactions is to follow documented common debugging paths that trace entry points and upstream references, ensuring accuracy by consulting CLAUDE.md and README files.

Do I need to reference CLAUDE.md to understand ErsatzTV architecture?▼

You need to reference CLAUDE.md and README files to understand ErsatzTV architecture because they provide sourced facts, project history, and upstream schemas that ensure traceability when locating components or migrating workflows.

How do I migrate workflows from ErsatzTV Legacy to Next?▼

To migrate workflows from ErsatzTV Legacy to Next, identify the architectural differences between the two stacks, then use CLAUDE.md and READMEs to guide component migration and module interactions across the bifurcated repositories.