Codex Kernelia System Design for Repository and Deployment Choices
Evaluate the application, repository and deployment separately. Base each recommendation on team constraints, scale and the existing setup.
中文Install in Codex
Open Kernelia in Codex or supply the system context, team size and deployment constraints. Record any assumptions.
- Review `.agents/skills/system-design/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/system-design/` in your project and save the reviewed file as `.agents/skills/system-design/SKILL.md`.
- Start Codex from that project's root, then type `$system-design` and select the matching skill.
Example task
Recommend the three architecture choices for this new internal catalogue.
{"product":"internal catalogue","teamSize":2,"expectedServices":1,"releaseArtifacts":1}What to check
Propose `modular monolith`, `single repository` and `one deployable artifact`, given the team of two and the single-release constraint.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does one repository automatically imply one deployment artifact?
Decide system topology, repository and deployment separately. Revise the deployment shape when independent releases are needed.