@iamdevlinph/codex-kit 1.0.19 → 1.0.20
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -121,12 +121,16 @@ conditional procedures into validated project skills.
|
|
|
121
121
|
|
|
122
122
|
## Structure
|
|
123
123
|
|
|
124
|
-
- Follow the repository's organization and naming.
|
|
125
|
-
|
|
124
|
+
- Follow the repository's organization and naming. Organize feature-specific
|
|
125
|
+
code under the feature's existing directory; when a feature contains multiple
|
|
126
|
+
substantial UI pieces, place them in a `<feature>/components` subdirectory.
|
|
127
|
+
Keep broadly reused code in the repository's established shared locations.
|
|
126
128
|
- Keep route and page files focused on page-level composition, data loading, and
|
|
127
129
|
orchestration. Extract substantial self-contained UI sections and complex
|
|
128
|
-
page-specific logic into colocated
|
|
129
|
-
|
|
130
|
+
page-specific logic into focused files colocated with the feature. Split large
|
|
131
|
+
or mixed-responsibility files by cohesive behavior so each file remains easy
|
|
132
|
+
to read, navigate, test, and review. Keep small one-use markup or logic inline;
|
|
133
|
+
do not create files or components solely to reduce line count.
|
|
130
134
|
- Use intent-revealing domain names. A reader should understand what a variable
|
|
131
135
|
contains or what a helper guarantees at the call site without opening its
|
|
132
136
|
implementation. Avoid vague transformation names such as `normalized`,
|