The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need a local copy of the payments-lib repo so I can implement token rotation. Clone the…
Execute — do the immediate task
+I need a local copy of the payments-lib repo so I can implement token rotation. Clone the repository acme-payments/payments-lib to my machine into ~/code/payments-lib, check out the feature/token-rotation branch if it exists, otherwise create the branch from origin/main. Verify that LFS files, submodules, and Git hooks are cloned.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before teammates clone, make it as painless as possible. Add a short Getting Started section at the…
Improve — make it easier to accept
+Before teammates clone, make it as painless as possible. Add a short Getting Started section at the top of README showing the exact clone command including the target path, describe required credentials or SSH vs HTTPS, note any large files or submodules and how to fetch them, and add a script or git template to install recommended hooks. Call out troubleshooters for common clone failures.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I tried to clone acme-payments/payments-lib and got a permission denied error. My coworker Anna can…
Decide — diagnose the stuck moment
+I tried cloning and it failed with 'permission denied'.
I tried to clone acme-payments/payments-lib and got a permission denied error. My coworker Anna can clone fine. I don't know whether it's my SSH key, an org membership, or repo visibility. What is the most likely cause given Anna's success, and what sequence of checks and fixes will get me unstuck quickly without changing org-wide settings?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+New hires keep emailing that they can't clone repos on day one because SSH keys, 2FA, or org…
Become — change the pattern
+Clones repeatedly fail for new hires who don't have access set up.
New hires keep emailing that they can't clone repos on day one because SSH keys, 2FA, or org invites weren't completed. This creates stop-the-line delays for onboarding. Which credential and invite steps should I standardize and automate so a developer can clone any team repo on day zero, and what quick habit will prevent regressions?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
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.