← Work02 / 132026

Private Tooling

Personal Skin Manager

Private Windows tooling where League integration, packaging, compatibility, provenance, and in-game QA are treated as one system.

Role
Personal build · Integration · QA
Status
Private active development
Stack
Python · PyInstaller · League/LCU · Pengu · CSLOL
Provenance
Derived from open-source Rose · private personal tooling

Personal Skin Manager is a private personal build derived from the open-source Rose project. The work focuses on League/LCU state, skins and chromas, custom mods, Pengu and CSLOL tooling, local archives, monitoring and synchronization, packaging, diagnostics, compatibility, and manual in-game verification while preserving clear upstream provenance.

02 / Private ToolingPersonal Skin ManagerPrivate active development · 2026

00 / System

How the work connects.

  1. 01League / LCU
  2. 02Skins
  3. 03Chromas
  4. 04Custom mods
  5. 05Pengu
  6. 06CSLOL
  7. 07Packaging
  8. 08QA
01Provenance

The underlying project is not presented as original work from scratch.

Rose remains explicit upstream provenance. The portfolio focuses on the personal engineering layered around the build: controlled dependencies, packaging, integrations, state handling, diagnostics, compatibility work, local tooling, and QA.

02Integration

The difficult work is the runtime around the content, not simply listing skins.

League/LCU state, skin and chroma selection, custom mods, Pengu Loader, CSLOL tooling, local archives, injection/runtime files, monitoring, and synchronization have to agree across development and packaged builds.

03Diagnostics

Dynamic skins make the boundary between UI state and game content visible.

Focused archive audits and form/native-state testing separate what the Python/UI layer can control from behavior embedded in the actual game content. Some dynamic behavior can be verified and switched; other skins remain limited by their native content rather than being falsely represented as fully controllable.

04Verification

Packaging and local runtime dependencies are part of the test surface.

PyInstaller builds, Pengu/CSLOL dependencies, diagnostics, runtime-file checks, and manual in-game QA are tested as one delivery surface. User-local League runtime dependencies are kept local and are not presented as redistributable public bundle content.