shard-document

Split documents into metadata-rich shards with cross-reference preservation and index generation.

1|Updated Oct 19, 2025

Search Tags:#validation #navigation #metadata #index #document #shard

Ready to run

npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill shard-document-acidicsoil

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shard-document
Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/shard-document
Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill shard-document-acidicsoil

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Break large, unwieldy documents into smaller, self-contained shards while preserving relationships and navigation, making PRDs, specs, and technical docs easier to maintain.

Core Features & Use Cases

Logical sharding by topic/section to preserve meaning
Metadata-rich shards with navigation anchors and cross-references
Automatic index generation and validation to ensure discoverability
Use Case: large product specs can be split into per-feature shards with a central index

Quick Start

Shard the source document into a navigable shard set and generate a master index

Frequently Asked Questions about shard-document

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

FAQPage Schema

How do I split large technical documents into smaller navigable files?▼

To split large technical documents into navigable files, apply logical, size-based, or hierarchical sharding by topic. This process creates self-contained shards with metadata, preserving cross-references and generating a central index for discovery.

What's the best way to maintain cross-references when breaking down a product spec?▼

The best way to maintain cross-references when breaking down a product spec is to generate metadata-rich shards with navigation anchors. The process automatically validates links and dependencies to ensure structural integrity across the divided document set.

When do I need to shard a document?▼

You need to shard a document when maintaining large, unwieldy files like PRDs or technical specs becomes difficult. Sharding divides them into smaller, self-contained sections by topic, making them easier to manage while preserving their relational meaning.

How do I generate an index for sharded document sets?▼

To generate an index for sharded document sets, apply a sharding strategy to the source file and produce a master index. This index documents the output structure, ensuring discoverability and reuse of the individual shards.

Does document sharding work with hierarchical document structures?▼

Yes, document sharding works with hierarchical structures by applying hierarchical sharding based on the document's native sections. It preserves the original meaning and relationships while creating metadata-rich files and validating all resulting dependencies.

What are the limitations of sharding a document by size?▼

When sharding a document by size, the limitation is that purely size-based splits might disrupt logical topic boundaries. To mitigate this, the process applies logical or hierarchical sharding as appropriate, validating links to ensure no meaning is lost.