/design-docs:user-docs-create-docs

To scaffold documentation for a new software project, this skill automatically generates a standardized directory structure containing a README, getting-started guide, API reference, and troubleshooting files. It operates directly on your target project directories to ensure consistent architecture.

The best way to structure technical writing for developer onboarding is using a standardized, numbered naming convention. This approach organizes getting-started guides and API references logically, ensuring every project starts with a professional, user-friendly documentation foundation.

Yes, you can automatically update your main README to link new project docs. The scaffolding process integrates project-specific context, pulling in your table of contents and updating the root README to connect the newly generated documentation suite.

Generating a standardized docs folder requires integration with user-docs subagents to generate content and update project-level documentation links. The skill creates the initial file structure, while these subagents handle populating the actual technical writing.

When scaffolding project documentation, the generated files include a README, a getting-started guide, an API reference, and a troubleshooting page. This standardized suite eliminates manual setup overhead and enforces a consistent, navigable architecture.