code-antipatterns

Detect React and TypeScript anti-patterns and propose concrete fixes.

8|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kensaurus/cursor-kenji --skill code-antipatterns-kensaurus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-antipatterns
Source: https://github.com/kensaurus/cursor-kenji/tree/main/skills/code-antipatterns
Command: npx skills add https://github.com/kensaurus/cursor-kenji --skill code-antipatterns-kensaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and remediate code anti-patterns that cause bugs, slow performance, and maintenance headaches.

Core Features & Use Cases

  • Detects React anti-patterns, TS anti-patterns, and architecture flaws.
  • Provides concrete fixes and refactoring guidance to improve maintainability and performance.
  • Use cases include code reviews, legacy refactoring, debugging, and onboarding teams.

Quick Start

Ask me to scan your project for common React/TypeScript anti-patterns and propose concrete, actionable fixes.

Frequently Asked Questions about code-antipatterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify React anti-patterns causing slow performance and maintenance issues?

Identify React anti-patterns by scanning your project for common structural and performance flaws. This process enforces checks for problematic component designs, providing concrete refactoring fixes to improve maintainability and rendering speed.

What are common TypeScript anti-patterns I should look for during code reviews?

Common TypeScript anti-patterns include architectural flaws and poor separation of concerns. During code reviews, enforce checks for these patterns to detect bugs early and guide the team toward clean design best practices.

How do I refactor legacy code to fix architectural flaws and improve separation of concerns?

Refactor legacy code by identifying architectural flaws and applying concrete remediation steps. This enforces separation of concerns and clean component design, resolving maintenance headaches and puzzling debugging issues.

Can I use this to onboard teams to best practices for clean component design?

Yes, you can use this to onboard teams to best practices for clean component design. It guides developers through detecting anti-patterns and applying concrete fixes, establishing consistent separation of concerns across React and TypeScript.

What is the best way to debug puzzling issues caused by code anti-patterns?

The best way to debug puzzling issues caused by code anti-patterns is to scan the codebase for known structural flaws. This identifies the root causes of bugs and slow performance, providing actionable refactoring guidance.