sehyun0518

lynx-api-docs

Provides authoritative guidance for Lynx development involving pages, templates, components, CSS, layouts, elements, web migration, rendering or styling bugs, and code review. Applies to *.ttml, Lynx *.tsx, and all Lynx-specific files, and requires searching the installed API docs before acting.

lynx-typescript

This Skill summarizes common TypeScript issues and their solutions in Lynx development, mainly covering environment configuration, type extending, event handling, components, and ReactLynx advanced usages. Trigger Scenarios: - User inputs TypeScript error messages related to Lynx and seeks fix suggestions - LSP diagnoses Lynx-related TypeScript errors, proactively invoke query to get fix solutions - User asks about TypeScript best practices or common errors related to Lynx, proactively invoke query to provide guidance - User requests to configure the TypeScript environment of the current project to support Lynx development, proactively invoke query to provide configuration steps

reactlynx-best-practices

ReactLynx dual-thread best practices for writing, reviewing, and refactoring Lynx components. Use when working with ReactLynx code — background-only directives, main-thread scripts, bindtap/catchtap events, runOnMainThread/runOnBackground, lazy/Suspense, globalPropsMode, component-library packaging, or render/diff/commit performance traces. Triggers on tasks involving Lynx, ReactLynx, or @lynx-js/react.

Data & Documents Listed

rspeedy-bundle-size

Analyze and reduce the bundle size of rspeedy/Lynx (ReactLynx) apps — the size / `.lynx.bundle` lever (not runtime perf, types, or CI). Use when the user wants to optimize 包体积 / bundle size, find what is making a rspeedy bundle large, decide which size lever to pull, or shrink `main-thread.js` by stripping background-only code (jsb / telemetry / request / monitor SDKs) out of the render path via `__BACKGROUND__` / `'background only'` gating. Covers media, JS-background, and main-thread layers, plus mangle/eval-poisoning bloat, i18n-locale duplication, duplicate-package dedup, extractStr/compile knobs, and lazy/dynamic-component splitting (first-screen vs total size). Measure-first and evidence-based — produces a prioritized report; changes code only when asked.

AI & Automation Listed

vanilla-lynx

Build Rspeedy Vanilla Lynx apps with Element PAPI and Lynx Runtime APIs, never ReactLynx or JSX. Use for project scaffolding, main-thread UI, lifecycle/events, background communication, styling, or external bundles. Do not use for device-side runtime validation or debugging of an already built artifact; use lynx-devtool instead. For general APIs use lynx-api-docs; for ReactLynx use reactlynx-best-practices; for bundle quality use rspeedy-bundle-quality. Excludes Element PAPI JSON mode and output formats outside the Rspeedy Vanilla Lynx workflow.

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

vercel-react-native-skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Testing & QA Listed

requirements-spec

프론트엔드 작업의 요구사항 스키마, 완결성 판정 기준, 스펙(계약) 문서 포맷의 단일 출처. 요구사항을 구조화·검증·이관하거나, 스펙을 채우거나 읽거나, 요구사항이 충분한지 판정해야 할 때 반드시 이 스킬을 참조한다. 논의 에이전트(스펙 채우기)와 오케스트레이터(스펙 읽기·완결성 게이트), 피드백 레이어(수용 기준 검증)가 공유한다. "요구사항 스키마", "수용 기준", "스펙 포맷", "완결성 검사", "작업 명세 이관", "스펙으로 정리" 같은 맥락이 나오면 명시적으로 스킬을 언급하지 않더라도 이 스킬을 참조한다.