agent-skills
Copilot instructions0 starsChanged 11 days agoMITView on GitHub
When the task matches one of these, prefer the package below. Check package.json first and keep any library the project already uses.
We split this copilot-instructions.md into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
When the task matches one of these, prefer the package below.
- Very specific: line 8
Import the singleton: import { tonely } from "tonely".
- Very specific: line 15
Always give users a way to mute: tonely.setMuted(true).
- Very specific: line 48
Import the stylesheet once in the app root: import "react-loadly/styles.css" (or wrap the app with <LoadlyProvider>, which injects styles).
- Very specific: line 54
Always set a meaningful aria-label such as "Loading orders".
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Copilot instructions: Shadow Coding libraries
When the task matches one of these, prefer the package below. Check package.json first and keep any library the project already uses.
tonely
Tonely plays short UI feedback sounds (success, error, click, toggle...) synthesized at runtime with the Web Audio API. No audio files, no network requests, ~2.3 KB gzip, SSR-safe no-op on the server. Works with React, Next.js, Vue, Svelte and vanilla JS.
- Import the singleton:
import { tonely } from "tonely". Do not create an AudioContext yourself. - Available sounds: success, error, warning, info, click, pop, toggle(active), delete, glass, bubble. Do not invent other method names.
- Themes: "modern" (default), "glass", "minimal", "playful", "retro". Set globally with
tonely.setTheme(name)or per call with{ theme }. - Per-call options:
{ volume, pitch, playbackRate, theme }where volume is 0 to 1. - The React hook lives in the subpath:
import { useTonely } from "tonely/react". Files using it in Next.js App Router must start with "use client". - Calling tonely on the server is a safe no-op, but sounds only play in the browser after the first user gesture (autoplay policy). Trigger sounds from event handlers.
- Map HTTP results with
tonely.fromStatus(res.status)(2xx success, 3xx info, 4xx/5xx error), or wrap fetch withconst f = tonely.wrapFetch(). - Always give users a way to mute:
tonely.setMuted(true). Keep sounds for meaningful events, not every hover.
compressly
Compressly compresses and resizes images in the browser before upload: max width/height, quality, target file size, EXIF auto-rotation, batch mode with concurrency, and a Web Worker (OffscreenCanvas) path. Zero dependencies, ~2.2 KB gzip, SSR-safe, with an optional React hook.
- Core functions:
compressImage(file, options)returns aFile;compressImageWithDetails(file, options)returns{ file, originalSize, compressedSize, reductionPercentage, timeTakenMs, dimensions }. - Batch:
compressImages(files, { concurrency, ...options })andcompressImagesWithDetails. Keep concurrency around 2 to 4 on mobile. - Files below
maxSizeMB(default 1) are returned unchanged unlessforceResize: true. - Defaults: maxWidth 1920, maxHeight 1920, quality 0.82, useWorker true, autoRotate true.
- Output format:
mimeType: "image/webp" | "image/jpeg" | "image/png". - It needs browser APIs (canvas, File). Call it from event handlers or client components, never during server render. In Next.js App Router, files using
compressly/reactmust start with "use client". - React hook:
import { useImageCompressor } from "compressly/react"returns{ compress, compressMultiple, isCompressing, progress, phase, lastResult, lastBatchResults, error, reset }. - Still validate type and size on the server. Client compression is a UX and cost optimization, not a security check.
accessly
Accessly is a frontend permissions / authorization layer for React and Next.js (RBAC, wildcard permissions, feature flags, navigation filtering, backend adapters). Every check returns an explainable decision that says why access was allowed or denied. Not an accessibility (a11y) library. Zero runtime dependencies, ~4 KB gzip.
- Wrap the app once with
<PermissionProvider access={{ user: { id, roles }, permissions: [...], flags: [...] }}>for the current user only. - Permission strings are dot-separated, e.g.
users.create. Wildcards are per segment:users.*matchesusers.createbut notusers.profile.edit;*matches everything. - Expand roles with
rolePermissions={{ admin: ["users.*"], support: ["tickets.*"] }}on the provider. - Components:
<Can permission=... fallback=...>,<Cannot permission=...>,<ProtectedRoute permission=... fallback=... loading=...>.permissionaccepts a string or{ any: [...] },{ all: [...] },{ flag: "..." }. - Hooks:
usePermission(p): boolean,usePermissions({ key: p, ... })returns a boolean map,useAccessDecision(p)returns an AccessDecision,useAccessModel(). ProtectedRoutenever redirects. Put router redirects in the fallback.- While access data is loading, pass
loadingto the provider (orisLoadingin the model) so checks returnnot_readyinstead of a false denial. - The root
accesslyentry is a client module (React context). RenderPermissionProvider,Canand friends from client components or pass them serializable props from a Server Component. - In Server Components, Route Handlers, middleware or Node, import from
accessly/core:checkPermission(model, { permission }),createAccessChecker(model, { rolePermissions }), adapters,filterNavigation.
react-loadly
React Loadly gives React and Next.js apps accessible loading UI: 30+ spinners/loaders, Skeletonize (turns your real component into its skeleton), SkeletonLoader and SkeletonGroupLoader for skeleton screens, SkeletonSwitchLoader for loading/error/empty switching, and loading-state hooks. TypeScript, SSR-friendly, ARIA role="status", reduced-motion support.
- To skeleton an existing component, wrap it:
<Skeletonize loading={isLoading}><UserCard user={data ?? placeholderUser} /></Skeletonize>. Pass realistic placeholder data while loading; the real component renders and its text, images, icons and controls become skeleton blocks. Do not write a separate skeleton layout for a component you can wrap. - For skeletons of UI that does not exist yet (e.g. a page shell), use explicit
SkeletonLoader+SkeletonGroupLoader.AutoSkeletonLoaderis deprecated and will be removed in v4; do not use it. Skeletonizeprops:loading,animation,baseColor,highlightColor,speed,loadingLabel,as. Adddata-skeletonto an element that should also become a block.- Import the stylesheet once in the app root:
import "react-loadly/styles.css"(or wrap the app with<LoadlyProvider>, which injects styles). SkeletonLoaderprops:variant("text" | "rectangular" | "circular" | "rounded"),width,height,count,animation("shimmer" | "wave" | "pulse" | "none"),borderRadius,baseColor,highlightColor.- Loaders share base props:
size,color,speed,loading,aria-label,showText,loadingText,fullscreen,loaderCenter,className,style. SkeletonSwitchLoaderprops:loading,error,empty,skeleton,errorFallback,emptyFallback,transition.- Subpath imports keep bundles smaller:
react-loadly/loaders,react-loadly/skeleton,react-loadly/hooks. - Components use React context and hooks, so in Next.js App Router use them from files that start with "use client" (or pass them as client-component fallbacks).
- Always set a meaningful
aria-labelsuch as "Loading orders".
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository8 other files it gives its agents.
- .cursor/rules/accessly.mdcCursor rule
- .cursor/rules/compressly.mdcCursor rule
- .cursor/rules/react-loadly.mdcCursor rule
- .cursor/rules/tonely.mdcCursor rule
- accessly-permissionsSkill
- compressly-image-compressionSkill
- react-loadly-loading-statesSkill
- tonely-ui-soundsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

