leviFrosty

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.

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.

Rules for working with the Publisher role in WitnessWork — entry mode, goals, credit cap, milestone ladder, tenure display, and which sections render. Use whenever code reads or branches on a publisher/role, touches goals/credit-cap/milestones/tenure, gates UI by role, or adds a new role. CONTEXT.md has the role semantics; this is the code-level seam.

Refactor an existing TypeScript project to the lattice feature-folder architecture with enforced boundaries, using a TDD red-green-refactor discipline so behavior is preserved at every step. Use when a user wants to adopt the lattice structure, "features" folder structure, ESLint boundaries plugin, and full linting/format/test guardrails in an existing codebase.

Bootstrap a new TypeScript project with the lattice feature-folder structure and the ESLint `boundaries` plugin enforcing one-way imports — minimal dependencies only. Formatter, git hooks, test runner, and parallel runner are all opt-in. Does NOT pull in Next.js, Tailwind, React, or any UI dependencies. Use when a user wants the lattice structure on a clean slate for a framework-agnostic project (CLI, library, server, etc.).

Walk the user through creating a `work.yml` smug config for the current project so they can launch their full dev workstation (any GUI startup programs they want — editor, browser tabs, design tools, etc. — plus tmux panes with all dev servers) with a single `work` command. Terminal- and OS-agnostic: asks the user what they actually use rather than assuming. Use when invoked via /create-work-yml, when the user asks to set up `work` for a project, or when they say their `work.yml` is missing.