Star a repository

Star a repository in GitHub — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Star the repository myteam/cli-tool so our PMs can quickly find it from their dashboard and track…
Star the repository myteam/cli-tool so our PMs can quickly find it from their dashboard and track its visibility metrics. Confirm the star is on my personal account jessica.dev and return a quick note if it was already starred.

Improve — make it easier to accept

+
Before I star myteam/cli-tool to signal interest to the maintainer, make the action meaningful:…
Before I star myteam/cli-tool to signal interest to the maintainer, make the action meaningful: check if I already starred it, show recent release notes and open issues that justify the star, and surface whether other product managers in my org have starred it. If there’s a duplicate or organizational account, warn me.

Decide — diagnose the stuck moment

+
I clicked star on my personal account jessica.dev for myteam/cli-tool and the UI still shows…

I tried to star a repo but the button didn’t change

I clicked star on my personal account jessica.dev for myteam/cli-tool and the UI still shows unstarred. I’m not sure if the action failed, if I’m signed into a different account, or if there’s a permissions problem. Which checks should I run now to confirm I’ve starred the repo and to fix the account mismatch if needed?

Become — change the pattern

+
Our team stars are inconsistent: PMs, engineers, and security give stars without any record, so we…

we lose track of which team members endorsed projects

Our team stars are inconsistent: PMs, engineers, and security give stars without any record, so we can’t tell which projects the company is tracking. What habit or small policy would get us a reliable signal of who in the org has endorsed a repo and why, without adding heavy process?

Next to this one

Other code hosting work people do in GitHub.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.