unitism

Use this skill when the user pastes a cross-repo handoff message originating from the `non-engineer-frontend-contribution` skill. Triggers specifically on messages containing the header "## Cross-repo change requested" or the block "## Paste-ready brief for Claude Code", or on pastes that start with "I need to add a backend change to support a frontend PR that's waiting." Also triggers when the user pastes any message that names a frontend PR URL from `tennis-miami-web`, `arenna-link`, or `tennis-miami` and asks for a matching backend change. This skill parses the message, identifies the target repo, creates a branch from `development`, implements the specified change, opens a PR back to `development` linked to the originating frontend PR, and — on merge — generates a notification message for the original requester (Asad or Kath). Installed on Yuval's and Yudi's Claude Code only. Do NOT trigger on general feature requests unconnected to a non-engineer handoff, on discussions about the handoff flow itself, or on frontend-only changes.

Use this skill whenever the user is contributing to the frontend of `arenna-link`, `tennis-miami`, or `tennis-miami-web`. Triggers on any UI change (buttons, forms, layout, colors, spacing, icons), copy or text changes, design tweaks, or bug fixes visible to users. Also triggers on requests phrased as "I want to change...", "fix the...", "update the...", "the landing page needs...", or similar, when the session is in one of those three repos or mentions them by name. This skill keeps the person on a safe branch off `development`, auto-writes commits, and runs scope / secret / out-of-scope checks before opening a PR. It also generates paste-ready handoff messages when a change requires a different repo (backend, agent-server). Do NOT trigger on backend repos (`unitism-backend`, `arenna-backend`, `arenna-agent-server`), on Flutter/Dart business-logic changes that are not UI-visible, on CI / deploy / infrastructure config, or on documentation-only changes. Intended for team members whose primary role is not engineering (e.g., UX design, customer success) — engineers working in these repos can say "I'll handle this manually, skip the rails" to opt out mid-session.

Use this skill whenever a change is being made to a primary surface in a UNITISM consumer-facing repo (`tennis-miami`, `tennis-miami-web`, `arenna-link`, or future consumer apps on the platform). Primary surfaces include: bottom navigation / tab bar, the first screen shown after login or signup, the onboarding or signup flow's headline / primary CTA, the app store listing copy, the marketing site hero or top-level navigation, the home tab's empty state, and the first push notification copy sent to a new user. Triggers on diffs that add, remove, rename, reorder, or re-label items on these surfaces; on copy changes to hero headlines, CTAs, or onboarding text; on icon or label changes for nav tabs; and on any request phrased as "add X tab", "show Y on home", "rename the Z tab", "change the hero", or similar primary-surface language. Also triggers when a backend or features-only change introduces a new user-facing surface that will need primary-surface placement (e.g., a new entitlement that implies a new tab). The skill checks the change against `_shared/strategy/product-positioning-principles.md`, identifies which product's positioning applies (Tennis Miami → community-first; ARENNA → instructor-first), runs the primary-surface decision test, and outputs a flag-with-reasoning + a suggested non-primary alternative when the change risks shifting the product's perceived category. Do NOT trigger on backend-only changes with no user-visible surface, on internal tooling, on test files, on lockfiles, on changes confined to non-primary surfaces (account/settings/profile sub-views), or on changes to internal product or strategy docs. Engineers can opt out for a single change by saying "skip the positioning check — I've thought about it."

Use this skill whenever the user is working on `unitism-backend` — adding, modifying, or removing endpoints under `/api/v1/*`, creating or editing modules, writing TypeORM migrations or entities, changing DTOs or response shapes, modifying database triggers, or touching authentication, units, projects/holons, payments, or any cross-cutting platform module. Triggers on requests phrased as "add an endpoint for...", "the backend needs to support...", "modify the X module", "update the X entity", "create a migration for...", "fix the payment / auth / units bug", or any session where the working directory is `unitism-backend` or where files under its `src/` are being edited. Also triggers when a `cross-repo-handoff-message` paste asks for a backend change in `unitism-backend`. The skill enforces: COMPONENTS.md / API_GUIDE.md / PROTECTED.md as the canon, the `/api/v1/*` versioning contract, attribute inheritance via DB triggers, the no-breaking-changes rule, TDD red→green→refactor, event-table logging for every mutation, and — critically — cross-client verification before declaring done (web AND mobile, not just one). Do NOT trigger on frontend-only changes (those go to `non-engineer-frontend-contribution`), on infrastructure or CI changes, or on documentation-only edits. For ARENNA cross-repo features that touch `unitism-backend` AND `arenna-agent-server` AND `sessionizer` in one flow, this skill runs for the `unitism-backend` portion only.