skills/tapcart-blocks/SKILL.md
Create, pull, push, and manage versions of Tapcart blocks and global components using the Tapcart CLI. Use when the user wants to create a block or component, pull blocks from the dashboard, push changes, start a dev server, list versions, or set a version live.
npx skillsauth add tapcartinc/tapcart-agent-skills tapcart-blocksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage Tapcart blocks and global components. Blocks and components have identical operations — this skill covers both. All commands run from the root of the Tapcart project directory.
You (the agent) run all commands directly unless noted otherwise.
Run the create command, then confirm to the user what was created:
# Block
tapcart block create <BlockFolderName>
# Component
tapcart component create <ComponentFolderName>
After creating, tell the user how to start the dev server (see Dev Server below).
Run the pull command to sync from the Tapcart dashboard to the local ./blocks or ./components folder:
# Pull all blocks
tapcart block pull -a
# Pull specific block(s)
tapcart block pull -b MyBlock
tapcart block pull -b BlockOne -b BlockTwo
# Pull a specific version of a block
tapcart block pull -b MyBlock -v 2
# Pull all components
tapcart component pull -a
# Pull specific component(s)
tapcart component pull -c ProductCard
tapcart component pull -c ProductCard -c Button
# Pull a specific version of a component
tapcart component pull -c ProductCard -v 3
Constraints:
-a and -b/-c cannot be combined-v can only be used with a single block/component nameBefore pushing, read the local code.jsx and config.json to confirm the changes look correct, then confirm with the user before running.
# Push a specific block (creates new version, not live)
tapcart block push -b MyBlock
# Push and set the new version live immediately
tapcart block push -b MyBlock --live
# Push multiple blocks
tapcart block push -b BlockOne -b BlockTwo
# Push all blocks
tapcart block push -a
# Push a specific component
tapcart component push -c ProductCard
# Push and set live
tapcart component push -c ProductCard --live
# Push all components
tapcart component push -a
Warning:
--livemakes the new version immediately visible to all app users. Default to pushing without--liveand then usingversions setafter the user has verified the result.
Run the dev server in the background and tell the user it is running. Keep it running until the user asks you to stop it.
# Block dev server
tapcart block dev -b MyBlock
tapcart block dev -b MyBlock -p 4995 # custom port, default is 4995
# Component dev server
tapcart component dev -c ProductCard
tapcart component dev -c ProductCard -p 4996 # default is 4996
The dev server opens at http://localhost:<port> (block default: 4995, component default: 4996).
When the user asks to stop the dev server, terminate the process.
Run this and show the output to the user:
tapcart block versions list -b MyBlock
tapcart component versions list -c ProductCard
Output shows each version number, which is local, and which is live on the dashboard.
Confirm with the user which version to promote, then run:
tapcart block versions set -b MyBlock -v 2
tapcart component versions set -c ProductCard -v 3
Version numbers are 1-based (version 1 is the first push).
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.