reference-map

Route legacy guidance to correct skill and reference documents in the AniTrend repo.

51|6|Updated Mar 10, 2019
One-click install
npx skills add https://github.com/AniTrend/anitrend-v2 --skill reference-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reference-map
Source: https://github.com/AniTrend/anitrend-v2/tree/main/.agents/skills/reference-map
Command: npx skills add https://github.com/AniTrend/anitrend-v2 --skill reference-map

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates confusion and documentation drift by providing a single, repo-local navigation map from legacy monolithic guidance to the correct split instruction and skill files.

Core Features & Use Cases

  • Instruction-to-skill routing: Quickly determines which skill should be used for a given implementation topic.
  • Stable cross-layer anchors: Points to a canonical example inventory so teams can reuse consistent, non-brittle references across modules and layers.
  • Validation-first workflow: Encourages running the repo audit script to confirm references and formatting before proposing changes.

Quick Start

Use reference-map to locate the primary instruction and the exact skill file for your topic, then follow its pointers to the layer-example-matrix reference inventory.

Frequently Asked Questions about reference-map

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

FAQPage Schema
How do I route legacy documentation to the correct skill files?

Route legacy documentation to the correct skill files by using a repo-local navigation map that points from monolithic guidance to the exact split instruction and reference documents for your topic.

What is the best way to prevent brittle SHA-pinned links during documentation migrations?

Prevent brittle SHA-pinned links during documentation migrations by using repo-relative paths and running the audit script to verify instruction references before proposing changes.

How do I find the right skill for an Android architecture deep dive across multiple modules?

Find the right skill for an Android architecture deep dive by using instruction-to-skill routing to quickly determine which skill applies to implementation topics across app, feature, common, domain, and data layers.

Can I use reference anchors for cross-layer implementation planning in the AniTrend repo?

Use reference anchors for cross-layer implementation planning by pointing to a canonical example inventory, allowing teams to reuse consistent, non-brittle references across modules and buildSrc layers.

Do I need to run an audit script before proposing changes to instruction references?

Run the audit script before proposing changes to instruction references to confirm references and formatting, which prevents documentation drift and verifies that all anchors remain valid.