A collection of real prompts I used while working on Project Bluefin (July–August 2026). No prompt engineering, just talking. Pulled from my Copilot CLI session history.
- "let's publish sboms and start fixing things here"
- "keep finding things to fix in the container"
- "check projectbluefin/common, why is chairlift not on my system?"
- "let's keep working on shipping chairlift give me a status after you load up docs and skills"
- "load all docs and skills and let's prepare the lab to merge these updates, I want full distributed bst testing on the cluster - so do the prep work for that first - be thorough and use subagents and context7, k8sgpt, whatever you need"
- "onboard into the repo and prepare to take my feedback on the tool, start by reviewing and merging PRs, you have my permission, then start fixing issues, I will give you thinks to fix during the session. Let's go for 1 hour"
- "continue the session where we're fixing wolves, there was a computer crash"
- "what is happening with this issue, check these pull requests"
- "add "OGC Kernel" and then version, drop podman, flatpak"
- "run the website locally so I can see it, let's add a new section to the downloads. "For the Wolves" then a description... Then add three box downloads, left to right, just like up top, same style. Dakotaraptor, [ REDACTED ], and then Bluefin Server. Use the right dinos for each"
- "let's add these bleak landscapes from destiny 2 into the intro before the destiny sequence, to show the devatastation - use agents to get desinty artwork it's all freely licensed - I especially love the ones of europa - ensure variety"
- "the readme png on the dakota page is out of date and is generate here, fix it"
- "post a thumbnail of this video in a blog post, just open the PR I will finish it. Don't make content just the video"
- "let's make a blog version of this: -- title "The Wolves Are Coming" and then "embedd" the post stylistically in the standalone blog post, load some design skills"
- "Fleet deployed: implement it"
- "Fleet deployed: check all PRs and issues and let's fix everything"
- "Review: load all skills and start going through the queue, fix and merge do not leave comments - ensure you are testing on the lab if the item requires testing"
- "let's merge the PR then"
- "I approve it, merge it"
- "merge into main let's go!"
- "commit and push"
- "update all documentation, enforce projectbluefin/common doc structure, end session"
- "a previous agent has destroyed the cluster and the review container, repair it"
- "why is there a bunch of made up text? that's not what I asked for get rid of it"
- "why is the review-container up I literally told you to only run it in the foreground. Look at policy"
- "the container is stale - colors are still broken - you didn't update anything."
- "still yellow instead of capucchin"
- "right because I told you the lab isn't working and to build locally"
- "the lab might be stuck build locally"
- "all variants MUST source from their SBOMs or it's a bug, fix it"
- "let's find a way to cut traffic but I want on-demand dakota/bluefin testing when I'm reviewing PRs"
- "codify this, it's only done when :stable is pushed"
- "let's clean up this mess, merge whatever fixes it, close the rest, and resolve this issue, if it's a problem someone can open a new one"
- "fix everything after one rubber duck from opus5"
- "rubber duck the plan with fable"
- "check the bandwidth metrics over the past few days"
- "what is taking all my bandwidth"
- "how much is left"
- "am I connected to the hive?"
- "why would danathar get a PR review job?"
- "build locally and show me"
- "serve it local"
- "the font should match the initial intro movie"
Short, imperative, context-loaded. The agent has the repo, the skills, and the docs — the prompt is just the intent.