RRepoGEO

REPOGEO REPORT · LITE

RayFernando1337/llm-cursor-rules

Default branch main · commit d31bec10 · scanned 6/5/2026, 1:23:16 AM

GitHub: 888 stars · 136 forks

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface RayFernando1337/llm-cursor-rules, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition the README H1 and opening sentence to clarify the repo's purpose

    Why:

    CURRENT
    # LLM Cursor Rules
    
    Welcome to my repository of go-to rules for using Cursor and LLMs in software development!
    COPY-PASTE FIX
    # LLM Cursor Rules: A Guide to Best Practices for AI-Assisted Development
    
    This repository contains my opinionated rules and best practices for *developers* leveraging Large Language Models (LLMs) and the Cursor editor in software development workflows. It's a practical guide for *using* AI coding tools effectively, not an AI tool itself.
  • mediumtopics#2
    Add relevant topics to improve categorization

    Why:

    COPY-PASTE FIX
    llm, large-language-models, cursor-ide, ai-coding, best-practices, software-development, swift, swiftui, nextjs, development-workflow, developer-tools, coding-guidelines
  • lowhomepage#3
    Add a homepage link to your X (formerly Twitter) account

    Why:

    COPY-PASTE FIX
    https://x.com/RayFernando1337

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface RayFernando1337/llm-cursor-rules
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GitHub Copilot
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. GitHub Copilot · recommended 2×
  2. Tabnine · recommended 2×
  3. ChatGPT/GPT-4 · recommended 1×
  4. Cursor · recommended 1×
  5. vercel/ai · recommended 1×
  • CATEGORY QUERY
    What are effective best practices for using AI coding tools in Next.js development?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot
    2. ChatGPT/GPT-4
    3. Tabnine
    4. Cursor
    5. Vercel AI SDK (vercel/ai)
    6. AWS CodeWhisperer
    7. Google Gemini Code Assist

    AI recommended 7 alternatives but never named RayFernando1337/llm-cursor-rules. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking guidelines for integrating AI coding assistants into a modern software development workflow.
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot
    2. Amazon CodeWhisperer
    3. DeepSource
    4. SonarQube
    5. CodiumAI
    6. Tabnine
    7. Mintlify
    8. Fig AI

    AI recommended 8 alternatives but never named RayFernando1337/llm-cursor-rules. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of RayFernando1337/llm-cursor-rules?
    pass
    AI named RayFernando1337/llm-cursor-rules explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts RayFernando1337/llm-cursor-rules in production, what risks or prerequisites should they evaluate first?
    pass
    AI named RayFernando1337/llm-cursor-rules explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo RayFernando1337/llm-cursor-rules solve, and who is the primary audience?
    pass
    AI named RayFernando1337/llm-cursor-rules explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of RayFernando1337/llm-cursor-rules. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/RayFernando1337/llm-cursor-rules.svg)](https://repogeo.com/en/r/RayFernando1337/llm-cursor-rules)
HTML
<a href="https://repogeo.com/en/r/RayFernando1337/llm-cursor-rules"><img src="https://repogeo.com/badge/RayFernando1337/llm-cursor-rules.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

RayFernando1337/llm-cursor-rules — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite