RRepoGEO

REPOGEO REPORT · LITE

kunchenguid/lavish-axi

Default branch main · commit 0fa3968f · scanned 6/20/2026, 1:51:43 AM

GitHub: 534 stars · 43 forks

AI VISIBILITY SCORE
28 /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
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 kunchenguid/lavish-axi, 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 core value proposition in README

    Why:

    CURRENT
    The current README starts with badges and a generic tagline before stating the core purpose.
    COPY-PASTE FIX
    Move 'HTML is the new markdown. Lavish is the new editor for your HTML artifacts.' to be the very first line of text after the main heading/badges, or integrate it into the main heading.
  • hightopics#2
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    html, editor, ai-collaboration, annotation, feedback, local-development, generative-ai
  • mediumhomepage#3
    Add a homepage URL to the repository

    Why:

    COPY-PASTE FIX
    [Insert URL to project website, demo, or documentation here]

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 kunchenguid/lavish-axi
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
microsoft/vscode
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. microsoft/vscode · recommended 1×
  2. ritwickdey/vscode-live-server · recommended 1×
  3. kaihao/vscode-html-preview · recommended 1×
  4. aaron-bond/better-comments · recommended 1×
  5. Gruntfuggly/todo-tree · recommended 1×
  • CATEGORY QUERY
    How can I provide precise feedback on AI-generated HTML documents locally?
    you: not recommended
    AI recommended (in order):
    1. VS Code (microsoft/vscode)
    2. Live Server (ritwickdey/vscode-live-server)
    3. HTML Preview (kaihao/vscode-html-preview)
    4. Better Comments (aaron-bond/better-comments)
    5. Todo Tree (Gruntfuggly/todo-tree)
    6. Git
    7. Chrome DevTools
    8. Firefox Developer Tools
    9. Beyond Compare
    10. KDiff3 (KDE/kdiff3)
    11. Meld (GNOME/meld)
    12. Storybook (storybookjs/storybook)
    13. Playwright (microsoft/playwright)
    14. Cypress (cypress-io/cypress)
    15. Percy
    16. Applitools
    17. Figma
    18. Sketch
    19. Adobe XD

    AI recommended 19 alternatives but never named kunchenguid/lavish-axi. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools allow interactive annotation and element-specific comments on local HTML files?
    you: not recommended
    AI recommended (in order):
    1. Hypothesis
    2. AnnotatorJS
    3. DocFX
    4. Live Server
    5. Perlite

    AI recommended 5 alternatives but never named kunchenguid/lavish-axi. 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 kunchenguid/lavish-axi?
    pass
    AI named kunchenguid/lavish-axi explicitly

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

  • If a team adopts kunchenguid/lavish-axi in production, what risks or prerequisites should they evaluate first?
    pass
    AI named kunchenguid/lavish-axi 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 kunchenguid/lavish-axi solve, and who is the primary audience?
    pass
    AI did not name kunchenguid/lavish-axi — 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?

Embed your GEO score

Drop this badge into the README of kunchenguid/lavish-axi. 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/kunchenguid/lavish-axi.svg)](https://repogeo.com/en/r/kunchenguid/lavish-axi)
HTML
<a href="https://repogeo.com/en/r/kunchenguid/lavish-axi"><img src="https://repogeo.com/badge/kunchenguid/lavish-axi.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

kunchenguid/lavish-axi — 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
kunchenguid/lavish-axi — RepoGEO report