contentrain-content

Skill: Create Content for Existing Models

Generate and save content entries for models already defined in the project.

---

When to Use

The user wants to create new content, add entries to a collection, populate a singleton, or says something like "add a blog post", "create content", "fill in the hero section".

---

MUST Rules

• MUST call contentrain_describe before writing content (know the schema)
• MUST provide ALL required fields in entries
• MUST create entries for ALL supported locales when model has i18n: true
• MUST NOT set system fields (id, slug, createdAt, updatedAt, status, source)
• MUST run npx contentrain generate after adding new models or changing fields

---

Steps

1. Check Project State

Call contentrain_status to get the full project context:

• Confirm the project is initialized.
• List available models, their kinds, domains, and field counts.
• Note supported locales and the source locale.
• Check for any pending changes or validation errors.

If .contentrain/ does not exist, stop and suggest running /contentrain-init first.

2. Identify the Target Model

If the user specified a model, use it. Otherwise:

• Present the list of available models from status.
• Ask the user which model to create content for.
• If the user describes content without naming a model (e.g., "write a blog post about X"), infer the model from context.

3. Read the Model Definition

Call contentrain_describe(model: "<model-id>", include_sample: true) to get:

• All field definitions (name, type, required, constraints).
• A sample entry if one exists (use it as a structural reference).
• Relation fields and their target models.

If the user's request does not match an existing model, offer to create one first with contentrain_model_save.

4. Read Vocabulary and Context

• Check .contentrain/vocabulary.json for canonical terms. All content must use these terms consistently across locales. Do not use alternative spellings or synonyms for vocabulary-defined terms.
• Check .contentrain/context.json for tone conventions (professional, casual, technical).
• For dictionaries: Before creating any new key, call contentrain_content_list on the target model and scan existing values. If the value you intend to write already exists under a different key, REUSE the existing key instead of creating a new one. MCP will also warn you via advisories in the save response if duplicates are detected. Replacing an existing key's value is allowed — the response reports what was replaced, so read the advisories rather than assuming a save was purely additive.