Stripe Projects CLI

This repository is initialized for the Stripe project "2026-06-11-justhtml".

Workflow

0. Run stripe projects llm-context to get the LLM context for the project.

1. Start with stripe projects status or stripe projects show to inspect the current project, linked providers, and named resources.

2. Use stripe projects catalog or stripe projects services to browse available providers and services. When you know the provider, run stripe projects catalog <provider> --json or stripe projects catalog <provider> and copy the exact <provider>/<service> slug from the output.

3. Provision a resource with stripe projects add <provider>/<service>. Do not guess the stripe projects add argument. Run stripe projects catalog <provider> --json or stripe projects catalog <provider> and copy the exact <provider>/<service> slug before you run stripe projects add. Example: stripe projects add databaseco/postgres --name primary-db. Use --name <resource> to control the local resource name used by future resource commands and environment variable prefixes. If you omit --name, the CLI uses the provider/service default for the local resource name. When a service config field looks like a name, the CLI uses the current project name as the default value when that satisfies the field schema. Use --config '<json>' when the service requires configuration.

4. Review credentials with stripe projects env. Values are redacted by default, and you can use stripe projects env --pull to write them to local files. If named project environment commands are available, stripe projects env --pull writes credentials for the active environment to that environment's output file.

5. After a successful stripe projects add, summarize the result and suggest next steps:

   Field	Value
   Provider	<provider name>
   Service	<service type>
   Tier	<tier>
   Env vars	<variable names only — never values>