// Use when implementing or reviewing deeplinks, Open in App CTAs, dashboard shortcuts, and web-to-app handoff decisions across the AniTrend website.
| name | anitrend-ecosystem-awareness |
| description | Use when implementing or reviewing deeplinks, Open in App CTAs, dashboard shortcuts, and web-to-app handoff decisions across the AniTrend website. |
| argument-hint | Which route, CTA, or handoff path needs ecosystem-aware guidance? |
Use this skill when work touches the boundary between the AniTrend website and the native AniTrend app. It helps keep app handoff behavior discoverable, consistent, and measurable.
app.anitrend://...)src/config/links.ts
src/components/anime-analytics.tsx
open_in_appsrc/app/dashboard/page.tsx
Implementation-level route literals and per-surface details live in:
./references/website-surfaces.md./references/app-route-contract.md./references/app-route-contract.md for route confidence and caveats.src/config/links.ts rather than introducing new literals..github/instructions/deeplink-contract.instructions.md so emitting surfaces use the right element and migration rules../references/website-surfaces.md.Use when working autonomously in the AniTrend website repository and needing project-specific conventions, CI requirements, tool choices, or implementation patterns before making changes.
Use when implementing or reviewing Next.js App Router metadata, Open Graph, Twitter cards, and social preview consistency across AniTrend routes.
Use when extending AniTrend UI primitives with shadcn, cva, asChild, or Tailwind tokens instead of duplicating components or scattering raw classes.
Use when adding or editing Next.js App Router pages, React components, or Tailwind styles in the AniTrend website and you need guidance on server vs client boundaries, metadata, state placement, shadcn/ui reuse, or token-based responsive styling.