Turn the charming skill into an app-building guide, not just a CLI reference - #9
Merged
Merged
Conversation
skills/charming/SKILL.md was a command reference with no mention of the app contract: manifest shape, capabilities, env.storage rules, the window.charming.api calling convention, sandbox gotchas, or the design system an agent needs to build something that actually works. Port the universal (transport-agnostic) parts of the contract, split into SKILL.md plus resources/contract.md and resources/patterns.md, and add a templates/crud starter so agents copy a working skeleton instead of free-handing one from memory. Also fix examples/hello, which was still on the pre-contract manifest shape (version, displayName, capabilities.exports) and would fail create against the current API. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
michaelmagan
force-pushed
the
skill-app-building-guide
branch
from
August 23, 2026 18:17
111dce1 to
9b0f374
Compare
This was referenced Aug 23, 2026
michaelmagan
added a commit
that referenced
this pull request
Aug 23, 2026
#11) main shipped a literal leftover '>>>>>>> 111dce1 (...)' conflict-marker line from #9's merge, live on the public repo and served by ClawHub and Hermes. Also re-applies the version pin on the npm install example, lost in the same merge (ClawHub's security scan flags a bare, unpinned npm install -g as MEDIUM supply_chain risk).
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
1 participant
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
skills/charming/SKILL.mdonly documented CLI verbs (auth, apps create/list/describe/source/update/call/delete). It said nothing about the app contract itself, so an agent following it had no way to know what a workingmodule.js/ui.jsneeds to contain.env.storagerules,window.charming.apicalling convention, sandbox gotchas, the stone design system, and hard-won patterns like undo-toast deletes and migration discipline) from the internal MCP-flavored skill, adapted for the CLI's actual workflow (full-bundleupdatewith ETag matching, not MCP'sedits[]/revision).SKILL.md+resources/contract.md(long-form capability/permissions/secrets/images reference) +resources/patterns.md, mirroring the existingresources/convention.templates/crud/(module.js + ui.js + styles.css) as a real, copyable starter —cp -r "$(npm root -g)/usecharming/templates/crud" ./my-app— instead of building a scaffold-generator command. Addedtemplatestopackage.json'sfiles.examples/hello/module.js, which was still on a pre-contract manifest shape (version,displayName,capabilities.exports,readOnlyinstead ofannotations.readOnlyHint) that the current API would reject.Test plan
bun run typecheck— passes (no TS files touched)bun run test— 111/111 passingnode --checkon every new/changed.jsfilenode bin/run.js apps create ./templates/crud --dry-runand... ./examples/hello --dry-run— both bundle and print correctly🤖 Generated with Claude Code