block-creationlisted

# block-creation — Skill instructions ## When to invoke Invoke this skill when the builder expresses intent to create a new block. Trigger phrases include: - "build me a block that ..." - "scaffold a block for ..." - "create a new block named ..." - "I need a block that does ..." Do NOT invoke when the builder is asking to: - Install an existing block into a workspace (that's the SeldonFrame MCP's `install_*` tools). - Modify an existing block (refer to direct file edits). - Generate UI components or pages (out-of-scope for this slice; future SLICE 4 scope). ## Framing — this is code-authoring, not workspace-admin The scaffold writes files to the builder's repo working tree. It does NOT: - commit to git - push to a remote - install the block into a running workspace - modify any workspace's database Those are the builder's follow-up actions (`git add` / `git commit` / `git push`, then `install_block` against a workspace). Claude Code is a code-gen assistant here, not a platform admin. ## Workflow ### 1. Intent → BlockSpec Claude Code reads the builder's natural-language intent and constructs a `BlockSpec` JSON object matching the shape below. **Before constructing the spec, Claude should Read:** 1. Reference anatomies — the composition-contract shape of two existing blocks. These show the canonical layout for produces / consumes / tools / subscriptions: - `packages/crm/src/blocks/notes.block.md` (simple tool-only block — the PR 1 C7 smoke-test)