jprokay
jprokay has an llms.txt. Do you?
Julian Prokay's blog is a treasure trove for developers eager to enhance their coding workflows. With a focus on AI-assisted tools and modern development practices, Julian shares insights and practical extensions that elevate coding efficiency. Dive in for actionable tips and innovative strategies!
Not sure yours is this good? Check it →
jprokay's llms.txt Insights
Short and sweet
4 sections. Minimalist, but hey — at least they showed up.
What's inside jprokay's llms.txt
jprokay's llms.txt contains 5 sections:
- Julian Prokay's Blog
- Blog Posts
- Technical Interests
- Contact
- Optional
How does jprokay's llms.txt compare?
| jprokay | Directory Avg | Top Performer | |
|---|---|---|---|
| Lines | 46 | 1029 | 163,447 |
| Sections | 4 | 17 | 3207 |
Cool table. Now the real question — where do you land? Find out →
jprokay's llms.txt preview
First 46 of 46 lines
# Julian Prokay's Blog
> Full-stack developer with 15 years of experience architecting systems, building teams, and deploying infrastructure. Writing about AI development, software engineering, and the intersection of technology and creativity.
I'm Julian Prokay, a software engineer passionate about building tools and sharing insights about modern development practices, particularly around AI-assisted coding and efficient software workflows.
## Blog Posts
- ["pi: The Coding Agent For Your Workflow"](https://jprokay.com/post/018-pi-coding-agent): Most coding agents (and especially their interfaces) have limited extensibility. pi is a minimal terminal harness you extend with TypeScript — custom tools, commands, and even the TUI. Here's how I built three extensions that turned it into an agentic IDE.
- [Working on the Go with Terminus, Tailscale, and Claude](https://jprokay.com/post/017-mobile-dev-workflow): A look at using Terminus, Tailscale, and Claude Code to enable productive development sessions from anywhere.
- [Looking back on a year of change](https://jprokay.com/post/016-reflections-on-2025): 2025 has been a transformative year both personally and professionally. Let's reflect and look forward to 2026
- [devenv - The best tool for the job](https://jprokay.com/post/015-devenv): You start a new project, you open up the README, and begin going through all the installation instructions. Oops someone forgot to document a dependency! What if you could get rid of this problem entirely? What if setting up a project just required you to open it up?
- [Process update - How I use Agents as of Dec. 2025](https://jprokay.com/post/014-process-update): My process has solidified over the fall into something consistent and repeatable. Even as models change, I have found a lightweight, easy to manage flow with Claude.
- [Finally Understanding Subagents](https://jprokay.com/post/013-finally-understanding-subagents): Creating subagent configurations for specific tasks in Claude Code or Opencode.
- [Planning with Claude Desktop, Coding with Claude Code ](https://jprokay.com/post/012-claude-and-claude-code): Using different types of Claude to play to their strengths
- [Claude Code Custom Slash Commands ](https://jprokay.com/post/011-slash-commands): 3 Custom Slash Commands to orchestrate an end-to-end development life cycle using Claude Code
- [Remote Agents and You ](https://jprokay.com/post/010-remote-agents): Remote coding agents like Devin are getting a lot of hype. Are they ready for primetime?
- [Helpful MCP Servers ](https://jprokay.com/post/009-mcp-suggestions): 3 MCP Servers that have made a difference
- [Enterprise Vibe Coding ](https://jprokay.com/post/008-enterprise-vibes): Ideas on avoiding slop when you are trying to vibe
- [Reformed AI Skeptic](https://jprokay.com/post/007-on-ai-assistance): AI assistants are changing coding. Is it still worth the skeptism?
- [Shifting Left ](https://jprokay.com/post/006-shifting-left): AI is shifting the task of engineering towards one of judgement and evaluation. What skills will the engineer of the future need to be successful?
- [Minimal Viable Blogging ](https://jprokay.com/post/005-mvb): Starting a blog doesn't require Rails, Django, or Astro. You can do it with HTML, CSS, and a bit of Caddy. Start your own Minimal Viable Blog
- [Sorting files in reverse order ](https://jprokay.com/post/004-sorting-files): Using Sprig and Caddy template functions to render a list of posts in reverse order
- [Styling code blocks with Chroma ](https://jprokay.com/post/003-styling-code-with-chroma): Setting up CSS with Chroma to render code blocks
- [Anatomy of a Post ](https://jprokay.com/post/002-anatomy-of-a-post): Leveraging Caddy's splitFrontMatter to build a feed
- [Hello World ](https://jprokay.com/post/001-first-post): Using Caddy templates to generate a link feed ala Simon Willison
## Technical Interests
- AI-assisted development workflows
- Model Context Protocol (MCP) and AI tool integration
- Minimalist web architectures
- Developer productivity and automation
- Software engineering best practices
## Contact
- [LinkedIn](https://www.linkedin.com/in/julian-prokay/)
- [GitHub](https://github.com/jprokay)
- [Bandcamp](https://bandcamp.com/jbeard)
## Optional
- [Homepage](https://jprokay.com/): Personal website and blog
- [Blog Feed](https://jprokay.com/feed): Complete list of all blog posts
What is llms.txt?
llms.txt is an open standard that helps AI language models understand your website. By placing a structured markdown file at /llms.txt, websites provide AI search engines like ChatGPT, Claude, and Perplexity with a clear map of their content, services, and documentation. Companies like jprokay use it to ensure AI accurately represents their brand when answering user queries. Read the spec.
jprokay showed up. Where's yours?
1000+ companies didn't overthink it. 60 seconds. Go.
Check your site →