post-for-me

Open a high-quality pull request for the post-for-me monorepo and wire it to its Linear issue. Use this skill whenever the user wants to open/create/raise a PR, "put this up for review", push a branch for review, or finalize a change for merge — even if they don't say the words "pull request". It covers branch naming (feat/fix/chore), the PR body template, tagging the Linear issue in the body so it auto-closes on merge, and auto-attaching the PR link to the Linear issue via the Linear MCP. Reach for it any time work is ready to become a PR.

Apply Post for Me's conversion-tracking conventions to any change that touches user/team lifecycle, billing, signup, the Stripe webhook, PostHog/Meta/Google integrations, or anything under `app/tracking/`. Use this skill whenever adding/modifying analytics events, working with PostHog identify/group calls, handling Stripe webhook events, building checkout or billing flows, wiring ad attribution, or adding any new user-lifecycle moment that might be worth tracking. Reach for it any time someone says "track this", "add a posthog event", "log this conversion", "do we capture X anywhere", or "should we be tracking…" — even if the word "conversion" isn't said. Default to firing when in doubt; under-tracking is the failure mode this skill exists to prevent.

Explains this repo's non-workspace "dumb monorepo" layout and the iron rule that every build/test/lint/typegen/package command runs from inside a sibling directory — never the repo root. Use BEFORE running any bun/npm/supabase/trigger/shadcn command, before installing or adding a dependency, before generating DB types, or whenever a skill or task says to "run X" without naming a directory. Reach for it any time you're about to shell out a command in this repo and aren't certain which directory it belongs in, or when a command fails with "no package.json / no lockfile / script not found" at the root.

Animate UI with Motion (the library formerly named Framer Motion, npm package `motion`) in this project's React Router v7 apps — primarily marketing/. Use when adding or editing any animation, transition, scroll effect, gesture (hover/tap/in-view), layout/shared-element animation, or enter/exit transition; when importing `motion`, `AnimatePresence`, `useScroll`, `useTransform`, `useReducedMotion`, etc.; or when reviewing animation code for correctness, performance, or reduced-motion support. Covers our import convention, SSR setup, the core API, performance rules, and accessibility. This is a thin in-house summary of the public Motion docs (motion.dev) — verify against the live docs for anything beyond the basics.

Add or modify routes in this project's React Router v7 apps — both dashboard/ and marketing/. Use when creating a new page, layout, resource/api route, or modifying any folder under dashboard/app/routes/ or marketing/app/routes/. Covers the shared modular route architecture (route.ts barrel + route.component/loader/action/meta/handle), flat-routes folder-name → URL conventions, the per-app overlays (marketing: MetadataComposer + sitemaps, read-only; dashboard: actions, auth layouts, route.handle), and common gotchas. This is the project-specific contribution layer on top of the generic react-router-framework-mode skill.

Use when adding a new social media platform to post-for-me. Covers implementing a PostClient subclass in trigger/posting/platforms/, adding a Configuration type to post.types.ts, updating post-client.ts, and documenting options in api/src/social-posts/dto/post-configurations.dto.ts.