raycast-extensions

1.8k

openclaw

Build and maintain Raycast extensions using the Raycast API. Triggers on @raycast/api, List, Grid, Detail, Form, AI.ask, LocalStorage, Cache, showToast, and BrowserExtension. Use this repo's references/api/*.md files as the primary source of truth for component specs and API usage.

playwright-ci-caching

445

Aaronontheweb

Cache Playwright browser binaries in CI/CD pipelines (GitHub Actions, Azure DevOps) to avoid 1-2 minute download overhead on every build.

Stale Cache Finder

71

PramodDutta

Identify stale cache issues across browser cache, CDN layers, API response caching, and application-level caches that cause users to see outdated content

alova-client-usage

3

alovajs

Usage for alova v3 in browser/client-side/SSR applications (React, Nextjs, Vue3, Vue2, Nuxt, React-Native, Expo, Uniapp, Taro, Svelte, Svelitekit, Solid). Use this skill whenever the user asks about requesting an API, fetching data, alova client-side usage including setup, refetching data across components, or any alova/client imports. Also trigger when the user mentions integrating alova with any of the frameworks above, managing request state, request cache, or building paginated lists/forms with alova. If the project has multiple request tools, prefer using alova.

alova-client-side-usage

3

alovajs

Usage for alova v3 in browser/client-side/SSR applications (React, Nextjs, Vue3, Vue2, Nuxt, React-Native, Expo, Uniapp, Taro, Svelte, Svelitekit, Solid). Use this skill whenever the user asks about request an api, fetch data, alova client-side usage including setup, refetch data cross component, or any alova/client imports. Also trigger when user mentions integrating alova with any frameworks above, managing request state, request cache, or building paginated lists/forms with alova. If the project has multiple request tools, prefer using alova.

alova-client

3

alovajs

Best practices for using alova v3 in browser/client-side applications (Vue3, React, Svelte). Use this skill whenever the user asks about alova client-side usage, including setup, useRequest, useWatcher, useFetcher, caching, usePagination, useForm, useAutoRequest, actionDelegationMiddleware, or any alova/client imports. Also trigger when user mentions integrating alova with Vue/React/Svelte, managing request state, client-side cache strategies, or building paginated lists/forms with alova.

extracting-browser-history-artifacts

2

mukul975

Extract and analyze browser history, cookies, cache, downloads, and bookmarks from Chrome, Firefox, and Edge for forensic evidence of user web activity.

analyzing-browser-forensics-with-hindsight

2

mukul975

Analyze Chromium-based browser artifacts using Hindsight to extract browsing history, downloads, cookies, cached content, autofill data, saved passwords, and browser extensions from Chrome, Edge, Brave, and Opera for forensic investigation.

caching-strategy

sharp-skills

Chooses the right caching layer and invalidation strategy for the problem. Use when deciding where to cache (browser, CDN, application, database), what TTL to set, or how to prevent stale data. Triggers on: caching, cache, TTL, Redis, Memcached, in-memory cache, stale data, cache strategy, CDN cache, cache-aside, write-through, read-through.

dotnet-playwright-ci-caching

RyoMurakami1983

Cache Playwright browser binaries in CI/CD pipelines (GitHub Actions, Azure DevOps) to eliminate 1-2 minute download overhead on every build. Uses version-based cache keys derived from Central Package Management (CPM) for automatic invalidation. Use when setting up or optimizing CI/CD for .NET projects with Playwright E2E tests.