← all publishers

liberatedpixelcup

@liberatedpixelcup source repo

11 published skills

  1. Cls · liberatedpixelcup
    Measure lab CLS with profile:cls, debug layout shift from loading shells and first-paint jump, and keep budgets tied to a CI artifact. Use when editing first-paint CSS, loading shells, critical-shell, or when the user mentions CLS, layout shift, or Lighthouse.
    0
    installs
  2. Catalog · liberatedpixelcup
    Thread CatalogReader and State through Mithril attrs, never a hidden global. Handle Result/LoadError, seed test catalogs, and keep URL hashes stable. Use when adding or editing a component, a browser spec, or sources/state/ code, or when the user mentions catalog, state, hash, or aliases.
    0
    installs
  3. Coverage · liberatedpixelcup
    Run and read unit-test coverage for this repo and satisfy the codecov/patch and codecov/changes gates. Use when a PR check fails on coverage, after editing gated production code under sources/ or scripts/, or when the user mentions coverage, Codecov, patch, or uncovered lines.
    0
    installs
  4. Typescript · liberatedpixelcup
    Write TypeScript that satisfies this repo's lint and tsconfig rules, and convert an existing .js file to .ts without breaking its call sites. Use when adding or editing a .ts file, converting a .js file, adding the first .ts browser spec, or hitting a type-check or ESLint failure.
    0
    installs
  5. Write Spec · liberatedpixelcup
    Write a browser Mocha, Node, or Playwright visual spec for this repo. Use when adding a test, covering new production lines, or the user asks for a spec. New specs are TypeScript. Register browser specs in tests/tests.js.
    0
    installs
  6. Visual Test · liberatedpixelcup
    Run or add Playwright visual specs and know when a layout or CSS change needs npm run test:visual. Use after first-paint, panel-layout, or PurgeCSS safelist changes, or when adding a Playwright case.
    0
    installs
  7. Run One Spec · liberatedpixelcup
    Run a single Node, browser, or Playwright spec instead of the full suite. Use when debugging one test, iterating on a failing spec, or the user asks to run one file, one test, or a filtered suite. Do not start with npm test.
    0
    installs
  8. Canvas Render · liberatedpixelcup
    Change the offscreen renderer, palette recolor, z-position order, or magenta mask, and ask the user to check WebGL and the CPU fallback. Use when editing sources/canvas/, palette recolor, z-positions, or renderer output.
    0
    installs
  9. Sheet Definition · liberatedpixelcup
    Add or edit sheet_definitions JSON for items, categories, variants, credits, layers, or z-positions. Use when adding art, a new category, a credits entry, or renaming an asset. Copy a neighboring definition; do not invent keys.
    0
    installs
  10. Generated Metadata · liberatedpixelcup
    Diagnose missing or stale dist/*-metadata.js, the Vite metadata plugin cache, and the ../name-metadata.js import alias. Use when dist/ is missing, a catalog resolves nothing, a spec fails only locally, or editing the Vite metadata plugin. Do not hand-edit dist/ or add another metadata module.
    0
    installs
  11. Performance Profiling · liberatedpixelcup
    Run the headless app, catalog-load, and ZIP profilers and interpret the JSON the way a human would from window.profiler.report(), profile:load, and the ZIP console table. Use when editing sources/canvas/, load-image, renderer, zip export, zip-helpers, performance-profiler, install-item-metadata, loadAllMetadata, or when the user mentions performance, profiling, slow render, FPS, catalog load, or ZIP export timing.
    0
    installs