yjcli 0.2.3__tar.gz → 0.2.4__tar.gz

{yjcli-0.2.3 → yjcli-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: yjcli
-Version: 0.2.3
+Version: 0.2.4
 Summary: Scaffold platforms, services, and AI agent wiring (Cursor/Claude/Codex) for YJ architecture repos.
 Project-URL: Homepage, https://github.com/yseiren87/yjcli
 Project-URL: Repository, https://github.com/yseiren87/yjcli

{yjcli-0.2.3 → yjcli-0.2.4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "yjcli"
-version = "0.2.3"
+version = "0.2.4"
 description = "Scaffold platforms, services, and AI agent wiring (Cursor/Claude/Codex) for YJ architecture repos."
 readme = "README.md"
 requires-python = ">=3.12"

{yjcli-0.2.3 → yjcli-0.2.4}/src/yjcli/data/skills/yj-frontend/SKILL.md

@@ -24,7 +24,7 @@ frontend/
   {app_name}/
     src/
       main.tsx, App.tsx          # entry
-      stores/{feature}/          # flow state/orchestration
+      stores/{feature}.ts        # flow state/orchestration
       api/{feature}/             # flow API access/mapping
       pages/{feature}/           # container view
       components/{feature}/      # presentational view
@@ -37,7 +37,7 @@ One `{app_name}` = one web app. No micro-frontends unless the user requests it.
 
 ```text
 entry = src/main.tsx, src/App.tsx (routes)
-flow  = stores/{feature} + api/{feature}
+flow  = stores/{feature}.ts + api/{feature}
 view  = pages/{feature} + components/{feature} (+ generated ui primitives)
 infra = lib/*, hooks/*
 ```
@@ -56,6 +56,8 @@ Missing domain ≠ dump DTOs/utils into `main.tsx` / `App.tsx`. Keep feature wor
 - Follow `yj-arch-core` env names; listen apps need `HOST`/`PORT`. No plain `.env`.
 - `npm start` / local mode must mean local-dev — do not silently point bare start at development/production deploy envs.
 - Store calls the same feature's `api`; pages/components do not call network directly.
+- Keep one store file per feature directly under `stores/`; do not add a
+  redundant `{feature}/` directory for a single store file.
 - Container route wires store + router; presentational page takes props only.
 - Routes declared at entry — do not scatter route tables; entry stays registration-thin.
 - Generated UI primitives: do not hand-edit or duplicate.

{yjcli-0.2.3 → yjcli-0.2.4}/src/yjcli/data/skills/yj-mobile-app/SKILL.md

@@ -21,9 +21,9 @@ mobile-app/
   {app_name}/
     lib/
       main.dart, router.dart       # entry
-      providers/{feature}/         # flow state/orchestration
-      repositories/{feature}/      # optional flow data-source composition/mapping
-      api/{feature}/               # infra remote clients
+      providers/{feature}.dart     # flow state/orchestration
+      repositories/{feature}.dart  # optional flow data-source composition/mapping
+      api/{feature}.dart           # infra remote client
       screens/{feature}/           # container view
       widgets/{feature}/           # presentational view
       lib/ or core/                # infra
@@ -35,9 +35,9 @@ One `{app_name}` = one mobile service.
 
 ```text
 entry = main + router
-flow  = providers/{feature} + repositories/{feature}
+flow  = providers/{feature}.dart + repositories/{feature}.dart
 view  = screens/{feature} + widgets/{feature}
-infra = api/{feature} clients + shared clients/formatters/utils
+infra = api/{feature}.dart clients + shared clients/formatters/utils
 ```
 
 Flow and view use the same `{feature}` boundary under separate role roots. A
@@ -45,7 +45,7 @@ feature repository belongs to flow, not beside `screens/` or `widgets/` as a
 view-level module.
 
 Use a repository only when it composes data sources, cache, mapping, or feature
-IO. A thin remote transport client belongs under `api/{feature}/` as infra; do
+IO. A thin remote transport client belongs at `api/{feature}.dart` as infra; do
 not add a repository that merely forwards every API call.
 
 **No `lib/domain/` by default.** Feature rules live in providers (flow).  
@@ -58,6 +58,8 @@ Missing domain ≠ put feature logic in `main.dart` / router registration.
 - Provider calls its feature repository when composition is needed; otherwise
   it may call the feature `api` directly. Widgets do not call repositories or
   network clients directly.
+- Keep one file per feature directly under `providers/`, `repositories/`, and
+  `api/`; do not add a redundant `{feature}/` directory for a single file.
 - Container screen watches providers and passes plain props to presentational widgets.
 - Routes declared at entry (thin); feature work stays in providers/api.
 - Prefer symlink/consume `backend/proto/dist/dart` for MSA contracts when present. Do not copy `.proto` into the app.