aif-docs

Generate a landing README and topic-specific docs with navigation and cross-links.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ichinya/idshka --skill aif-docs-ichinya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-docs
Source: https://github.com/ichinya/idshka/tree/main/.codex/skills/aif-docs
Command: npx skills add https://github.com/ichinya/idshka --skill aif-docs-ichinya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The tool helps teams generate and maintain consistent project documentation by creating a lean landing README plus topic-specific docs in a configured docs directory.

Core Features & Use Cases

  • Generate a landing page README that links to structured docs sections
  • Split, reorganize, and update docs without losing content
  • Maintain navigation, See Also sections, and cross-links across pages

Quick Start

Create a landing README and topic-dedicated docs in the configured docs directory.

Frequently Asked Questions about aif-docs

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

FAQPage Schema
How do I automate project documentation generation from my codebase?

Automate project documentation by analyzing the codebase to generate a landing README alongside topic-specific docs pages, complete with structured directories and consistent navigation.

What is the best way to split a large README into topic-specific markdown docs?

Splitting a large README into topic-specific docs is handled by reorganizing content into a configured docs directory without losing data, while maintaining cross-links and See Also sections.

Can I automatically update navigation and cross-links when documentation changes?

Navigation and cross-links update automatically during documentation generation, enforcing consistent Markdown templates and See Also sections across all pages when content is split or modified.

Do I need to manually create a docs directory before generating landing page documentation?

Manual creation of a docs directory is unnecessary, as the documentation automation process produces the required directories, generates the landing README, and updates AGENTS.md directly.

How does codebase analysis work for generating markdown documentation templates?

Codebase analysis for markdown documentation works by scanning the project structure to automatically create relevant topic pages, enforce consistent navigation, and establish cross-links throughout the docs.