Generate a landing README and structured docs/ directory with navigation and audits.
npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-docs-artemyurov
Please help me install this Agent Skill. Skill: aif-docs Source: https://github.com/ArtemYurov/TomoBar/tree/main/.claude/skills/aif-docs Command: npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-docs-artemyurov
Documentation is often scattered, hard to discover, and hard to maintain; this Skill provides a streamlined approach to generate a lean landing page README and a structured docs/ directory split by topic, keeping documentation current with minimal manual overhead.
Ask me to generate or update your project docs and I will create a landing-page README plus topic-based docs with navigation.
High-intent search queries and answers about installing and using this skill.
Generate project documentation by creating a concise landing-page README alongside a structured docs/ directory split by topic. This approach enforces navigational structure and See Also sections, keeping documentation current with minimal manual overhead.
Maintain scalable documentation using automated auditing and REVIEW-CHECKLISTS to keep docs in sync with code. This approach enforces navigational structure and topic-based pages, reducing manual overhead for software projects.
Yes, you can organize installation guides, architecture details, and API references into separate topic-based pages within a structured docs/ directory. This enforces navigational structure and See Also sections for scalable documentation.
A lean landing-page README improves discoverability by serving as a concise entry-point with essential project info, linking to a structured docs/ directory. This enforces navigational structure and reduces scattered documentation overhead.
Yes, this documentation approach works for software projects requiring configuration topic pages. It generates a structured docs/ tree covering configuration, API references, and architecture with enforced navigational structure and automated audits.
Project documentation becomes scattered and hard to maintain without a structured docs/ directory and navigational enforcement. Using a lean landing-page README with topic-based pages and REVIEW-CHECKLISTS keeps documentation current and discoverable.
Svarog83Generate and maintain project documentation with YAML frontmatter and HTML rendering.
brainbrewlabsPublishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.
williamzujkowskiMitigate SQL security vulnerabilities across PostgreSQL, MySQL, and SQLite configurations.
zzafergokConvert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.
