Write Laravel-style documentation for docs and README files.
npx skills add https://github.com/loadinglucian/dotagents --skill docs-loadinglucian
Please help me install this Agent Skill. Skill: docs Source: https://github.com/loadinglucian/dotagents/tree/main/skills/docs Command: npx skills add https://github.com/loadinglucian/dotagents --skill docs-loadinglucian
Writes consistent, high-quality Laravel-style documentation that emphasizes reader-first explanations, active voice, and a clear progression from basic to advanced concepts. It is designed for editing docs/**/*.md and README.md files across Laravel projects.
Create a Laravel-style documentation draft for a new feature in docs/ or README.md following the reader-first, problem-solution structure.
High-intent search queries and answers about installing and using this skill.
To write Laravel-style documentation, you should apply a reader-first tone using active voice and problem-solution openings. This approach ensures a clear progression from basic to advanced concepts across your docs and README files.
The best way to structure a Laravel feature guide is using a standardized format with problem-solution openings, conceptual explanations, and progressive detail, ensuring a consistent and accessible output for your readers.
To create a tutorial draft, write content in your docs directory following the reader-first, problem-solution structure while enforcing an active-voice tone across all sections to maintain high-quality documentation.
Yes, you can use this approach to standardize API guides and feature retrospectives by applying standardized structure and reader-first explanations to ensure consistent, accessible output across all documentation tasks.
Frontmatter-driven guidance affects markdown documentation by meeting specific tone-structure requirements that ensure consistent output, applying reader-first explanations and active voice across all documented sections.
You should not use a reader-first active-voice tone when your documentation requires strict passive-voice compliance or highly formalized structural conventions that conflict with progressive, problem-solution formatting.
saffron-healthGenerate phased specification documents from code and documentation analysis.
JongsixGenerate technical documentation from source code and API definitions.
clover-stormDetect code changes from git diffs and update corresponding documentation sections.
ZenkakuHiraganaDraft and refine long-form technical documents with artifact-specific checks.
