docs

Regenerate README.md, APP_STORE_DESCRIPTION.txt, and static/index.html from current features.

105|10|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/everpcpc/KMReader --skill docs-everpcpc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/everpcpc/KMReader/tree/main/.agents/skills/docs
Command: npx skills add https://github.com/everpcpc/KMReader --skill docs-everpcpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate project-facing documentation by aligning core files with current features.

Core Features & Use Cases

  • Regenerate README.md, APP_STORE_DESCRIPTION.txt, and static/index.html from current codebase features.
  • Align product messaging for marketing, onboarding, and developer communications.
  • Use case: after major feature updates, regenerate docs to reflect new capabilities and reflect them across public and internal docs.

Quick Start

Invoke the docs skill to regenerate the target files from the latest product features.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I regenerate README and app store descriptions after major feature updates?

You can regenerate project documentation by aligning core files like README.md and APP_STORE_DESCRIPTION.txt with current product features. This ensures marketing and developer communications reflect the latest codebase capabilities after major updates.

What is the best way to keep landing page documentation in sync with code?

Keeping landing page documentation in sync involves regenerating static/index.html to reflect current codebase features. This updates your landing page to accurately represent the latest product capabilities for onboarding and marketing.

Can I use automation to update developer onboarding docs from current features?

Yes, you can use automation to regenerate developer onboarding docs by extracting current product features. This automatically updates README.md and static/index.html to align external messaging with the latest codebase.

Does this documentation regeneration process work without external dependencies?

Documentation regeneration works without external dependencies to update README.md, APP_STORE_DESCRIPTION.txt, and static/index.html. It directly aligns product messaging for marketing and developer communications using current codebase features.

When do I need to regenerate project-facing documentation?

You need to regenerate project-facing documentation after major feature updates to reflect new capabilities. This ensures README.md, APP_STORE_DESCRIPTION.txt, and static/index.html accurately represent current product features for marketing and onboarding.