information-architecture

Validate documentation folder order, index.md files, and markdown links.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lc0rp/luke-agent-scripts --skill information-architecture-lc0rp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: information-architecture
Source: https://github.com/lc0rp/luke-agent-scripts/tree/main/parked-skills/information-architecture
Command: npx skills add https://github.com/lc0rp/luke-agent-scripts --skill information-architecture-lc0rp

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Information Architecture (IA) skill keeps project documentation aligned with a fixed, serial folder structure and ensures reliable cross-links by validating folder order, index.md content, and README references.

Core Features & Use Cases

  • Canonical structure validation: enforces the 00-foundation to 99-archive layout and required index.md presence.
  • Link discipline: validates markdown links and wiki-like references to avoid broken or ambiguous links.
  • Change governance: supports PR reviews, migrations, and documentation hygiene by guiding updates to be consistent with the IA guidelines.
  • Use Case: during documentation changes or PR reviews, it ensures the docs remain navigable and correctly indexed.

Quick Start

Run the IA validation workflow to verify the canonical folder order, index.md structure, and link validity.

Frequently Asked Questions about information-architecture

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

FAQPage Schema
How do I validate project documentation structure and folder ordering?

Validate project documentation structure by enforcing a canonical 00-foundation to 09-user-docs and 99-archive folder layout, ensuring correct ordering, required index.md files, and valid cross-links. Run the included validation scripts to lint the IA structure.

How do I check markdown links and prevent broken or ambiguous cross-references in docs?

Check markdown links by running link validation scripts that enforce proper relative paths, disallow wikilinks, and verify correct README references. This ensures documentation cross-links remain navigable and avoids ambiguous references.

What is the canonical folder structure for documentation and when do I need to enforce it?

The canonical documentation structure uses serial folders from 00-foundation to 09-user-docs plus 99-archive, each requiring an index.md. Enforce it during documentation work, PR reviews, and migrations to maintain consistent folder ordering and indexing.

Can I use this IA validation for documentation migrations and PR reviews?

Yes, the IA validation supports PR reviews, migrations, and documentation hygiene by verifying folder order, per-folder index headings, and link validity. It guides updates to remain consistent with IA guidelines during structural changes.

Why are wikilinks not allowed and what link format should documentation use instead?

Wikilinks are disallowed because they create ambiguous references; documentation must use proper relative paths and correct README references instead. The link validation scripts enforce these rules to prevent broken cross-links.

What does an information architecture lint check cover for markdown documentation?

An information architecture lint check covers canonical folder order validation, index.md presence and headings, relative path link validation, and README reference correctness. It provides scripts to lint both IA structure and links during documentation changes.