Skip to content

Conversation

@rickhanlonii
Copy link
Member

Overview

Adds more claude stuff.

I iterated on this throughout the useOptimistic, useEffectEvent and useActionState doc revamps.

To create/update these, I had claude comb through the existing docs more throughly to create exhastive rules in each section, then i had it go over them with the skills superpower to consolidate the repetition into the right skills (e.g. voice things in the docs-voice skill). Rinse and repeat until it was working pretty well.

Then I had it run a verification plan where it would create some sham docs, and then run the /docs-reviewer on them, iteratively improving the skills for thing that the skills, or reviewer agent missed.

Finally, I had it do the useEffectEvent docs, and then edited them by hand to do an editorial pass, then had claude review the diff and update the skills needed to write it with my edits. I'll probably do that more in the future PRs and just land the claude files in each PR iteratively.

SKILL Improvements

  • [new] docs-voice skill that consolidates and expands on the brand voice rules
  • [new] docs-writer-blog skill for writing blog posts
  • [updated] docs-writer-learn: expanded
  • [updated] docs-writer-reference: expanded a ton
  • [updated] docs-writer-components: expanded with all components
  • [updated] docs-writer-sandpack: expanded with thing i found it missed

New /review-docs skill

The docs-reviewer agent was completely redone. Now there's a /review-docs skill that spawns a docs-reviewer agent for each skill (docs-components, docs-sandpack, etc). The reviewer agent creates a task list of things to review for that skill, and then reviews the the changes for conformance:

Screenshot 2026-01-29 at 11 36 30 PM

That gives an output of feedback at the end like this:

Screenshot 2026-01-29 at 11 40 59 PM

New /react-expert agent

Adds a /react-expert agent that understands concepts/APIs from the react repo using:

  • react tests
  • react PR descriptions / comments
  • git commit history and messages
  • issues referencing the API
  • typescript / flow types

This thing is nuts, but really useful.

Workflow for editing docs

This prompt worked really well for useEffectEvent:

/superpowers:write-plan I want to rewrite the useActionState docs. Can you create a plan that will first use the /react-expert agent to understand the api, then take that research and create a task list for the use the docs-writer-reference skill write the new docs, and finally iterate with the /review-docs skill a minimum of 10 times to iterate on feedback?

Here's the plan it ran
And this commit was the output.

@github-actions
Copy link

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

You can also create an event to fire from any Effect hook using:
- [`useEffectEvent`](/reference/react/useEffectEvent) lets you extract non-reactive logic from Effects into reusable functions.
Copy link
Member Author

Choose a reason for hiding this comment

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

Oops i'll remove this, it should be in #8279

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant