update-waystone-inventory

Update waystone inventory JSON by comparing Svelte code usage.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill update-waystone-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-waystone-inventory
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/update-waystone-inventory
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill update-waystone-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill ensures that the documentation for contextual help markers (waystones) accurately reflects their usage in the codebase, preventing outdated or missing help information.

Core Features & Use Cases

  • Inventory Auditing: Compares actual waystone component usage in Svelte files against a central inventory JSON file.
  • Discrepancy Identification: Highlights new, removed, or changed waystone instances.
  • Use Case: After a code review flags an inventory mismatch, or when adding new waystones, run this skill to automatically update the .github/waystone-inventory.json file to match the current state of the codebase.

Quick Start

Run the update-waystone-inventory skill to synchronize the waystone documentation with the latest code changes.

Frequently Asked Questions about update-waystone-inventory

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

FAQPage Schema
How do I sync Svelte component usage with a JSON documentation file?

To sync Svelte component usage with a JSON file, run an inventory audit that compares actual waystone instances against `.github/waystone-inventory.json`, automatically generating additions, removals, and metadata changes.

What is the best way to detect documentation drift for UI help elements in CI?

Detecting documentation drift for UI help elements in CI involves comparing code usage against a central inventory JSON file, flagging mismatches when new, removed, or changed waystone instances diverge from the stored metadata.

How do I update contextual help markers after modifying Svelte files?

Updating contextual help markers after modifying Svelte files requires comparing the current codebase against the inventory JSON, then applying additions, removals, and metadata changes to ensure documentation accuracy.

Does the waystone inventory auditor work outside of Svelte projects?

The waystone inventory auditor is designed specifically for Svelte projects, parsing Svelte files to identify waystone component instances and compare them against the central JSON inventory.

Why are my waystone documentation checks failing during code review?

Waystone documentation checks fail during code review when actual component usage in Svelte files diverges from the central inventory JSON, indicating outdated, missing, or changed metadata for UI help elements.

Can I manually edit the waystone inventory JSON instead of using an automated sync?

While you can manually edit the waystone inventory JSON, automated syncing prevents outdated or missing help information by directly comparing code usage and applying precise metadata changes without human error.