improve vercel-react-best-practices skill structure + add skill-review-and-optimize CI - #6
Open
fernandezbaptiste wants to merge 1 commit into
Conversation
…mize CI - expand description with concrete actions + performance-specific trigger terms - add workflow section with priority ordering and verification steps - add inline code examples for highest-impact patterns (Promise.all, barrel imports) - add .github/workflows/skill-review.yml for automated skill review + optimize on PRs - add .github/workflows/skill-apply-optimize.yml for /apply-optimize command
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
hey @jarrodwatts, thanks for sharing your Claude Code config. really like how you've structured the vercel best practices as prioritized rules with individual reference files. Kudos on soon hitting
1kstars! I've just starred it.ran your vercel-react-best-practices skill through agent evals and spotted a few quick wins that took it from
~77%to~86%performance:expanded description with concrete actions like code splitting, lazy loading, parallel data fetching + performance-specific trigger terms like slow page loads, Core Web Vitals, bundle size so agents can match it reliably
added a workflow section with priority ordering + verification steps (
next build, Lighthouse)added inline code examples for the
2highest-impact patterns (Promise.all parallel fetching + barrel import avoidance)also added a GitHub Action (
skill-review.yml) that freely reviews any skill.md changed in a PR. review mode works out of the box with no auth and posts a score comment.these were easy changes to bring the skill in line with what performs well against Anthropic's best practices. honest disclosure, I work at tessl.io where we build tooling around this. not a pitch, just fixes that were straightforward to make!
optionally, you can enable optimize mode by adding a token as
TESSL_API_TOKENin your repo secrets. when enabled, the action suggests improvements you can accept by commenting/apply-optimize.this means that it gives you and your contributors an instant quality signal before you have to review yourself.
happy to answer any questions on the changes.