compact-tv-check
Check code for Chromium 70 and TV platform compatibility issues (CSS, JS, APIs). Use when the user wants to verify code will work on target TV platforms.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- compact-tv-check
- tags
- [ "smarttv", "compatibility", "chromium", "tizen", "webos" ]
- type
- skill
- agents
- [ "claude", "codex", "cursor", "gemini", "copilot" ]
- author
- Aliendreamer
- version
- 0.1.0
- description
- Check code for Chromium 70 and TV platform compatibility issues (CSS, JS, APIs). Use when the user wants to verify code will work on target TV platforms.
- user-invocable
- true
- disable-model-invocation
- false
03 SKILL.md 正文
TV Compatibility Check
Check code for compatibility issues with Chromium 70, Tizen, LG webOS, and Hisense TV platforms.
Input: File path, directory, or glob pattern. If omitted, ask.
Steps
-
Resolve the target
If no path provided, use AskUserQuestion to ask:
"Which file or directory do you want to check? You can provide a path or glob (e.g. src/components/)."
Read all matching files. For directories, scan for
.tsx,.ts,.cssfiles. -
CSS Compatibility Checks (scan
.css,.module.css, Tailwind classes in JSX)Flag any use of:
Feature Issue Fix clamp()Not in Chrome 70 (added 79) Use calc() with min/max JS fallback min()/max()Not in Chrome 70 (added 79) Use calc() or JS aspect-ratioNot in Chrome 70 (added 88) Use padding-top % hack gapon flexboxNot in Chrome 70 (added 84) Use margins or column-gap/row-gapon grid:focus-visibleNot in Chrome 70 (added 86) Use :focusscroll-snap-*Unreliable in Chrome 70 Use JS scroll management subgridNot supported Use nested grids backdrop-filterNot in Chrome 70 (flag-only in Chrome 70, stable later) Avoid — not in Chrome 70 content-visibilityNot in Chrome 70 (added 85) Remove or polyfill @containerqueriesNot in Chrome 70 (added 105) Use media queries color-mix()Not in Chrome 70 Use static colors overflow: clipNot in Chrome 70 Use overflow: hiddenAlso check Tailwind utility classes that map to unsupported CSS - e.g.
aspect-*,gap-*on flex,focus-visible:*. -
JavaScript / TypeScript Compatibility Checks
Flag any use of:
Feature Issue Fix ?.optional chainingES2020 - needs Babel transpile Verify tsconfig target / Next.js transpiles this OK ??nullish coalescingES2020 - needs transpile Same - verify transpilation ??=/&&=/||=logical assignmentES2021 Needs transpile Array.at()Not in Chrome 70 Use bracket notation Object.hasOwn()Not in Chrome 70 (added 93) Use Object.prototype.hasOwnProperty.call()structuredClone()Not in Chrome 70 (added 98) Use JSON parse/stringify or lodash cloneDeep crypto.randomUUID()Not in Chrome 70 (added 92) Use a uuid library queueMicrotask()Not in Chrome 70 (added Chrome 71) Needs polyfill Promise.allSettled()Not in Chrome 70 (added Chrome 70) Needs polyfill globalThisNot in Chrome 70 (added Chrome 71) Needs polyfill Dynamic import()OK in Chrome 70 Fine AbortControllerOK in Chrome 70 Fine ResizeObserverOK in Chrome 70 Fine IntersectionObserverOK in Chrome 70 Fine -
Browser API Checks
Flag use of APIs unavailable or unreliable on TV browsers:
API Issue localStorage/sessionStorageMay be restricted or quota-limited on some TVs - handle errors IndexedDBAvailable but may be slow - verify with try/catch navigator.userAgentfor TV detectionUnreliable - use feature detection instead window.screen.width/heightMay not reflect TV resolution accurately navigator.connectionNot available in Chrome 70 Web Animations APIPartially available - verify Pointer Lock API Not relevant/available on TVs devicePixelRatio> 1TV is always 1:1 - safe to assume -
Next.js / RSC Checks
'use client'directives: verify they are placed correctly (top of file, before imports)- Browser APIs (
window,document,localStorage) used in Server Components - flag these useEffect/useStateused without'use client'- flagnext/imageusage: verify TV-appropriatesizesand no layout shift
-
Report findings
Format:
## TV Compatibility Report: <path> ### Summary Files checked: N Issues found: N (X critical, Y warnings) ### Critical Issues (will break on Chromium 70) - [file:line] `clamp(...)` - not supported in Chrome 70. Fix: use calc() instead. ### Warnings (may cause issues) - [file:line] `localStorage` without error handling - may fail on Tizen. ### Info (verify these) - [file:line] Optional chaining `?.` - confirm Next.js transpiles to ES5 target. ### Clean - No CSS compatibility issues found in: ... -
Offer to fix
After the report, ask:
"Want me to fix the critical issues?"
Fix only what's reported. Do not refactor unrelated code.
Guardrails
- Flag, don't auto-fix without confirmation
- Note when Next.js/Babel transpilation likely handles an issue (mark as Info not Critical)
- For Tailwind: check the generated CSS meaning, not just class names
- Do not flag things that are genuinely supported in Chrome 70
04 同仓库更多 Skills
setup-git-credentials
Use when the user wants Git to stop using a PAT in the remote URL or a plain-text credential store, wants Git Credential Manager (GCM) with OAuth for GitHub, GitLab or Azure DevOps on Ubuntu/Debian or WSL2, or sees 'cannot persist Microsoft authentication token cache securely' / 'using plain-text fallback token cache'. Asks whether this is WSL, which Git hosts and which parts to set up, checks what is already done, sets git config itself after confirmation and hands every sudo or interactive step (apt, gpg, pass init, secret-tool, first sign-in) to the user. Bundles gcm-keyring-session.sh to start or reuse a D-Bus + GNOME Keyring session without systemd. Trigger terms - git credentials, PAT in URL, token in remote, git credential manager, gcm, github auth, gitlab auth, azure devops auth, pass, gpg store, secret service, gnome keyring, msal token cache, wsl git auth.
setup-flow
Use when onboarding a repository or agent to the standard development workflow — installs the required skills from the ai.skills store, installs or updates a MANDATORY workflow block in the agent's instruction file (CLAUDE.md, AGENTS.md, GEMINI.md, Copilot or Cursor rules), AND configures .claude/settings.json with Serena MCP, sandbox, permissions, hooks, and plugins. Hooks are wired to the context-hooks kit, which speaks once per session instead of injecting text on every turn; re-running replaces earlier inline hooks rather than adding to them. Also writes .vscode/settings.json to hide the empty shell dotfiles an agent sandbox leaves in the repo root. Use when setting up a new repo, switching agents, or refreshing the workflow rules.
developer-flow
Use when starting, implementing, or completing any feature, change, or fix in any software project — at feature start, before writing code, and before claiming a change is done, fixed, working, or green. A strict ordered flow with a gate per phase; stack-agnostic and repo-agnostic (OpenSpec optional, gates discovered).
daily-log-check
Use to check whether everyone on duty filed their Azure DevOps time-log Tasks for a given day, per platform — reports tickets, hours and activities per person against the headcount you give. Fires on "did everyone log yesterday", "check web 4 mobile 3", "who is missing for 8.09", "daily log check". Read-only. Org and project come from configuration.
daily-activity-log
Use at end of day to file the Azure DevOps time-log Tasks — one closed Task per Activity worked that day, Original Estimate in decimal hours, parented to the current sprint's Feature. Fires on "log my day", "fill my tasks", "close my daily tasks", "I had 2h meetings and 4h development". Org and project come from configuration.
conventional-commits
Write commit messages that follow the Conventional Commits specification so tooling can derive versions and changelogs.