skills.rest
eboody
eboodyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mds-repo-docs-index

...

Updated Jan 6, 2026
Search Tags:#documentation#policy#code-audit#axum#maud#datastar#bon
One-click install
npx skills add https://github.com/eboody/eran.codes --skill mds-repo-docs-index
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mds-repo-docs-index
Source: https://github.com/eboody/eran.codes/tree/main/.codex/skills/mds-repo-docs-index
Command: npx skills add https://github.com/eboody/eran.codes --skill mds-repo-docs-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes a definitive, docs-first retrieval policy for the repository, ensuring that documentation within the /docs directory serves as the single source of truth for various technical domains.

Core Features & Use Cases

  • Policy Enforcement: Enforces a docs-first approach for Maud, Datastar, Axum, Bon, Statum, and CSS conventions.
  • Conflict Resolution: Provides clear rules for handling conflicting documentation and prioritizes the most specific or authoritative sources.
  • Curated Lookup: Maintains an allowlist and denylist of authoritative documentation roots, guiding retrieval and preventing the use of stale or irrelevant information.
  • Use Case: When developing a new feature related to Datastar, this Skill ensures that all design decisions and implementation details are aligned with the latest guidelines found in /docs/datastar/.

Quick Start

Use the mds-repo-docs-index skill to find the authoritative documentation for Datastar route mapping.

Frequently Asked Questions about mds-repo-docs-index

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

FAQPage Schema
How do I enforce a docs-first retrieval policy for Axum and Datastar development?▼

Enforce a docs-first retrieval policy by prioritizing the `/docs` directory as the source of truth for Axum and Datastar. This ensures design decisions and implementations align with curated, authoritative documentation roots.

What is a documentation allowlist and how does it resolve code audit conflicts?▼

A documentation allowlist defines authoritative doc roots for code audits, while a denylist blocks stale information. Conflicts are resolved by prioritizing the most specific or authoritative sources mapped within the `/docs` directory.

How do I extract concrete constraints from Maud and Bon documentation areas?▼

Extract concrete constraints for Maud and Bon by classifying requests into specific technical areas. This lookup protocol retrieves relevant rules from mapped documentation areas and attaches them directly to your working context.

Does this repository documentation index cover CSS conventions and Statum?▼

Yes, the repository documentation index covers CSS conventions and Statum. It establishes a definitive retrieval policy treating the `/docs` directory as the authoritative source for these specific technical domains.

What are the limitations of using a curated docs index for policy enforcement?▼

The limitation of a curated docs index is that it restricts retrieval to predefined allowlists and denylists. If documentation is not mapped within the specified `/docs` directory areas, it will not be retrieved for policy enforcement.

Related Skills

Explore More Software Engineering Skills→
eboodyeboody

mds-bon-patterns

Enforce repository-standard `bon` builder usage patterns for optional members and conditional building.

Community
Intermediate
adriannoesadriannoes
46

technical-diagram-analyzer

Analyze and validate technical diagrams for standards compliance.

Community
Intermediate
zzafergokzzafergok
1

markdown-to-html-skill

Convert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.

Community
Intermediate
oborchersoborchers
28

abbreviation-policy

Enforce consistent abbreviation usage across codebases during code review.

Community
Intermediate