edit-docs

Wire DUI components into the docs dev server and update doc pages.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/deepfuturenow/dui --skill edit-docs-deepfuturenow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit-docs
Source: https://github.com/deepfuturenow/dui/tree/main/.agents/skills/edit-docs
Command: npx skills add https://github.com/deepfuturenow/dui --skill edit-docs-deepfuturenow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wire a DUI component or template into the DUI docs dev server, or modify existing doc pages, to streamline documentation workflow and reduce manual wiring steps.

Core Features & Use Cases

  • Wire components and templates into the docs site via side-effect imports.
  • Update routes, demos, and API tables without rewriting the docs pages.
  • Create or modify docs pages and demos to reflect new features or templates.

Quick Start

Open the DUI docs project and run the dev server to preview your documentation changes.

Frequently Asked Questions about edit-docs

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

FAQPage Schema
How do I wire a component into the docs dev server?

To wire a component into the docs dev server, you use side-effect imports to connect components or templates, validating the docs architecture and registry entries to ensure proper route rendering and consistent navigation.

What is the best way to update routes and demos without rewriting doc pages?

Updating routes, demos, and API tables without rewriting doc pages is achieved by wiring new components into the docs dev server through side-effect imports, which automatically modifies existing pages and generates accurate demo pages.

Can I use this approach to add new templates to my documentation site?

Yes, you can add new templates to your documentation site by applying this wiring process, which restructures the docs site, validates registry entries, and ensures accurate API table generation for the new templates.

Why does my documentation navigation break when adding new components?

Documentation navigation breaks when adding new components if the docs architecture or registry entries are not properly validated, so this wiring process validates route rendering and architecture to ensure consistent navigation.

Do I need a dev server to preview changes to documentation components?

Yes, you need the docs dev server running to preview your documentation changes, allowing you to verify that newly wired components, updated demos, and modified routes render accurately before deployment.