RRepoGEO

REPOGEO REPORT · LITE

kinopeee/cursorrules

Default branch main · commit 46ec5200 · scanned 5/20/2026, 7:31:54 AM

GitHub: 1,118 stars · 60 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
23 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 0 warn · 1 fail
Objective metadata checks
AI knows your name
2 / 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 kinopeee/cursorrules, 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 README H1 and opening sentence to explicitly state 'Cursor AI Assistant'

    Why:

    CURRENT
    # cursorrules "v5"
    
    🇬🇧 **English** | 🇯🇵 **日本語## 🌏 Select Your Language / 言語を選択
    
    This repository provides custom instructions and custom commands optimized for Cursor.
    COPY-PASTE FIX
    # cursorrules "v5" - Custom Instructions & Commands for the Cursor AI Assistant
    
    🇬🇧 **English** | 🇯🇵 **日本語## 🌏 Select Your Language / 言語を選択
    
    This repository provides custom instructions and custom commands specifically optimized for the [Cursor AI Assistant](https://cursor.sh).
  • highabout#2
    Add a concise description to the repository's About section

    Why:

    COPY-PASTE FIX
    Custom instructions, rules, and workflow commands optimized for the Cursor AI Assistant (cursor.sh) to enhance coding support and consistency.
  • mediumtopics#3
    Add relevant topics to improve discoverability and categorization

    Why:

    COPY-PASTE FIX
    ai-assistant, cursor-ai, custom-instructions, coding-assistant, developer-tools, prompt-engineering, workflow-automation

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 kinopeee/cursorrules
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. OpenAI API · recommended 2×
  3. GitKraken Client · recommended 1×
  4. JetBrains AI Assistant · recommended 1×
  5. Git Commit AI · recommended 1×
  • CATEGORY QUERY
    How to configure an AI coding assistant for consistent commit messages and PR descriptions?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot
    2. GitKraken Client
    3. JetBrains AI Assistant
    4. Git Commit AI
    5. AI Commit
    6. OpenAI API
    7. Anthropic API

    AI recommended 7 alternatives but never named kinopeee/cursorrules. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking pre-built instructions to enhance AI developer tools for better coding support.
    you: not recommended
    AI recommended (in order):
    1. OpenAI API
    2. GitHub Copilot
    3. Hugging Face Transformers Library (huggingface/transformers)
    4. Tabnine
    5. Snyk Code
    6. CodeQL (github/codeql)
    7. Pylint (pylint-dev/pylint)
    8. ESLint (eslint/eslint)
    9. RuboCop (rubocop/rubocop)

    AI recommended 9 alternatives but never named kinopeee/cursorrules. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    fail

    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 kinopeee/cursorrules?
    pass
    AI did not name kinopeee/cursorrules — likely talking about a different project

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

  • If a team adopts kinopeee/cursorrules in production, what risks or prerequisites should they evaluate first?
    pass
    AI named kinopeee/cursorrules 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 kinopeee/cursorrules solve, and who is the primary audience?
    pass
    AI named kinopeee/cursorrules 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 kinopeee/cursorrules. 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/kinopeee/cursorrules.svg)](https://repogeo.com/en/r/kinopeee/cursorrules)
HTML
<a href="https://repogeo.com/en/r/kinopeee/cursorrules"><img src="https://repogeo.com/badge/kinopeee/cursorrules.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

kinopeee/cursorrules — 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