in an era of slop, the product yearns for an interface from a human touch

Mattan Ingram DANN© Word doesn't make you a Writer. And Figma doesn't make you a Designer. And also: everyone working on software should care about design. We should welcome more input in the design process and encourage non-designers to improve their skills / taste.

Today we're introducing Skills in claude dot ai, Claude Code, and the API. Skills let you package specialized knowledge into reusable capabilities that Claude loads on demand as agents tackle more complex tasks. Here's how they work and why they matter for the future of agents:

How to turn your website into a revenue generating machine give Claude Code / Codex etc this checklist

steal my claude commands: github.com/jxnl/dots/tree… also works in Cursor

99% of the reason people think AI coding sucks is their lack of knowledge about how LLMs work. this guy explains how abusing the context window with crap results in AI confusion. in other words, skill issue.

Vector databases explained for people who just want to understand. You have 10,000 product descriptions. User searches for "comfortable outdoor furniture." Traditional database: - Searches for exact word matches - Finds products containing "comfortable" OR "outdoor" OR

Most people get more rewarded for talking about their goals than going after them. Which is why most people stay stuck and never start.

Felix If you want to see what they look like github.com/contains-studi…

Getting over the hump of AI slop to create something aesthetic and user friendly is no joke.

Training LLMs end to end is hard. Very excited to share our new blog (book?) that cover the full pipeline: pre-training, post-training and infra. 200+ pages of what worked, what didn’t, and how to make it run reliably huggingface.co/spaces/Hugging…

Loving how the Figma MCP <> Cursor connection cuts iteration time. One-shotting designs lands ~60-70% right. Still need to prompt for logic tho and yet to see if it detects prototype links.

- you are - a normal dev who’s heard “embeddings” and “RAG” 1000x - want to know what they actually are, how they plug into LLMs - suddenly: vectors are just coordinates for meaning, not magic - first: what even is an “embedding”? - embedding = a list of numbers (a vector)

Cursor scaled to $29B without any full-time PMs. Ryo (Cursor's Head of Design) walked me through how they work and it's the opposite of every big tech best practice: 1. Roles are muddy PM work is spread across designers and engineers. Everyone does what fits their strengths

the old way of scaling teams is dead: we used to hire specialists – designers, engineers, PMs – each in their lane, scaling by adding more people. but when Cursor can take you from idea to code in minutes, execution isn't the bottleneck anymore. taste and judgment are. what

Pro tip: If you're afraid to take the risk, write down in excruciating detail what you're actually afraid of having happen. Step by step what happens next when you fail. You'll often find it's not so bad when you spell it out. Fear exists in the vague, not the specific.

so I’m starting to believe more and more that the most effective employees will have custom agents and personal software they bring to their jobs. and these people will become 100x employees. how I see this working: personally, the way I operate now is simple: whatever I’m

few will understand this. for the last few decades, UI/UX has been built on a stable background assumption: the human is the only general intelligence in the loop. software is procedural. UI's job is to make that procedure discoverable and efficient: - show the state of the

This is wild 🤯🤯🤯