RRepoGEO

REPOGEO REPORT · LITE

jtdaugherty/brick

Default branch master · commit 868004e1 · scanned 5/21/2026, 5:48:25 AM

GitHub: 1,716 stars · 171 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
62 /100
Needs work
Category recall
1 / 2
Avg rank #1.0 when recommended
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 jtdaugherty/brick, 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
    Clarify `brick`'s identity as a declarative TUI *framework* in the README opening

    Why:

    CURRENT
    `brick` is a Haskell terminal user interface (TUI) programming toolkit. To use it, you write a pure function that describes how your user interface should be drawn based on your current application state and you provide a state transformation function to handle events. `brick` exposes a declarative API.
    COPY-PASTE FIX
    `brick` is a declarative Haskell terminal user interface (TUI) *framework*. Unlike most GUI toolkits, it provides a declarative API where you describe your UI based on application state, and handle events by updating that state.
  • mediumcomparison#2
    Add a 'Comparison' section to the README

    Why:

    COPY-PASTE FIX
    Add a new section titled 'Comparison to other TUI Frameworks' or 'Why Brick?' that highlights `brick`'s declarative approach and contrasts it with other TUI libraries/frameworks (e.g., `Textual`, `Bubbletea`, `Lip Gloss` from other languages, or Haskell alternatives like `vty` directly).
  • lowhomepage#3
    Add a homepage URL to the repository About section

    Why:

    COPY-PASTE FIX
    Set the repository homepage URL to `https://github.com/jtdaugherty/brick` (or a dedicated documentation site if one exists).

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
1 / 2
50% of queries surface jtdaugherty/brick
Avg rank
#1.0
Lower is better. #1 = top recommendation.
Share of voice
8%
Of all named tools, what % are you?
Top rival
vty
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. vty · recommended 1×
  2. Haskeline · recommended 1×
  3. prompt-toolkit-haskell · recommended 1×
  4. optparse-applicative · recommended 1×
  5. ansi-terminal · recommended 1×
  • CATEGORY QUERY
    How to build interactive command-line user interfaces using Haskell?
    you: #1
    AI recommended (in order):
    1. brick ← you
    2. vty
    3. Haskeline
    4. prompt-toolkit-haskell
    5. optparse-applicative
    6. ansi-terminal
    Show full AI answer
  • CATEGORY QUERY
    Seeking a declarative framework for developing rich terminal user interfaces.
    you: not recommended
    AI recommended (in order):
    1. Textual (Textualize/textual)
    2. Bubbletea (charmbracelet/bubbletea)
    3. Lip Gloss (charmbracelet/lipgloss)
    4. Glamour (charmbracelet/glamour)
    5. Rich (Textualize/rich)
    6. tui-rs (fdehau/tui-rs)
    7. Blessed (chjj/blessed)

    AI recommended 7 alternatives but never named jtdaugherty/brick. 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 jtdaugherty/brick?
    pass
    AI did not name jtdaugherty/brick — 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 jtdaugherty/brick in production, what risks or prerequisites should they evaluate first?
    pass
    AI named jtdaugherty/brick 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 jtdaugherty/brick solve, and who is the primary audience?
    pass
    AI named jtdaugherty/brick 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 jtdaugherty/brick. 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/jtdaugherty/brick.svg)](https://repogeo.com/en/r/jtdaugherty/brick)
HTML
<a href="https://repogeo.com/en/r/jtdaugherty/brick"><img src="https://repogeo.com/badge/jtdaugherty/brick.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

jtdaugherty/brick — 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