document-features

Regenerates public feature documentation and screenshots from source code and a running app build.

96|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/devthrottle --skill document-features-thefrederiksen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-features
Source: https://github.com/thefrederiksen/devthrottle/tree/main/.claude/skills/document-features
Command: npx skills add https://github.com/thefrederiksen/devthrottle --skill document-features-thefrederiksen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Public feature documentation drifts out of sync with the actual application as the UI evolves, and screenshots become stale. This Skill keeps docs/public/features/ accurate by deriving the feature inventory from source code, capturing fresh screenshots from a real build, and regenerating the published pages together. ## Core Features & Use Cases - Inventory reconciliation: Scans the Avalonia desktop source and phone client pages to add, remove, or reclassify features in feature-inventory.yaml based on what is actually implemented. - Automated screenshot capture: Runs a PowerShell harness that builds a throwaway slot, launches the app, creates dummy sessions, and captures occlusion-proof screenshots via Win32 PrintWindow. - Page and manifest regeneration: Rewrites the feature pages, rebuilds the overview feature matrix, and validates docs/public/index.json so every page is listed. - Use Case: After a UI change lands before a release, run the skill to refresh every feature page and screenshot in one pass instead of hand-editing markdown and retaking screenshots manually. ## Quick Start Ask the agent to run /document-features to regenerate the feature documentation and screenshots after the latest UI changes.

Frequently Asked Questions about document-features

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

FAQPage Schema
How do I keep feature documentation in sync with my app?▼

Run the document-features skill, which reconciles a YAML feature inventory against the UI source, captures fresh screenshots from a real build, and regenerates the published markdown pages and manifest in one pass.

How to automate screenshots of a Windows desktop app for docs?▼

The capture harness builds a throwaway slot, launches the app via a scheduled task, creates dummy sessions, and captures each screen with cc-click screenshot using Win32 PrintWindow, which grabs only the app's own window pixels.

Why are modal dialog screenshots missing from the capture run?▼

Modal dialogs like New Session and Settings only render when the app can be foregrounded. Run the harness from an interactive desktop session; background or non-interactive runs report those shots as missing.

Can the screenshot capture run without spending a Claude subscription?▼

Yes. The default dummy sessions use plain shells with -Agent RawCli, so no Claude subscription is consumed. Pass -Agent ClaudeCode only when real agent output is needed for the wingman or voice screens.

Does the docs drift check run in CI?▼

The docs-drift.yml workflow runs only the inventory reconcile step on pull requests and flags stale entries. It cannot screenshot a desktop GUI on a headless runner, so a human must re-run the full local pass.