Design or substantially improve a landing page for tinte. Use when building a marketing site, hero section, product page, pricing page, or any page whose job is to make a first-time visitor understand and want the product. Carries tinte composition rules, type scale, voice, and token API.
Generate code screenshots via ray.tinte.dev API. Use when user asks for code screenshots, code images, code snippets as images, or says "ray". Calls POST https://ray.tinte.dev/api/v1/screenshot and saves the PNG result.
Agent-native design system infrastructure. Browse, install, and preview design systems from tinte.dev. Use when user asks about themes, design systems, presets, color palettes, or says "tinte". Works with shadcn/cli v4 presets and registries.
Survey an unfamiliar or shared issue backlog, qualify a small set of worthwhile contributor-side candidates, compare them in an evidence-backed matrix, recommend one, let the user make the final selection, and seed the canonical Issue Contract. Use for requests like "what should I work on here", "find a good issue to…
Understand, diagnose, change, or review an unfamiliar codebase through one evidence-backed mission. Use when learning architecture, tracing a feature, investigating a bug, implementing a real change with guided or agent execution, reviewing a diff or PR, or checking whether tests and the built artifact prove the…
Create granular, browser-openable visual proof for a web UI change by capturing the same real DOM element or page state before and after with agent-browser. Use when a web bug fix, component change, responsive adjustment, loading state, interaction, or styling change has a visible browser result worth demonstrating…
Escribe el handoff de un ciclo de trabajo en el vault, verificando el estado contra git antes de afirmarlo. Usar al cerrar una sesion larga, antes de compactar, cuando el usuario dice handoff, /handoff, escribi el handoff, donde quedamos, antes de irme, cerra el ciclo, o cuando un hilo se vuelve demasiado largo para…
Materialize selected engineering workstreams as visible, persistent Herdr workspaces after a portfolio or handoff review. Use when the user asks to set up, resume, or organize project work in Herdr; turn a workstream-reconcile queue into repo-scoped workspaces; or make specialist agents launched by other skills…
Prove a performance improvement before and after changing algorithms, data structures, latency, throughput, memory, bundle size, build time, or repeated work. Use when a concrete path is slow or resource-heavy, when considering Map, Set, heap, trie, queue, cache, index, batching, or memoization, or when asked to…
Baseline a repository before quality work. Use when asked to audit maintainability, reliability, performance, security, test quality, technical debt, or code health across a codebase; to identify and rank gaps before fixing them; or to compare quality state over time. Remain read-only on target source.
Candidate: Root-cause a bug you cannot reproduce because it needs another OS or hardware you don't have, by detecting its structural OR visual signature on the machine you DO have. Use whenever you're about to write cannot-reproduce-needs-Windows/Linux/a-device/a-monitor, when a bug is platform-specific but you're on…
Reduce code size, PR additions, duplication, ceremony, or maintenance surface while preserving behavior and regression protection. Use whenever the user asks to simplify, deduplicate, delete unnecessary code or tests, reduce LOC, shrink a diff below a line budget, centralize repeated runtime logic, or make a feature…
Test whether behavioral coverage can reject realistic wrong implementations. Use when tests are green but may be weak, after fixing a bug, and whenever code implements or changes a protocol, parser, serializer, state machine, lifecycle, event translation, browser interaction, adapter, or compatibility layer. Also use…
Candidate: Keep a decision trail (a.k.a. show-your-work) while implementing, so a later reviewer can audit the choices and not just the diff. A TSV appended one row per real decision (what, why, evidence), written in the moment, never reconstructed. Use at the start of any implementation task an agent runs unattended…
Reassess one or more ongoing engineering workstreams by treating handoffs as leads and revalidating their drift-prone claims against live GitHub state, local Git checkouts, releases, deployments, and package registries. Use when work may have stalled or changed since the last handoff; when the user asks to reassess…
Read-only GitHub PR status and reference graphs for maintainers and agents. Use whenever the user asks for PR counts or status by author, project, repository, or review state; approved, changes-requested, conflicting, draft, ready-for-review, or unassigned PRs; a compact portfolio table; or counts for named…
Survey an unfamiliar or shared issue backlog, qualify a small set of worthwhile contributor-side candidates, compare them in an evidence-backed matrix, recommend one, let the user make the final selection, and seed the canonical Issue Contract. Use for requests like "what should I work on here", "find a good issue to…
Orchestrate Shaping to decide whether a fix or contributor PR is the right thing to build. Use before implementation when a defect has multiple solution shapes, changes a contract or persistent state, follows a prior review finding, or requires adopting, amending, absorbing, recreating, or rejecting an existing patch.…
Gate whether a fix or existing contributor PR is the right thing to build. Use before implementation when a defect has multiple solution shapes or changes a contract, especially session state, long-lived process configuration, restart or reuse behavior, fixes to prior review findings, and decisions to adopt, absorb…
Gate whether a fix or existing contributor PR is the right thing to build. Use before implementation when a defect has multiple solution shapes or changes a contract, for fixes to prior review findings, and before adopting, absorbing, recreating, or substantially amending an existing PR or patch. In candidate-audit…
Review a code change or security claim by modeling attackers, assets, trust boundaries, exploitability, and impact. Use for authentication, authorization, origin or request validation, secret handling, tenant isolation, sandboxing, privilege changes, injection, unsafe deserialization, or when deciding whether a…
★not rated 11 todayA73 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: