Iptvnator Nx Architecture
Developmentiptvnator-nx-architectureIptvnator Nx Architecture is an Agent Skill for development published in the 4gray/iptvnator repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Repository-specific Nx monorepo structure, library placement rules, scoped path aliases, and migration guardrails for portal/workspace/app code.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/4gray/iptvnator/blob/HEAD/.codex/skills/iptvnator-nx-architecture/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/iptvnator-nx-architecture, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
IPTVnator Nx Architecture
Use this skill when deciding where code belongs, extracting libraries, changing imports, editing project tags, or refactoring portal/workspace/app boundaries.
Project Shape
apps/web: Angular renderer application.apps/electron-backend: Electron main process and native/runtime integration.apps/*-e2e: Playwright E2E projects.apps/*-mock-server: local development and E2E mock servers.libs/playlist/*: M3U/import/shared playlist functionality.libs/portal/*: Xtream, Stalker, and provider-neutral portal functionality.libs/workspace/*: workspace shell and dashboard.libs/ui/*: provider-neutral UI, playback, EPG, remote control, and pipes.libs/shared/*: contracts, database, and pure utility code.
Import Policy
- Use scoped aliases from
tsconfig.base.json, for example@iptvnator/servicesand@iptvnator/shared/interfaces. - Do not reintroduce legacy bare aliases such as
services,components, orshared-interfaces. - Prefer library public APIs (
src/index.ts) over deep imports unless a sub-entrypoint is explicitly configured. - Keep app-only code in
apps/*; shared behavior belongs in a domain library.
Tag Policy
- Every project should have
scope:*,domain:*, andtype:*tags. - Use
type:featurefor route/component orchestration,type:data-accessfor stores/API/persistence,type:uifor reusable components, andtype:utilfor pure helpers/contracts. - Keep
type:data-accessfrom depending ontype:featureortype:ui. - Add or update
@nx/enforce-module-boundariesconstraints when introducing new tag families.
Validation
pnpm nx show projects
pnpm nx lint <project>
pnpm nx test <project>
When dependencies are not installed in a fresh worktree, run pnpm install --frozen-lockfile first.