Skip to content
Agentic Levels
Start hereLevelsTracksPromptsAbout
Get my levelGet my level

  • Start hereYour first useful task with AI.
  • Level quiz8 questions. No AI needed.
  • Fluency ScoreYour Level and a score, from your own AI.

  • LevelsThe 11 levels, in order.
  • LessonsShort lessons, filter by level.
  • TracksGuided paths by tool, role or goal.
  • Set up your AI tool
  • Starter packFree files that help AI remember.

  • PromptsReady prompts to copy and adapt.
  • ChatGPT vs Claude vs GeminiPick the right one for the job.
  • How-tos
  • ReferenceCommands for Claude Code, Codex, Antigravity.
  • ResourcesHand-picked reading and tools.

  • Your progress
  • Your next moveAn interview that picks your next skill.
  • Your next lessonsThe next lessons at your level.
  • Updates

  • Pricing
  • About
  • FAQ & Feedback
  • Work with us
  • How we handle your data
Sign inPreferences
AboutPricingHow-tosPromptsStarter packMy stackHow we handle your data

© 2026 Fuentes Studio

PrivacyTermsRefundsAccessibilityAI content policyCredits
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

←How-to guides
  1. Resources
  2. ›How-to guides

How to use Awesome Cursor Rules

Community-curated rules files for every stack, the fastest way to get stack-aware coding behavior.

Levels 1 to 2On GitHub

Claude's default coding style doesn't match your stack. You want it to follow your conventions, use your preferred patterns, and stop suggesting the wrong imports.

Before you start

Claude Code or Cursor installed

  1. 1Find the rule file for your stack
  2. 2Add to CLAUDE.md or .cursorrules and customize

Steps

01

Find the rule file for your stack

The repo is organized by framework and language. Search for your stack (React, Next.js, Python, FastAPI, SwiftUI, etc.) and copy the rules file. These are battle-tested by the community.

02

Add to CLAUDE.md or .cursorrules and customize

Paste the rules into your CLAUDE.md or .cursorrules file. Then add your own project-specific rules on top, naming conventions, file structure, what to always/never do in your codebase.

Extend with your project rules
I've added the [STACK] rules from awesome-cursorrules to my CLAUDE.md. Now I need project-specific rules for: [YOUR_CONVENTIONS]. Write the additional CLAUDE.md section that captures these rules clearly and specifically.
[STACK]Your stack e.g. Next.js 15 + TypeScript + Tailwind
[YOUR_CONVENTIONS]Your project conventions e.g. kebab-case filenames, no default exports, all state in Zustand stores, no prop drilling beyond 2 levels

How do you know it worked?

  • Claude follows your stack's conventions without being reminded each session
  • At least 3 project-specific rules added on top of the base rules

If something looks off

Trim the bloat
Rules files can grow large, trim anything Claude already knows by default. Shorter is more reliable.
Test in a fresh session
Test your rules file in a new session where Claude has no prior context for your project, that's the real test.

See also

  • Claude Code memory (CLAUDE.md)
  • Claude Code best practices

What you'll do, 2 steps

  1. 1Find the rule file for your stack
  2. 2Add to CLAUDE.md or .cursorrules and customize

Was this helpful?