Use this repository as a draft-first Substack CLI and MCP project.
- Keep CLI and MCP changes aligned. Shared behavior should live in
src/once, then be exposed through the CLI, MCP server, and tests. - Update the relevant
tracks/*.mdfile when scope changes or a milestone completes. - Keep secrets, browser sessions, traces, and
.substack-cli/out of Git. - Run
npm run qualityandnpm run scan:secretsbefore committing changes.
workflow.mdfor the high-level delivery strategy.docs/workflows/cli.mdfor command and track work.docs/workflows/mcp.mdfor MCP surface changes.README.mdfor user-facing command examples.
- Prefer small, typed modules over shared ad hoc helpers.
- Keep redacted summaries redacted.
- Treat direct browser/API probing as discovery input, not the default path.