What problem does it solve? Engineers working in this monorepo need consistent patterns for service layout, dependency keys, imports, RPC streams, tests, exports, and component styling, and this Skill encodes those conventions as concrete good/bad examples. ## Core Features & Use Cases - Service and App Layout Rules: Defines the exact file structure for packages (schema.ts, service.ts, lib/, internal/) and apps (rpcs/, services/, main.server.ts, main.client.tsx). - Effect and RPC Conventions: Specifies Context.Service key naming (@deslop/<package>/<path>), RpcGroup contracts with streaming, AtomRpc clients, and it.layer test patterns. - Tooling and UI Standards: Covers subpath import maps, package exports, root-owned dependencies, vp generators, oxlint/fallow enforcement, and flat monospace shadcn component styling. - Use Case: When adding a new service to packages/ai or a new app under apps/, apply this Skill to produce code that matches the repository's enforced structure and passes its lint and dead-code checks. ## Quick Start Apply the project-engineering skill to scaffold a new Effect service in this repository following its layout, key, and testing conventions.