Read the full article on sshh.io
A breakdown of how one developer integrates Claude Code into their daily engineering workflow.
The CLAUDE.md file acts as the repo’s operating manual for the agent. It defines the main tools, APIs, and conventions the team uses. Keep it concise and reference long documentation by link rather than embedding large sections. The goal is clarity, not verbosity.
To make a language model less predictable and more insightful, apply the following strategies:
Use a negative style guide
Clearly state what you don’t want the model to do.
Force divergence in choice
Push the model to break away from default phrasing or reasoning patterns.
At the start of a session Claude’s various harnesses can scan all available skill files and read a short explanation for each one from the frontmatter YAML in the Markdown file. This is very token efficient: each skill only takes up a few dozen extra tokens, with the full details only loaded in should the user request a task that the skill can help solve.
Claude Code is, with hindsight, poorly named. It’s not purely a coding tool: it’s a tool for general computer automation. Anything you can achieve by typing commands into a computer is something that can now be automated by Claude Code. It’s best described as a general agent. Skills make this a whole lot more obvious and explicit.
- Agent primitives are software: Your .prompt.md and .instructions.md files represent executable natural language programs that deserve professional tooling infrastructure.
- Runtime diversity enables scale: Agent CLI runtimes provide the execution environments that bridge development to production.
- Package management is critical: APM provides the npm-equivalent layer that makes agent primitives truly portable and shareable.
- Production ready today: This tooling stack enables automated AI workflows in CI/CD pipelines with enterprise-grade reliability.
- Ecosystem growth pattern: Package management infrastructure creates the foundation for thriving ecosystems of shared workflows, tools, and community libraries
How to build reliable AI workflows with agentic primitives and context engineering
it's three markdown files, and it's basically three prompts. What I figured out is, okay, if you want to build something, whether it's the whole app or just a feature of the app, you of course have to create a PRD, a product requirement doc, and again, it's like, duh. But a lot of people don't know this.
What I do is I have this file, you just tag it, and then you tag the filename, and then I now use Whisper Flow, and I'm not an investor, I'm not being paid to say that, but I just click the Alt key on my keyboard, and I just start blabbing about this feature and everything about it, and then I tag this file called Create PRD, and then the model goes to work, and the prompt is basically like, okay, take the user's requirements, ask them five clarifying questions, and then once you get the answer, then build out a pretty typical PRD. Yeah. Great.
>You got a PRD. You specify a lot of things, but now what? So, then the second file
I think it is one of the most powerful ways to create clarity of thinking for yourself, because clarity of thinking is, in my view, one of the most important things. And you only can really get that by forcing yourself to write down your ideas. And so I suppose one pertinent or timely piece of advice is, if you care about this, do not use an LLM to produce text for YouTube.
Because first of all, if you're putting your name on this thing, at least today, the LLM is like, it's pretty easy to tell when somebody does that. But more importantly, you are losing the opportunity to do the thinking yourself. And that thinking that happens when you write is one of the most important types of thinking for growth.
Mitchell Hashimoto describes how he shipped Ghostty’s unobtrusive macOS update UI using agentic AI with deliberate human oversight. 
Define the shape of the solution first. Hashimoto chose Sparkle’s custom UI path and a titlebar accessory concept, then used an agent to prototype UI states, not to “build everything.” Humans kept control of scope and taste. 
After the release from Gemini Cli, Claude Code is now offerings plugins. It seems taylor made for the Enterprise or teams, to quickly share configurations between team members. Excited to try it out.
Source: Claude Code plugins
The co-founder of Instagram, Mike Krieger, which is now at Anthropic, mentioned that they use the Claude Agent SDK in a automated Slack channel when there is a new incident. It is name Claude Pager and it gathers all the context of the incident and can be poked to give out infromation when needed.
I have been waiting to implement something similar in our stack, once we are finally off the waiting list of the Datadog MCP waitlist...
Source: Big Technology Podcast
Following the vibe research, we now get vibe engineering from Simon Willison:
Vibe engineering establishes a clear distinction from vibe coding. It signals that this is a different, harder and more sophisticated way of working with AI tools to build production software.