Skip to content

Experimental claude skills for docs updates#10473

Draft
gitKrystan wants to merge 7 commits intomainfrom
claude-skills
Draft

Experimental claude skills for docs updates#10473
gitKrystan wants to merge 7 commits intomainfrom
claude-skills

Conversation

@gitKrystan
Copy link
Copy Markdown
Contributor

@gitKrystan gitKrystan commented Feb 16, 2026

The idea here is to create skills to make it easier to draft API Docs and Guides w/ AI for a hu-mon to manually edit. I am hoping this can help us to get docs up quicker.

Sample convo:

image image image

gitKrystan and others added 6 commits February 15, 2026 19:07
Refactor .claude/skills to follow Claude Code best practices by
consolidating 7 separate documentation skills into a single
updating-warp-drive-docs skill with progressive disclosure.

Changes:
- Consolidate 7 skills (1,705 lines) into 1 lean skill (238 lines)
- Create 6 comprehensive reference files (4,232 total lines)
- Organize 11 example files by documentation type
- Apply imperative/infinitive writing style throughout
- Add comprehensive trigger phrases for better discovery
- Merge TypeDoc and VitePress expertise into single references

Benefits:
- Single entry point for all documentation work
- Better token efficiency (238 vs 400+ lines loaded initially)
- Progressive disclosure: load detailed expertise only when needed
- Clearer user experience with one obvious skill
- Easier maintenance with centralized coordination

Structure:
- SKILL.md: 238 lines (lean entry point with decision tree)
- references/: 6 files with detailed expertise
  - tech-writing.md (166 lines)
  - api-docs.md (418 lines)
  - guides.md (562 lines)
  - readmes.md (801 lines)
  - typedoc.md (1,030 lines, merged from 2 sources)
  - vitepress.md (1,255 lines, merged from 2 sources)
- examples/: 11 files organized by type
  - api-docs/ (1 file)
  - guides/ (5 files)
  - readmes/ (3 files)
  - typedoc/ (1 file)
  - vitepress/ (1 file)

Removed skills:
- tech-writer-expert
- typedoc-expert
- vitepress-expert
- warp-drive-update-docs
- warp-drive-update-api-docs
- warp-drive-update-guides
- warp-drive-update-readmes

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Improve skill triggering by adding "document the API" as an
explicit trigger phrase. Also adjust overview wording for clarity.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
const store = new Store();

// Use the store
const user = store.findRecord('user', '1');
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UGH FML

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: Tell it not to document deprecated/legacy features under "Quick Start" and "Key Concepts"

@@ -0,0 +1,436 @@
# @warp-drive/core
Copy link
Copy Markdown
Contributor Author

@gitKrystan gitKrystan Feb 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is generated by claude using the skill above + no edits from me.

Using this to validate the skill. We shouldn't merge w/o full vetting.

@gitKrystan gitKrystan changed the title Experimental claude skills for docs updates that claude refuses to actually use unless I bully it (him?) Experimental claude skills for docs updates Feb 16, 2026
});
```

## API Overview
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FIXME: Tell it not to do this since TSDoc already does this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant