Repository navigation
feat(trending): put braille sparks and run chips on the board - #431
Merged
Merged
Conversation
The new brand puts the dot motifs where the registry's evidence lives. Trending is the board readers copy from, so each row now shows its signal and its command in the brand shapes. - Each row with posts draws seven days of counted mentions as a braille spark. The loader already reads every post in the window, so the counts come from the same rows that rank the Skill, in rolling 24-hour days. - Surge and filler rows keep the star line, because stars ranked them. The surge reason now says it was a star surge, as VISION principle 4 asks of every trending number. - A compact run chip appears only where the row stands for exactly one Skill. Filler and the all-time range pick a Skill out of a repository, so a multi-Skill repository gets no command. Copies still report. - The skilld install chip sits in the header aside at every width. - The nav and the directory table drop the flame emoji for a braille mark, and the flame animation goes with it. - Ranks print in stone dots so the rose stays with the motifs.
DESIGN.md keeps motifs out of navigation and gives each surface one rose element. The header's rose is the logo dot, so the nav mark draws in stone. A month board also ranks posts older than the spark's seven days, and seven blank cells beside a zero read as a broken row, so those rows show no spark and their posts carry the dates.
Collaborator
Author
|
Agent note. Checked by hand, since CI cannot cover it:
|
Contributor
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. The pull request closed. |
1 of 6 tasks
This was referenced Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Related to #427 and #426
❓ Type of change
📚 Description
The dot brand from #427 needs to reach
/skills/trending, the board readers copy from. Each row now draws the signal that ranked it and prints its command in the brand shapes.loadTrendingSkillsalready reads those posts, so/api/feed/trendinggainsmentionsByDayfrom the same rows that rank the Skill. A row with no mention in seven days shows no spark; its posts carry their own dates.Star surge: +N stars in a day.repoSkillCountfor that check. Copies report throughuseInstallCopywith surfacetrending-row.Teach your agent skilldwith the skilld install chip at every width, under the weekly invitation on wide screens./skillstable replace the flame emoji with a braille mark. The flame animation CSS is gone. The nav mark is stone, because the logo dot is the header's rose.Page question: what are devs talking about, and how do I run it? Primary action: copy the run command. Owning concern: Loop 1. VISION principle 4: PASS; each number says what it counts, and a star-ranked row never shows a mentions spark. DESIGN motifs: PASS; one rose per motif, and the nav mark draws no rose.
Gap: the board has no per-Skill change dates, only a repository push date on the all-time range. That range keeps
Updated {date}instead of a change grid.