inmake DOCS
Docs / Starter / What you get

What you get

The contents of the starter zip.

The Starter is the downloadable template for a new store project: the prebuilt SDK packages with their types, the MCP launcher, an .env template and the Claude Code workspace files. These pages are the developer hand-out (docs/VENDOR.md) split by step.

This is the hand-out for external developers building a drop-core store. It is self-contained: everything you need is this file plus the download link below. (Internal note: the zip is published with npm run publish:vendor; see docs/sdk-development.md.)

What you get#

A ready-to-open store workspace, vendor-core/:

  • vendor/ — the four drop-core SDK packages, prebuilt with types (drop-core-lib, drop-core-sdk, drop-core-server, drop-core-generative). Nothing to build, nothing to edit there. Each is MIT-licensed — the LICENSE file sits in the package folder.
  • The drop-core MCP server (.mcp.json → vendor/mcp.mjs) — open the folder with an MCP-capable agent (Claude Code, Cursor, …) and it gets guarded, store-scoped tools for your store's data, schemas, templates and design. It ships as one self-contained file (vendor/mcp-server/), so it runs without npm install.
  • Workspace files — README.md (the full manual), RULES.md (app-code conventions), AGENTS.md (agent ground rules), init.mjs, .env.example, and this VENDOR.md (so the project and its agent always have the download link and the update steps).
  • vendor/manifest.json — records exactly which drop-core build the packages came from.
  • npm run module:pack (vendor/module-pack.mjs) — checks and packs a module folder into the zip the console's Upload package takes (see "Modules" below).

Requirements: Node 20+, npm, and (for the agent workflow) an MCP-capable agent. There is deliberately no app scaffold — the front-end/server is up to your project; README.md ("Building the front-end") covers both paths.