new-doppler-project

Create Doppler projects and environment configs for monorepo services.

198|19|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/iterate/iterate --skill new-doppler-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-doppler-project
Source: https://github.com/iterate/iterate/tree/main/.agents/skills/new-doppler-project
Command: npx skills add https://github.com/iterate/iterate --skill new-doppler-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines creating the correct Doppler project and environment configs when you add a new app or service to the monorepo.

Core Features & Use Cases

  • Create a new Doppler project for the new app/service and register it in the repo’s doppler.yaml with the proper path.
  • Wire config inheritance from _shared so the new project inherits the standard secrets, behavior, and environment setup.
  • Add per-user development configs and minimal app-local secrets, ensuring dev and production templates are consistent while keeping app-local overrides small.
  • Use safe environment defaults, including disabling Personal Configs on the dev environment to avoid creating dev_personal configs.

Quick Start

Add the app/service folder as <repo-path> and run: Create the Doppler project, create inherited configs (dev_jonas, dev_misha, dev_rahul, preview_2..preview_9, prd), set APP_CONFIG to {} for dev and prd, then register the project in doppler.yaml using the same slug and path.

Frequently Asked Questions about new-doppler-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Doppler environment configs for a new app in a monorepo?

To set up Doppler environment configs for a new monorepo app, create the project, generate standard inherited configs from _shared, disable dev Personal Configs, set APP_CONFIG, and update doppler.yaml with the correct slug and path.

How does config inheritance work when adding a new service to a monorepo?

Config inheritance wires the new Doppler project to inherit standard secrets and environment setup from a shared _shared config, ensuring consistent behavior across per-user dev configs and production templates while keeping app-local overrides minimal.

What's the best way to manage per-user development configs in Doppler?

Managing per-user development configs involves creating inherited configs like dev_jonas or dev_misha from the shared settings, disabling Personal Configs on the dev environment to prevent dev_personal configs, and keeping app-local secrets minimal.

Do I need to update doppler.yaml when creating a new Doppler project?

Yes, you need to update doppler.yaml when creating a new Doppler project by registering the new project using its specific slug and matching repository path to ensure correct monorepo onboarding and deployment preparation.

How do I configure preview environments in Doppler for a new repository?

Configuring preview environments in Doppler involves generating a standard config set that includes sequential preview environments, such as preview_2 through preview_9, alongside your dev and prd configs, all inheriting from the shared settings.

Why should I disable Personal Configs on the dev environment in Doppler?

Disabling Personal Configs on the dev environment prevents the automatic creation of dev_personal configs, ensuring developers use the intended inherited per-user configs like dev_jonas and maintaining consistent environment templates.