菜单
WitnessWork's three-tier feature architecture (app / features / shared) and its lint-enforced import boundaries. Use when adding or moving files, changing import lines, renaming folders under src/, deciding where new code lives, or resolving an eslint-plugin-boundaries violation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | project-architecture |
| description | WitnessWork's three-tier feature architecture (app / features / shared) and its lint-enforced import boundaries. Use when adding or moving files, changing import lines, renaming folders under src/, deciding where new code lives, or resolving an eslint-plugin-boundaries violation. |
Source lives in src/, organised into three tiers, enforced at lint time by eslint-plugin-boundaries:
src/app/ — app-tier infra: entry point, navigation, widgets, iCloud sync, deep links. May import from any tier.src/features/<domain>/ — one folder per domain (contacts, conversations, service-reports, map, milestones, supporter, profile, plans, progress, home, settings, updates, onboarding, …). Each holds the subset of screens/ components/ hooks/ lib/ stores/ types/ constants/ it actually needs. A feature may import from shared and itself only.src/components/ (ui/ primitives + root composed blocks), src/lib/, src/hooks/, src/stores/, src/types/, src/constants/, src/providers/, src/contexts/, src/assets/, src/locales/, src/shaders/, src/vendor/. Importable from anywhere; may only import from shared.Page-level orchestrators (home, settings, progress, plans, updates, onboarding) are classified as app in the boundaries config so they can compose across domains. home is a pure orchestrator — don't add components/hooks/lib under features/home/; put domain UI in the owning feature and import it.
Imports use the @/* alias (= src/*). Prefer @/features/... / @/app/... / @/components/... over relative paths.
pnpm run lint after import / file-tree changesTypeScript won't catch a boundary violation — only ESLint will. Run pnpm run lint after:
import line (it may cross a tier boundary).src/features/, src/app/, or src/components/.docs/project-structure.md — full directory map, one-line summary of every feature folder.docs/architecture-features.md — tier rules, boundaries lint config, why some features are classified as app, and the components/ui/ vs components/ (root) decision.How to write a WitnessWork PR description
WitnessWork's branching and release workflow — trunk-based on `main`, version bump + release notes via `pnpm run bump-version`, and what each GitHub Actions workflow does. Use when opening a PR, asking which branch to target, cutting a release/version bump, writing release notes, or touching `.github/workflows/*.yml`.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Submit a WitnessWork build to the App Store via the `asc` CLI — create a version, copy metadata, set "What's New", preflight, and submit. Use when releasing to the App Store / TestFlight, cutting a version, pushing release notes, or running App Store Connect operations (versions, metadata, screenshots, pricing, analytics).
Issue/PRD tracking and triage for WitnessWork via the `gh` CLI on leviFrosty/witness-work. Use when creating, reading, listing, commenting on, labeling, or closing GitHub issues, or when applying the repo's triage labels.
How to apply iOS 26 Liquid Glass material in WitnessWork — use `expo-glass-effect`'s GlassView, never hand-build glass from BlurView + opacity. Use when adding/reviewing material on nav bars, tab bars, sheets, primary CTAs, search, or floating overlays, or when you spot a hand-rolled blur/glass surface.