MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-04-26 13:04:49 -07:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Update docs skill for links

Browse Source
This commit is contained in:
Jenna Inouye
2026-03-06 13:36:41 -08:00
parent 7d31d5f4ec
commit e721dc65b9
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gemini/skills/docs-writer/SKILL.md
+9 -3
View File
@@ -65,13 +65,20 @@ accessible.
- **UI and code:** Use **bold** for UI elements and `code font` for filenames, - **UI and code:** Use **bold** for UI elements and `code font` for filenames,
snippets, commands, and API elements. Focus on the task when discussing snippets, commands, and API elements. Focus on the task when discussing
interaction. interaction.
- **Links:** Use descriptive anchor text; avoid "click here." Ensure the link
makes sense out of context.
- **Accessibility:** Use semantic HTML elements correctly (headings, lists, - **Accessibility:** Use semantic HTML elements correctly (headings, lists,
tables). tables).
- **Media:** Use lowercase hyphenated filenames. Provide descriptive alt text - **Media:** Use lowercase hyphenated filenames. Provide descriptive alt text
for all images. for all images.
### Links
- **Accessibility:** Use descriptive anchor text; avoid "click here."Ensure the
link makes sense out of context, such as when being read by a screen reader.
- **Use relative links in docs:** Use relative links in documentation to
ensure portability; avoid absolute URLs for links within the same repository. Do not
include the /docs/ section of a link.
- **When changing headings, check for deep links:** If a user is changing a heading,
check for deep links to that heading in other pages, and update accordingly.
### Structure ### Structure
- **BLUF:** Start with an introduction explaining what to expect. - **BLUF:** Start with an introduction explaining what to expect.
- **Experimental features:** If a feature is clearly noted as experimental, - **Experimental features:** If a feature is clearly noted as experimental,
@@ -126,7 +133,6 @@ documentation.
- **Consistency:** Check for consistent terminology and style across all edited - **Consistency:** Check for consistent terminology and style across all edited
documents. documents.
## Phase 4: Verification and finalization ## Phase 4: Verification and finalization
Perform a final quality check to ensure that all changes are correctly formatted Perform a final quality check to ensure that all changes are correctly formatted
and that all links are functional. and that all links are functional.