wa:sync-context

Compile YAML-frontmatter-filtered markdown docs into domain-specific agent context files.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-sync-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:sync-context
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/sync-context
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-sync-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, error-prone process of gathering project documentation and turning it into structured context files that agents can reliably use.

Core Features & Use Cases

  • Documentation-to-Context Compilation: Reads YAML frontmatter from the local docs/ directory, filters by accepted status and matching type taxonomy, and compiles domain context outputs.
  • Domain-Specific Outputs: Produces core, API, feature, design, data, ADR, and LLM context files so agents get only the relevant knowledge.
  • Guardrails for Readiness and Scale: Verifies docs/ exists, logs individual parse failures without blocking overall sync, and summarizes content when pages exceed size thresholds.

Quick Start

Run the sync to compile all accepted documentation from your local docs/ into the agent context snapshots under .claude/context/project/.

Frequently Asked Questions about wa:sync-context

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

FAQPage Schema
How do I compile project documentation into agent context files?

To compile agent context files, this Skill reads markdown pages from a local docs/ directory, filters them by YAML frontmatter status and type taxonomy, and outputs domain-specific context snapshots for deterministic downstream execution.

What is YAML frontmatter taxonomy filtering for markdown processing?

YAML frontmatter taxonomy filtering is the mechanism of reading metadata headers in markdown files to selectively compile only accepted documents matching specific domain types into structured agent context.

Does compiling agent context require a specific directory structure?

Yes, compiling agent context requires a local docs/ directory containing markdown files with YAML frontmatter. The Skill verifies this directory exists before synchronizing domain-specific outputs into .claude/context/project/.

How do I handle large documentation pages when syncing agent context?

When syncing agent context, large documentation pages exceeding configured size thresholds are automatically summarized. This size-based summarization ensures domain context outputs remain manageable for downstream agent workflows.

What happens if YAML frontmatter parsing fails during context synchronization?

If YAML frontmatter parsing fails during context synchronization, the Skill applies safe error handling by logging individual parse failures without blocking the overall sync process for remaining valid documents.

What types of domain-specific context files does this documentation compilation produce?

Documentation compilation produces domain-specific context files for core, API, feature, design, data, ADR, and LLM domains, ensuring agents receive only the relevant knowledge required for their specific tasks.