## What does this PR do? This PR adds https://vercel.com/blog/introducing-react-best-practices for your coding agent using `npx add-skill vercel-labs/agent-skills` command The skills are added to `.claude/`, `.cursor/`, and `.opencode/` directories to provide React and Next.js performance optimization guidance for AI-assisted workflows. ## Updates since last revision Addressed Cubic AI review feedback for issues with confidence >= 9/10: - **rerender-dependencies.md** - Replaced `console.log(user.id)` with `fetchUserDetails(user.id)` to avoid logging sensitive information - **server-after-nonblocking.md** - Removed `sessionCookie` from `logUserAction` call to avoid logging sensitive authentication data, added `await` to async call - **bundle-conditional.md** - Added `loadError` state and `setLoadError` setter to fix undefined `setEnabled` reference - **advanced-event-handler-refs.md** - Updated `useWindowEvent` handler signature to accept `Event` parameter and forward it to the stored handler - **rerender-derived-state.md** - Closed `<nav>` elements in both examples for valid JSX Fixes applied to both `.claude` and `.cursor` skill directories for consistency. ## Mandatory Tasks (DO NOT REMOVE) - [x] I have self-reviewed the code (A decent size PR without self-review might be rejected). - [x] N/A I have updated the developer docs in /docs if this PR makes changes that would require a [documentation change](https://cal.com/docs). If N/A, write N/A here and check the checkbox. - [x] N/A, I confirm automated tests are in place that prove my fix is effective or that my feature works. ## How should this be tested? These are documentation files for AI coding agents. No runtime testing required - review the markdown files to verify the example code snippets are correct. ## Checklist for human review - [ ] Verify example code snippets in the skill files are syntactically correct - [ ] Confirm the fixes don't introduce new issues in the documentation examples - [ ] Check that `.claude` and `.cursor` directories have consistent content --- Link to Devin run: https://app.devin.ai/sessions/f7f7e67fdeea4b22a4817d63ed9e1759 Requested by: unknown ()
40 lines
1.2 KiB
Markdown
40 lines
1.2 KiB
Markdown
---
|
|
name: web-design-guidelines
|
|
description: Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
|
|
argument-hint: <file-or-pattern>
|
|
metadata:
|
|
author: vercel
|
|
version: "1.0.0"
|
|
---
|
|
|
|
# Web Interface Guidelines
|
|
|
|
Review files for compliance with Web Interface Guidelines.
|
|
|
|
## How It Works
|
|
|
|
1. Fetch the latest guidelines from the source URL below
|
|
2. Read the specified files (or prompt user for files/pattern)
|
|
3. Check against all rules in the fetched guidelines
|
|
4. Output findings in the terse `file:line` format
|
|
|
|
## Guidelines Source
|
|
|
|
Fetch fresh guidelines before each review:
|
|
|
|
```
|
|
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
|
|
```
|
|
|
|
Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
|
|
|
|
## Usage
|
|
|
|
When a user provides a file or pattern argument:
|
|
1. Fetch guidelines from the source URL above
|
|
2. Read the specified files
|
|
3. Apply all rules from the fetched guidelines
|
|
4. Output findings using the format specified in the guidelines
|
|
|
|
If no files specified, ask the user which files to review.
|