A step-by-step guide to connecting ContextStore to Claude Desktop using Cowork. Grant folder access, co-create documents with Claude, and give your AI the context it needs.

Most AGENTS.md files try to do too much. Treat yours as a table of contents — link to essential docs, let your LLM know where to look, and keep the file itself short and scannable.

Remote MCPs add a round-trip tax every time your AI needs context. Local Markdown files are faster, cheaper, and more reliable. Here's why that matters.

Poor AI output is usually a context problem, not a prompting problem. ContextStore is a native Mac app that makes it easy for anyone on your team to build and manage a Markdown-based context repository.

The build vs. buy equation has radically shifted. I built a full comment system for my blog in a few hours with AI — moderation, magic link auth, spam protection — and I own every piece of it.

Poor AI output usually isn't a prompting problem, it's a context problem. A context repository gives your AI the business knowledge it needs to make good decisions. Here's how to build one.

Quiddity interviews you about your tools and process, then generates custom /new-issue, /next-task, and /approve skills tailored to how you actually work. One install, one setup command, and you're off.

The final post in my series on skills for dev workflow. A /new-issue skill lets you describe a bug or feature in a sentence and get back a well-structured issue with wireframes and acceptance criteria — better than most people write by hand.

As your agent skills grow, some parts want to be their own thing. Here's how I used a simple prompt to extract a standalone /approve skill from my /next-task skill — and why thinking of skills like functions leads to better workflows.

A step-by-step guide to building a /next-task agent skill that pulls from your issue tracker, manages branches, implements changes, and opens PRs. Customize it for your own tools — Linear or Jira, GitHub or GitLab.