realtimekit-ui-addons / hand-raise
AGENTS.md3 starsChanged 9 months agoApache-2.0View on GitHub
Three cooperating web components for participant hand-raise gesture + host list view.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- src/reactions-manager/AGENTS.mdAGENTS.md
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
All three components use Shadow DOM (mode: "open") and clean up event listeners on disconnectedCallback.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
hand-raise
Three cooperating web components for participant hand-raise gesture + host list view.
STRUCTURE
hand-raise/
├── index.ts # HandRaiseAddon — orchestrator; registers 3 custom elements
├── HandRaiseButton.ts # rtk-hand-raise-toggle — control bar toggle button
├── HandRaisedList.ts # rtk-hand-raised-list — host sidebar list of raised hands
└── RaisedHand.ts # rtk-raised-hand — icon overlay on participant tilesWHERE TO LOOK
| Task | Location |
| RTKStore creation | index.ts → meeting.stores.create('handRaise') inside static async init() |
| Store subscribe/unsubscribe | Each component's connectedCallback / disconnectedCallback |
| Toggle hand-raise state | HandRaiseButton.ts → dispatches store update via store.set(...) |
| Host view of raised hands | HandRaisedList.ts → filters store state, renders sorted list |
| Tile overlay icon | RaisedHand.ts → reads store state per participantId attribute |
| PIP integration | RaisedHand.ts:58-66 — sets participant.raised directly on the participant object |
CONVENTIONS
HandRaiseAddonconstructor isprivate; always usestatic async init(props).- Store key is
'handRaise'; created once ininit(), read in each component viameeting.stores.stores.get('handRaise'). - All three components use Shadow DOM (
mode: "open") and clean up event listeners ondisconnectedCallback.
ANTI-PATTERNS
participant.raised = this.raisedatRaisedHand.ts:58is a deliberate Web Core PIP workaround — Web Core reads this property directly instead of RTKStore; do not remove.as anycast atindex.ts:50onmeeting.participants.pipis an explicit backward-compatibility shim (comment: "Type-casting pip for backward compatibility"); do not replace with a typed import.HandRaisedList.tsre-renders the full list on every store update — no diffing; acceptable for small participant counts but becomes expensive at scale.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

