32pixels Blog

When software can be conjured from a conversation, the real differentiator won't be the code — it'll be the taste, the brand, and the vision behind it.

I built an autonomous research assistant using Claude scheduled tasks and ContextStore.

ASCII wireframes and flowcharts are one of the most practical things you can ask Claude to generate.

AI is advancing on three areas at once.

Your AI agent can read local files, but it doesn't know about your other ContextStore spaces.

A step-by-step guide to connecting ContextStore to Claude Desktop using Cowork.

Most AGENTS.md files try to do too much.

Remote MCPs add a round-trip tax every time your AI needs context.

Poor AI output is usually a context problem, not a prompting problem.

The build vs. buy equation has radically shifted.

Poor AI output usually isn't a prompting problem, it's a context problem.

Quiddity interviews you about your tools and process, then generates custom /new-issue, /next-task, and /approve skills tailored to how you actually work.

The final post in my series on skills for dev workflow.

As your agent skills grow, some parts want to be their own thing.

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.

One of the most exciting things about LLMs is their ability to do useful things that would be hard to script in the traditional sense.

Back in January, I posted on LinkedIn about using AI to build a documentation site for Opine.

I’m actually not sure when I first noticed this.

As a teenager I learned to program and it wasn't long before I had a directory filled with unfinished projects.

Since launching Zest Icons last year it was always my dream to have a free version of the set.

I build web applications for a living.

Not quite as glamorous as The Matrix may make it appear, the command prompt is still an essential part of the modern web design workflow.

I like to describe Zest as a modern icon set that has been meticulously handcrafted for web and mobile.

Learn how to use Sass color functions to calculate backwards compatible colors for browsers that don't support alpha transparency and wrap up this functionality in a couple of handy mixins.

Learn how to modularize your typography to create solid foundation for your projects.

The more you write your own stylesheets, the more you begin to value using good names in your code.

If avoiding nested selectors in favor of a flatter class-based CSS scares you, maybe this example will help you embrace some of the principles of modular CSS.

We've written before about the dangers of nesting your CSS selectors too deeply.

One of the coolest features of crafting CSS with Sass is that you can build out a file structure that puts all your components in their right place.

Since the creation of Sass, it has been plagued by many levels of controversy.

If you've been following my Twitter stream during the last month, you know that I've been hard at work on a project callded Serve.

Since Adam McCrea has introduced his solution for simplifying HTML mockups over on the EdgeCase blog, I thought I would take the time to reintroduce my own: Serve.

Based on my HAML server for web designers article, I've created a small gem "serve" which makes it extremely easy for a Web Designer to get up and running with Haml and Sass.

I have a script named serve in my bin directory that let's me quickly startup a Webrick server in any directory.