qol-shared-libs

Identify when plugin functionality should reside in shared libraries during development and code reviews.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/qol-tools/qol-skills --skill qol-shared-libs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qol-shared-libs
Source: https://github.com/qol-tools/qol-skills/tree/main/plugins/qol-dev-conventions/skills/qol-shared-libs
Command: npx skills add https://github.com/qol-tools/qol-skills --skill qol-shared-libs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Over time, plugins accumulate functionality that duplicates code, making maintenance harder and increasing the risk of inconsistency. This skill guides developers to move common capabilities into shared libraries to improve reuse and reduce fragility.

Core Features & Use Cases

  • Shared libraries like qol-plugin-api, qol-config, qol-platform, qol-runtime, qol-color, qol-search, qol-fx, qol-frecency provide common capabilities to multiple plugins.
  • Push order and contract validation rules enforce correct integration order and compatibility.
  • Real-world scenarios include migrating a feature from a plugin to a shared library when two or more plugins need it, ensuring consistency across the ecosystem.

Quick Start

Audit new plugin changes and migrate reusable functionality into the appropriate shared libraries before applying plugin edits.

Frequently Asked Questions about qol-shared-libs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I move plugin functionality into shared libraries?

Move plugin functionality into shared libraries when two or more plugins require the same capability to improve reuse and reduce fragility. This migration ensures consistency across the ecosystem and prevents duplicated code accumulation.

How do I audit new plugin changes for shared library migration?

Audit new plugin changes by identifying reusable functionality and migrating it into appropriate shared libraries before applying plugin edits. This ensures proper library placement for new capabilities across QoL plugins during development and code reviews.

What shared libraries are available for QoL plugins?

Available shared libraries include qol-plugin-api, qol-config, qol-platform, qol-runtime, qol-color, qol-search, qol-fx, and qol-frecency. These provide common capabilities to multiple plugins to reduce code duplication.

How does dependency management work for QoL shared libraries?

Dependency management for QoL shared libraries involves enforcing correct integration order and compatibility through push order and contract validation rules. This ensures proper library ownership and stable plugin integration.

Why do plugins accumulate duplicated code over time?

Plugins accumulate duplicated code over time when common capabilities are implemented independently rather than moved into shared libraries. This duplication increases maintenance difficulty and risks inconsistency across the plugin ecosystem.

Can I apply shared library placement rules during code reviews?

Apply shared library placement rules during code reviews to determine proper library placement for new capabilities. This identifies when plugin functionality should reside in shared libraries rather than individual plugins.