Codex ELISEI Content Type Design with Shared and Detail Fields
Add a publishable content type to ELISEI by keeping common data in the base layer and type-specific data in a detail model.
中文Install in Codex
Open ELISEI in Codex with the proposed fields, existing content contracts and intended listing surfaces.
- Review `.agents/skills/add-content-type/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/add-content-type/` in your project and save the reviewed file as `.agents/skills/add-content-type/SKILL.md`.
- Start Codex from that project's root, then type `$add-content-type` and select the matching skill.
Example task
Assign fields for this sample reading-list content type.
{"type":"reading list","base":["author","status"],"detail":["orderedLinks"],"surfaces":["feed","search"]}What to check
Put `author` and `status` in shared `content`. Keep `orderedLinks` in the detail model and check feed and search mapping.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should all type-specific fields go into the shared table?
Keep fields in the base layer when several content types actually share the concept. Put other values in type detail models.