agentleFS
4gray4gray/iptvnator/.agents/skills/iptvnator-ui-design/SKILL.md

iptvnator-ui-design

Skill7.6k starsChanged 6 days agoMITView on GitHub

Use when changing user-visible Angular UI in IPTVnator, especially channel rows or lists, EPG views, settings and playlist surfaces, selection states, shared portal components, or light/dark styling.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before adding local markup, inspect @iptvnator/ui/components, @iptvnator/ui/epg, @iptvnator/ui/playback, @iptvnator/ui/shared-portals, …

    line 17
  2. Distinctive:

    Prefer dense, scannable application UI.

    line 26
  3. Distinctive:

    Do not extend the known hard-coded EPG/surface styling debt.

    line 29
  4. Distinctive:

    Run the focused component/unit target and the closest Playwright workflow for a visible change.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

IPTVnator UI Design

Inspect First

  • Policy: docs/architecture/iptvnator-ui-guidelines.md
  • Theme and navigation: apps/web/src/m3-theme.scss, libs/ui/styles/_nav-list.scss
  • Channel row: libs/ui/components/src/lib/channel-list-container/channel-list-item/
  • Shared EPG timeline/list: libs/ui/epg/src/lib/epg-timeline/, libs/ui/epg/src/lib/epg-list-view/

Before adding local markup, inspect @iptvnator/ui/components, @iptvnator/ui/epg, @iptvnator/ui/playback, @iptvnator/ui/shared-portals, @iptvnator/portal/shared/ui, and @iptvnator/playlist/shared/ui. Stateful collection loading, persistence, and cross-provider orchestration belong in @iptvnator/portal/shared/data-access, not UI or util.

Design Contract

  • Prefer dense, scannable application UI. Behavior-only work must not include an opportunistic visual rewrite.
  • App chrome uses app-owned selection, surface, and text tokens in both themes. Do not extend the known hard-coded EPG/surface styling debt.
  • Dense rows use minimum dimensions rather than a fixed width: the text column needs min-width: 0 plus ellipsis, while logos and trailing actions use flex-shrink: 0.
  • Assign one scroll owner per pane. Preserve sticky controls, keyboard/focus feedback, and loading, empty, error, disabled, hover, and selected states.
  • Providers supply controlled data to shared EPG timeline/list/panel components instead of rebuilding those views.
  • Shared changes require checking every affected M3U, Xtream, Stalker, workspace, and collection consumer in light and dark themes.
  • <mat-icon> names must exist in the bundled Material Icons font; pnpm run styles:icon-ligatures:validate checks them (UI guidelines, Icon Names).

Validation

Run the focused component/unit target and the closest Playwright workflow for a visible change. Electron CDP is a fallback for Electron-only gaps, not a replacement for an available E2E flow. Record any uncovered visual state. A change that adds backdrop-filter, filter, animations or a rounded scroller also runs pnpm run perf:compositing (see the theme/style skill's Rendering Cost section) and quotes the numbers.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 3 mentionsJul 2026: 0 mentionsAug 2026: 1 mentionSep 2026: 2 mentionsOct 2026: 3 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the 4gray/iptvnator repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about 4gray/iptvnator

The biggest 5 of 25 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 25

Talked about on GitHub, Bluesky and Stack Overflow (25 times).

On GitHub · 19

14 more on GitHub

On Bluesky · 5

On Stack Overflow · 1

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.