Codex JHipster Vue Boundaries for Views, Themes and Core
Keep Vue view composition, reusable theme components and centralized API access in their project-specific layers.
中文Install in Codex
Open a JHipster Vue 3 project in Codex with the target view, reusable components and backend data contract.
- Review `.agents/skills/jhipster-vue-standards/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/jhipster-vue-standards/` in your project and save the reviewed file as `.agents/skills/jhipster-vue-standards/SKILL.md`.
- Start Codex from that project's root, then type `$jhipster-vue-standards` and select the matching skill.
Example task
Assign responsibilities for this sample item card view.
{"page":"ItemGrid.vue","card":"BaseItemCard","request":"listItems","pageLoading":true}What to check
Use `ItemGrid.vue` for Views composition, `BaseItemCard` in Themes and `listItems` in the Core API service. Keep visible loading feedback in the view.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should a view make its own data request directly?
This project centralizes requests in the Core API layer. Views consume the result and compose the presentation.