react-anti-patterns — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited react-anti-patterns (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Inject React anti-patterns and performance pitfalls into existing React apps while keeping them functional, so teams can practice identifying and fixing issues.
--comments: Add inline comments identifying the anti-pattern--comments-hint: Add comments with a hint on how to fix--comments-fix: Add comments with full fix explanation--specific <category>: Target specific category only (e.g., --specific rerender)React: rerender, state, effect, list, conditional, data
Next.js: waterfall, bundle, boundary, actions, rsc
Check if project is Next.js:
next.config.js, next.config.mjs, or next.config.tspackage.json for next dependencyIf Next.js detected, ask user:
"This is a Next.js project. Include Next.js-specific anti-patterns in addition to React patterns?"
If not specified in invocation, ask user:
Amount (default: medium): "How many anti-patterns should I introduce?"
Level (default: mixed): "What experience level should patterns target?"
Comments (default: none): "Should I add comments explaining the anti-patterns?"
--comments: identify only--comments-hint: with hints--comments-fix: with full fixesBased on selections, load relevant reference files:
references/anti-patterns-index.md # Always load for pattern selection
references/react/junior.md # If level includes junior
references/react/semi-senior.md # If level includes semi-senior
references/react/senior.md # If level includes senior
references/nextjs/junior.md # If Next.js + level includes junior
references/nextjs/semi-senior.md # If Next.js + level includes semi-senior
references/nextjs/senior.md # If Next.js + level includes seniorUsing the index, select patterns based on:
--specific filters by category--specific is setSelection by amount:
When level=mixed: distribute patterns roughly evenly across junior/semi-senior/senior. When specific level selected: all patterns from that level only.
For each selected pattern:
--comments: // ANTI-PATTERN: pattern-id--comments-hint: Add the hint comment from pattern--comments-fix: Add the fix comment from patternAfter all changes, provide summary:
## Anti-Patterns Applied
### Files Modified
- path/to/Component.tsx: 3 patterns
- path/to/hooks/useData.ts: 2 patterns
### Patterns Introduced
| Pattern | Level | Category | File |
|---------|-------|----------|------|
| list-keys-index | junior | list | Component.tsx:45 |
| usememo-inline-defeat | semi-senior | rerender | Component.tsx:23 |
...
### Next Steps
Run the app and use React DevTools Profiler to identify the performance issues,
or review the code to spot the anti-patterns.# Defaults (medium, mixed levels, no comments)
/react-anti-patterns
# Few junior patterns with hints
/react-anti-patterns --comments-hint low junior
# Many senior patterns with full explanations
/react-anti-patterns --comments-fix high senior
# Only waterfall patterns (Next.js)
/react-anti-patterns --specific waterfall
# Medium amount, semi-senior level, identify comments
/react-anti-patterns --comments medium semi-seniorreferences/anti-patterns-index.mdreferences/react/references/nextjs/~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.