docs(skills): rework devframe skill for standard handler + hub - #266
Merged
Conversation
Reframe the devframe agent skill around the current architecture: the Web-Standard handler (initDevframe) as the portability primitive, the @devframes/hub composition layer (initHub, docks/commands/messages/ terminals), and the single/hub split across @devframes/vite, /next, and /nuxt. Fold in the high-level positioning from 'Pluggable, Extensible, and Playful DevTools'. - Replace the stale Vite-DevTools-only mounting story with the deployment map (serve one devframe vs. serve many via a hub) - Add sections on the standard handler, the hub subsystems/protocol, and the framework packages' two scopes - Fix drift against current APIs: importMetaUrl, storage scopes, validator-neutral RPC schemas (devframe/utils/simple-schema), duplicationStrategy/services/staticConfig/rpc.snapshot - Remove the dead ../../skills/vite-devtools-kit reference - Update templates/counter-devframe.ts and add templates/hub.ts
✅ Deploy Preview for devfra ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Completely reworks the
devframeagent skill (skills/devframe/SKILL.md) to match the current architecture and the high-level positioning from Pluggable, Extensible, and Playful DevTools.The previous skill framed devframe almost entirely around mounting into Vite DevTools via
createPluginFromDevframe. It predated the standard web handler (initDevframe) and the@devframes/hubcomposition layer, so it undersold devframe's actual portability story and had drifted from the current API surface.What changed
initDevframe→.handler/.nodeMiddleware) vs. a hub (@devframes/hub, many tools composed behind one namespace).initDevframe, mounting snippets, the WebSocket-binding precedence,globalThismemoization, auth-gates-by-default. This was previously absent entirely.initHub, the four subsystems (docks/commands/messages/terminals), launchers/cross-iframe activation,ctx.install, the shared-state protocol, and theuislot.single/hubsplit across@devframes/vite,@devframes/next,@devframes/nuxt.importMetaUrl, corrected storage to the three scopes (workspace/project/global), reframed RPC schemas as validator-neutral Standard Schema (including the zero-depsbuilder fromdevframe/utils/simple-schema), documentedduplicationStrategy/services/staticConfig/rpc.snapshot, modernized client discovery to./__connection.json, and removed a dead link to a nonexistent sibling skill.templates/counter-devframe.tsand addedtemplates/hub.tsas a runnable hub-composition reference (covered by the existingskills/devframe/templates/*.tsknip entry glob).Verification
docs/guide/*,docs/adapters/*,docs/frameworks/*, and the actual package exports/source (packages/devframe,packages/hub,packages/vite,packages/next,packages/nuxt) rather than relying on the prior skill's wording.skills/is eslint-ignored and the new template is already covered byknip.jsonc's entry glob, so no lint/typecheck/knip impact.This PR was created with the help of an agent.