Create admin and user guides with structured procedures and cross-links.
npx skills add https://github.com/fullsend-ai/fullsend --skill writing-user-docs
Please help me install this Agent Skill. Skill: writing-user-docs Source: https://github.com/fullsend-ai/fullsend/tree/main/skills/writing-user-docs Command: npx skills add https://github.com/fullsend-ai/fullsend --skill writing-user-docs
Administrators and developers often struggle to maintain consistent, accessible, and up-to-date user-facing documentation across repos. This skill provides a structured approach and rules to write clear docs that align with project standards.
Create a new admin guide under docs/guides/admin/install-fullsend.md following the defined structure.
High-intent search queries and answers about installing and using this skill.
To structure admin and user documentation consistently, organize guides under docs/guides/ with separate admin and user folders, enforcing a single audience per file with step-oriented procedures and inline links to architecture docs.
The best way to write installation guides is using step-oriented procedures that explicitly list prerequisites and cross-link to ADRs and architecture docs. This ensures developers have the necessary context and environment setup before proceeding.
You separate audiences by enforcing a single-audience per guide rule, creating distinct user-facing and admin-facing documents. This ensures administrators get configuration details while users receive workflow instructions tailored to their access level.
Yes, you can use a structured writing checklist to standardize developer handbooks in GitHub-hosted repos. The checklist enforces rules for prerequisites, step-based procedures, and cross-linking to architecture documentation.
You need to cross-link ADRs and architecture docs when writing configuration and workflow guides to provide decision context. This inline linking satisfies project standards by connecting procedural steps directly to architectural rationale.
A limitation of using predefined directory layouts for project documentation is the strict enforcement of a single-audience per guide and specific structural rules. Projects requiring highly customized documentation flows may find these standardized constraints too rigid.
vadimcomanescuGenerate Mermaid diagrams and ADR templates from project dependency analysis.
daishimanCreate advanced Markdown documentation with Mermaid diagrams, tables, and code blocks.
PedroGiudiceGenerate HTML technical documentation with syntax-highlighted code and SVG architecture diagrams.
ChegginGenerate API references, user guides, and changelogs from code and git history.
