Integrate Frames into the developer workflow (skills, agents, frictionless install)

Motivation

Frames are only valuable when they are actually in the loop while someone works. Today, getting a Frame into a working session is a manual errand: open the web app, find the Frame, copy the markdown or run an install, and keep it in sync by hand. The MCP endpoint solves discovery for chat clients, but a developer in an editor or a terminal still has to think about Frames as a separate destination they visit, rather than context that is simply present.

The registry has the pieces (CLI, MCP endpoint, file install, .frame.md export). What's missing is the last mile that makes using them feel automatic.

Proposal

Make the common paths one step, and make the tooling meet people where they already work:

• Claude Code skills and agents. Ship first-class skills/agents for working with Frames - discover the Frames relevant to what I'm doing, pull one into the session, author or update one from the conversation, keep an installed Frame current. Frames should be usable without the author knowing anything about MCP wiring or the CLI's flag surface.
• Frictionless install and refresh. Installing a Frame into a project and later refreshing it should be a single command that does the right thing, including for a Frame with parents.
• Relevance, not just listing. Surface the Frames that apply to the repo/task at hand rather than the full org catalog, so the developer isn't picking from an undifferentiated list.
• Authoring from where the context lives. Let a developer promote what they just wrote or explained into a Frame without leaving their editor or terminal.
• Onboarding path. A first-time user should get from "I have access" to "a Frame is in my session" without reading the README end to end.

Notes

Worth scoping as a set of small, shippable improvements rather than one large change - each of the bullets above stands on its own. Some of this may land as documentation and defaults rather than code.

Acceptance criteria

• Using a Frame in a Claude Code session does not require manual copying or hand-editing config.
• Authoring or updating a Frame is possible from a working session.
• The onboarding path is documented and matches the shipped tooling.

Start by reviewing the existing CLI, MCP endpoint, file-install flow, and .frame.md export, then compare them with the README onboarding path. Split the proposal into independently shippable improvements, beginning with the smallest workflow gap. Done means the selected path supports session use or authoring without manual copying, and the documented onboarding matches the shipped tooling.