contentrain-initlisted

# Skill: Initialize Contentrain in a Project > Set up Contentrain content infrastructure in an existing project. --- ## When to Use The user wants to add Contentrain to their project, or says something like "set up contentrain", "initialize contentrain", "add content management". --- ## Steps ### 1. Detect the Tech Stack Read `package.json` to identify the framework: | Dependency | Stack | |---|---| | `nuxt` | Nuxt 3 | | `next` | Next.js | | `@astrojs/astro` or `astro` | Astro | | `@sveltejs/kit` | SvelteKit | If none match, treat as a generic Node.js project. Report the detected stack to the user before proceeding. ### 2. Ask for Configuration Ask the user for: - **Supported locales:** Which languages will the project support? Default: `["en"]`. Use ISO 639-1 codes. - **Source locale:** Which locale is the primary/source locale? Default: `"en"`. - **Domain names:** Suggest domains based on the project structure (e.g., `marketing`, `blog`, `app`, `docs`). Ask the user to confirm or modify. ### 3. Initialize the Project Call the MCP tool: ``` contentrain_init(stack: "<detected>", locales: ["en", ...], domains: ["marketing", ...]) ``` This creates the `.contentrain/` directory structure, `config.json`, and initial `context.json`. ### 4. Analyze Project Conventions After initialization, review the project for conventions to inform content creation: - **Tone:** Analyze existing copy in the project (README, landing page, UI text) to determine the appropriate to