Skip to main content

3 posts tagged with "VS Code"

Content related to Visual Studio Code and extensions

View All Tags

Why We Named Our Coding Companion “Huckleberry”

· 2 min read
Tim Morris
Huckleberry Creator

In Tombstone, Val Kilmer’s Doc Holliday delivers a line that hangs in the air like gun smoke:

“I’m your huckleberry.”

It’s not a boast. It’s not a catchphrase. It’s a statement of intent.
If this job needs doing, I’m the one who’ll do it.

According to Southern vernacular, a huckleberry was someone just right for the job. The person you call on when it’s time to get something done. Not flashy. Not loud. Just reliable, precise, and quietly confident. If there’s work worth doing, your huckleberry will be there. Coat off. Sleeves rolled. Toothpick optional.

That’s the energy we wanted for our VS Code assistant.

Are We There Yet?

· 3 min read
Tim Morris
Huckleberry Creator

If you’ve ever played The Oregon Trail, you know the vibe. You set off full of optimism, the wagon’s creaking, the oxen are cooperative, and spirits are high. Then reality sets in. The river’s too deep, someone’s caught dysentery, and the map you printed turns out to be wishful thinking.

Shipping a VS Code extension, especially one powered by AI, feels a lot like that.
You start with a plan and a promise. But the road? It’s longer.
The ruts are deeper.
And yes, someone’s always asking: “Are we there yet?”

Fastest Draw in the West: Calling Custom Prompts in VS Code

· 5 min read
Tim Morris
Huckleberry Creator

Back in the dusty streets of modern coding, there's a new gunslinger in town: VS Code v1.100. And no, it's not just another shiny feature or cosmetic tweak, this one packs real firepower: named prompt files.

For the Huckleberry agent crowd, the folks who keep their tasks sharp, tools clean, and AI sidekicks at the ready, this is a genuine shift in the landscape.


What Makes This a Big Deal?

Picture this: a busy day in the code corral. Bugs need wrangling, tests are bucking out of control, and documentation's flapping wild like a saloon door in the wind.

With the new prompt files feature, you can now summon task-specific prompts by name, right inside your VS Code chat. Drop your .prompt files into the .github/prompts directory, and when the moment calls, just type /your-prompt-name into the chat. That's all it takes, your custom instructions roll out like a sheriff's decree.

No more repeating the same explanations or reinventing the wheel. It's like carrying a custom-engraved six-shooter, ready to draw at a moment's notice.