Starter templates, verification tooling, and launch/presence utilities for small software products. Each repo is the source of truth for its current CI, release, and package status.
Already have a repo? Run the dry-run check inside that repo:
cd path/to/your/repo
npx @starter-series/create add-componentStarting from a starter instead?
gh repo create my-app --template starter-series/docker-deploy-starter| Starter | What it covers |
|---|---|
| docker-deploy-starter | Containerized app baseline with deploy workflows |
| mcp-server-starter | TypeScript MCP server baseline |
| python-mcp-server-starter | Python MCP server baseline |
| npm-package-starter | npm package baseline with trusted publishing workflows |
| browser-extension-starter | Browser extension baseline with store-release workflows |
| vscode-extension-starter | Editor extension baseline with marketplace workflows |
| discord-bot-starter | Chat bot baseline with deploy workflows |
| telegram-bot-starter | Chat bot baseline with polling and webhook modes |
| electron-app-starter | Desktop app baseline with packaging workflows |
| react-native-starter | Mobile app baseline with app-store workflows |
| cloudflare-pages-starter | Static site baseline with pages-deploy workflows |
| Tool | What it does |
|---|---|
| create-starter | Scaffolds starters and audits existing repos for release, CD, and security wiring |
| shotkit | Captures store and social assets from built browser extensions |
| Tool | What it does |
|---|---|
| ProfileKit | Builds composable SVG cards for profiles, READMEs, dev blogs, and personal sites |
| profilekit-mcp | Renders ProfileKit cards through an MCP stdio surface |
Use repo-local evidence rather than profile-page claims:
- Check each repo's README, package manifest, and
.github/workflows/directory for its current implementation surface. - Check the starter-series hub for the broader health table and org-audit notes.
- This profile intentionally avoids version, publish, CI-pass, and KPI claims that can drift.
