David Rivera jherax

Both skillshare and skills are two distinct CLI approaches to managing AI agent capabilities, differing primarily in their architectural philosophy, synchronization mechanism, and cross-platform capabilities.

skillshare

Is a skill manager. skillshare is a way to install and sync Agent skills across your local AI tools. skillshare is a centralized, declarative synchronization tool written in Go that acts as a universal hub for skills across 50+ AI CLIs. It solves the problem of scattered skill directories by maintaining a single source of truth in a local directory (e.g., ~/.config/skillshare/skills/) and using symlinks to instantly propagate changes to tools like

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

VS Code: Debugging

The way we usually debug JavaScript code, is through a web browser and typing the keyword debugger or console.log in our files, but switching between browser and VS Code can be annoying, and we also lose synchronization with the source code.

VS Code provides the extension Debugger for Chrome which enables you to edit, debug, and set breakpoints to your JavaScript

VS Code: Debugging Jest

Sometimes, debugging with console.log is not enough to find out what is happening in the code, as console.log prints only plain objects but neither functions nor objects with circular references. Besides, it's possible you may need to know the context and flow of the code.

Read more about debugging with VS Code in VS Code: Debugging.

	/**
	* The Promise.allSettled() method returns a promise that resolves
	* after all of the given promises have either resolved or rejected,
	* with an array of objects that each describe the outcome of each promise.
	*
	* For each outcome object, a `status` string is present.
	* If the status is "fulfilled", then a `value` is present.
	* If the status is "rejected", then a `reason` is present.
	* The value (or reason) reflects what value each promise
	* was fulfilled (or rejected) with.

	/**
	* Dynamic imports allow you to import modules asynchronously.
	* This can significantly improve the load time of web applications
	* by splitting the code into smaller chunks and loading them on demand.
	*/
	async function loadModule(moduleName) {
	try {
	const module = await import(`./modules/${moduleName}.js`);
	module.default(); // Assuming the module exports a default function
	// module.namedExport();

	{
	"assignments": [
	{
	"experiment": "MEDICARE_REPLACEMENTS",
	"pathName": "/",
	"variant": 1,
	"configs": [{
	"apiTarget": "/content/landingpage/MEDICARE/",
	"replacements": {
	"data": {

	/**
	* Gets all Reponse Headers for the current document.
	* @returns An object cointaining the key-value pairs for each header
	*/
	function getHeaders(url = document.location.href) {
	const req = new XMLHttpRequest();
	req.open("GET", url, false);
	req.send(null);

	let key: string;

	import React from 'react';

	let lastScrollY = 0;
	let ticking = false;

	class App extends React.Component {
	componentDidMount() {
	window.addEventListener('scroll', this.handleScroll);
	}