Codex Kernelia Frontend Feature Boundaries and Public Exports
Keep a feature's presentation, screen logic and data access together while exposing a small public interface.
中文Install in Codex
Open Kernelia in Codex with the feature code and an inventory of other modules that use it.
- Review `.agents/skills/frontend-features/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/frontend-features/` in your project and save the reviewed file as `.agents/skills/frontend-features/SKILL.md`.
- Start Codex from that project's root, then type `$frontend-features` and select the matching skill.
Example task
Map the file boundaries for this sample search feature.
{"feature":"search","ui":"SearchToolbar","query":"useSearch","request":"loadResults","externalImport":"SearchToolbar"}What to check
Use `components`, `hooks`, and `services` for the implementation. Export only `SearchToolbar` from `features/search/index.ts`.
Original SKILL.md on GitHub · Updated
Frequently asked question
When does a feature need a shared store folder?
Add a store for genuinely shared complex state. Keep single-screen state in the feature's local interaction logic.