docs: DevLogUI 아키텍쳐 하네스 반영

Author: opficdev

.hermes/skills/devlog-architecture-harness/SKILL.md

@@ -74,8 +74,9 @@ Ask the user before editing when:
 - Core vs Domain ownership is unclear.
 - A shared type is being moved only because multiple modules need access.
 - Firebase/Auth/Firestore/Functions/Messaging-specific logic would leave Infra.
-- WidgetCore would depend on Domain, Data, Infra, Persistence, Presentation, or App.
-- Presentation would depend on Data, Infra, Persistence, or App.
+- WidgetCore would depend on Domain, Data, Infra, Persistence, Presentation, UI, or App.
+- Presentation would depend on UI, Data, Infra, Persistence, or App.
+- UI would depend on Domain, Core, Data, Infra, Persistence, or App.
 - Data would gain concrete SDK or storage implementation details.
 - The Presentation `Store` flow or reducer responsibility would change.
 - A compile fix requires relaxing the intended architecture.

.hermes/skills/devlog-architecture-harness/references/devlog-architecture-flow.md

@@ -73,7 +73,8 @@ flowchart TD
 ```mermaid
 flowchart TD
 	App["DevLogApp\nComposition root\nApp lifecycle\nAssembler wiring"]
-	Presentation["DevLogPresentation\nSwiftUI views\nViewModels\nCoordinators\nUI state"]
+	UI["DevLogUI\nSwiftUI views\nReusable components\nView composition"]
+	Presentation["DevLogPresentation\nStore\nViewModels\nCoordinators\nUI state"]
 	Domain["DevLogDomain\nEntities\nRepository protocols\nUse cases"]
 	Data["DevLogData\nRepository implementations\nDTOs\nMappers\nService/store protocols"]
 	Infra["DevLogInfra\nFirebase\nSocial login\nNetwork\nLink metadata\nMessaging"]
@@ -83,13 +84,16 @@ flowchart TD
 	WidgetExtension["DevLogWidgetExtension\nWidgetKit UI\nProviders\nTimelines"]
 
 	App --> Presentation
+	App --> UI
 	App --> Domain
 	App --> Data
 	App --> Infra
 	App --> Persistence
 	App --> Core
 	App --> WidgetCore
 
+	UI --> Presentation
+
 	Presentation --> Domain
 	Presentation --> Core
 
@@ -114,13 +118,14 @@ flowchart TD
 | Layer | Owns | Allowed direction | Ask before |
 | --- | --- | --- | --- |
 | `DevLogCore` | DI primitives, logger, shared value/query types, widget snapshot values | No DevLog layer dependency | Moving domain entities into Core |
-| `DevLogDomain` | entities, repository protocols, use cases | Core only | Adding Data, Infra, Persistence, Presentation, App, Widget UI, or SDK dependency |
+| `DevLogDomain` | entities, repository protocols, use cases | Core only | Adding Data, Infra, Persistence, Presentation, UI, App, Widget UI, or SDK dependency |
 | `DevLogData` | repository implementations, DTOs, mappers, data protocols | Domain, Core | Adding concrete Firebase, WidgetKit, storage, or platform implementation details |
 | `DevLogInfra` | Firebase, social login, network, metadata, messaging implementations | Data, Core | Moving SDK-specific behavior out of Infra |
 | `DevLogPersistence` | local stores, image cache, widget snapshot persistence | Data, Core, WidgetCore | Moving domain logic or remote SDK behavior into Persistence |
-| `DevLogPresentation` | UI, view models, coordinators, presentation state | Domain, Core | Adding Data, Infra, Persistence, or App dependency |
+| `DevLogPresentation` | Store, view models, coordinators, presentation state | Domain, Core | Adding UI, Data, Infra, Persistence, or App dependency |
+| `DevLogUI` | SwiftUI views, reusable UI components, view composition | Presentation | Adding Domain, Core, Data, Infra, Persistence, or App dependency |
 | `DevLogApp` | composition root, lifecycle, assembler wiring | Concrete app layers | Moving feature logic into App |
-| `DevLogWidgetCore` | widget data contracts and pure snapshot logic | Core | Adding Domain, Data, Infra, Persistence, Presentation, or App dependency |
+| `DevLogWidgetCore` | widget data contracts and pure snapshot logic | Core | Adding Domain, Data, Infra, Persistence, Presentation, UI, or App dependency |
 | `DevLogWidgetExtension` | WidgetKit rendering and timeline plumbing | WidgetCore | Calling app/domain services directly |
 
 ## Presentation Store flow
@@ -159,6 +164,7 @@ flowchart TD
 	Shared{"Moved only because shared?"}
 	NewDependency{"New module dependency?"}
 	ExternalSDK{"External SDK crosses layer?"}
+	UIBoundary{"UI sees Domain/Core/Data/Infra/Persistence/App?"}
 	WidgetBoundary{"WidgetCore sees app/domain/data?"}
 	BuildShortcut{"Build fix relaxes boundary?"}
 	ScopeDrift{"Outside current task scope?"}
@@ -173,7 +179,9 @@ flowchart TD
 	NewDependency -->|Yes| Ask
 	NewDependency -->|No| ExternalSDK
 	ExternalSDK -->|Yes| Ask
-	ExternalSDK -->|No| WidgetBoundary
+	ExternalSDK -->|No| UIBoundary
+	UIBoundary -->|Yes| Ask
+	UIBoundary -->|No| WidgetBoundary
 	WidgetBoundary -->|Yes| Ask
 	WidgetBoundary -->|No| BuildShortcut
 	BuildShortcut -->|Yes| Ask

AGENTS.md

@@ -43,13 +43,14 @@ Treat this repository as an Xcode workspace-based modular iOS app. There is no r
 ### Current layer map
 
 - `Application/DevLogCore`: shared app primitives such as DI, logging, query/value types, display options, and widget snapshot value types. Core is shared, but shared access alone is not enough reason to move domain entities into Core.
-- `Application/DevLogDomain`: entities, repository protocols, use case protocols, and use case implementations. Domain may depend on Core. Domain must not depend on Data, Infra, Persistence, Presentation, App, Widget extension UI, Firebase SDKs, or storage implementations.
+- `Application/DevLogDomain`: entities, repository protocols, use case protocols, and use case implementations. Domain may depend on Core. Domain must not depend on Data, Infra, Persistence, Presentation, UI, App, Widget extension UI, Firebase SDKs, or storage implementations.
 - `Application/DevLogData`: repository implementations, DTOs, mappers, data-layer protocols for external services/stores, and widget sync coordination. Data may depend on Domain and Core. Data should not gain direct Firebase, GoogleSignIn, WidgetKit, or concrete storage implementation details unless the user explicitly approves the boundary change.
 - `Application/DevLogInfra`: Firebase, social login, network, link metadata, messaging, and platform service implementations. Infra may depend on Data and Core. Firebase/Auth/Firestore/Functions/Messaging-specific behavior belongs here unless the user approves another boundary.
 - `Application/DevLogPersistence`: local persistence, user defaults, image store, and widget snapshot persistence/updating. Persistence may depend on Data, Core, and WidgetCore when needed for snapshot persistence.
-- `Application/DevLogPresentation`: SwiftUI views, view models, coordinators, UI state structures, and presentation-only helpers. Presentation may depend on Domain and Core. It must not depend on Data, Infra, Persistence, or App.
+- `Application/DevLogPresentation`: Store, view models, coordinators, UI state structures, and presentation-only helpers. Presentation may depend on Domain and Core. It must not depend on UI, Data, Infra, Persistence, or App.
+- `Application/DevLogUI`: SwiftUI views, reusable UI components, and view composition. UI may depend on Presentation. It must not depend on Domain, Core, Data, Infra, Persistence, or App.
 - `Application/DevLogApp`: composition root, app lifecycle, app delegate, app-level routing, and assembler wiring. App may import concrete layers to assemble the dependency graph.
-- `Widget/DevLogWidgetCore`: widget snapshot models, factories, keys, app-group constants, and widget-only pure helpers. WidgetCore may depend on Core. It must not depend on Domain, Data, Infra, Persistence, Presentation, or App without explicit user approval.
+- `Widget/DevLogWidgetCore`: widget snapshot models, factories, keys, app-group constants, and widget-only pure helpers. WidgetCore may depend on Core. It must not depend on Domain, Data, Infra, Persistence, Presentation, UI, or App without explicit user approval.
 - `Widget/DevLogWidgetExtension`: WidgetKit UI, widget providers, entries, timelines, and extension resources. It should consume WidgetCore outputs rather than app/domain services directly.
 - `Firebase/functions`: TypeScript Cloud Functions. Deploy updated functions one by one separately.
 
@@ -68,6 +69,7 @@ Ask the user before editing when any of these are true:
 - A type could plausibly live in both Core and Domain.
 - A shared type is being moved only because multiple modules need access to it.
 - A new target dependency would make a lower-level module know a higher-level module.
+- UI would start depending on Domain, Core, Data, Infra, Persistence, or App.
 - A build fix would be achieved by loosening an architecture boundary.
 - Firebase, GoogleSignIn, AuthenticationServices, UserNotifications, LinkPresentation, Network, WidgetKit, or storage implementation details would move to another layer.
 - A repository protocol, service protocol, assembler, or DI ownership boundary would change.

README.md

@@ -181,7 +181,8 @@ SwiftUI_DevLog/
 │	├── DevLogData/            # Repository 구현, DTO, Mapper, Data 계층 Protocol
 │	├── DevLogInfra/           # Firebase, 소셜 로그인, 네트워크, 메타데이터 서비스 구현
 │	├── DevLogPersistence/     # UserDefaults, 이미지 저장소, 위젯 스냅샷 영속성 처리
-│	└── DevLogPresentation/    # SwiftUI 화면, ViewModel, Store, Coordinator
+│	├── DevLogPresentation/    # ViewModel, Store, Coordinator, 화면 상태
+│	└── DevLogUI/              # SwiftUI 화면, 재사용 UI 컴포넌트
 ├── Widget/
 │	├── DevLogWidgetCore/      # 위젯 스냅샷 모델, Factory, App Group 상수
 │	└── DevLogWidgetExtension/ # WidgetKit UI, Provider, Timeline