#mcp
8 posts.
-
framesmith 2.2: not everything is a dashboard
framesmith 2.1 and 2.2 are out: a commerce genre for checkout screens, a runnable test suite, a 45x faster viewer, and a pile of evaluator fixes.
-
framesmith 2.0: don't ask the model for taste
The thing agents are worst at is visual taste, so they fake it. framesmith 2.0 generates a full design language deterministically, no API key, AA by construction.
-
framesmith 1.10: approvals that can be proven wrong
A design gate is only as good as its ability to notice reality drifted. framesmith 1.10 binds approvals to a content hash and turns drift into a CI check.
-
framesmith 1.9: built for product screens
Charts as a first-class node type, reusable components, bulk edits, and an evaluator that knows a dashboard isn't a landing page. framesmith 1.9.0 is out.
-
framesmith 1.8: click the design, tell the agent
framesmith 1.8 makes human design feedback structured — click any element, type a note, and the agent gets it anchored to the exact node it belongs to.
-
framesmith 1.7: teaching an agent when a design is done
framesmith 1.7 adds a vetted pattern library and a machine-readable 'done' contract, so an agent crafts a good UI and won't hand you a half-finished one.
-
A wrong reconstruction is worse than an honest stack
Building framesmith v1.5's UI importer taught me the rule for any tool an agent consumes: be honest about your confidence, not just your output.
-
MCP tool descriptions are the API: lessons from a Rails server
An agent disqualified a sales deal that should have been marked lost. The MCP server did exactly what it was told. Here's what I learned shipping a Rails MCP server an agent could actually use right.