reticle

AI agents can generate code, but still struggle to understand what they build. Reticle brings Jev-style machine-native runtime perception to web & desktop applications.

Active — Updated in the last 14 days

Works with

Claude

View on GitHub

1.2k GitHub stars (1,240)

+349 in 20 days

Stars gained per day · daily snapshots since Sep 26

Stars gained between daily snapshots
Period	New stars
Sep 27	+2
Sep 28	+9
Sep 29	+14
Sep 30	+97
Oct 1	+6
Oct 2	+83
Oct 3	+43
Oct 4	+8
Oct 5	+5
Oct 6	+10
Oct 7	+11
Oct 8	+10
Oct 9	+5
Oct 10	+2
Oct 11	+8
Oct 12	+4
Oct 13	+7
Oct 14	+3
Oct 15	+4
Oct 16	+18

14 skills (14 skills found in its SKILL.md files)
201 forks (201 forks)
Today last update (Last updated today)

Install

Skills CLI

npx skills add reticlehq/reticle

Asks which skills and agents to install. Just one: npx skills add reticlehq/reticle --skill reticle — add -g for every project.

Claude Code

git clone https://github.com/reticlehq/reticlecp -r "reticle" ~/.claude/skills/reticle

Copies the reticle skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add reticlehq/reticle

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

Filter skills

In the author's own words, from each skill's SKILL.md.

reticle

No description in the SKILL.md.
SKILL.md on GitHub (opens in a new tab)
agentic-tdd

Test-driven development for behaviour a unit test cannot reach, by writing the expectation against the running app before writing the code. Declare the consequence first, watch it fail, implement, watch it pass. Use when building a user-facing feature, when the user asks for TDD on UI or full-stack work, when a unit test cannot express the outcome that matters, or when you want a red-green loop t…
skills/agentic-tdd/SKILL.md on GitHub (opens in a new tab)
audit-my-app

Sweep a whole running web app for what is broken, without writing a script or knowing the codebase. Clicks every reachable control and reports dead buttons, console errors, failed requests, and places where the API and the screen disagree. Use on an unfamiliar codebase, before a release, after a big merge or dependency bump, when the user asks for a smoke test or a health check, or when someone s…
skills/audit-my-app/SKILL.md on GitHub (opens in a new tab)
debug-broken-ui

Find out why something in a running web app does not work, when the console is empty and the code looks correct. Reads the click, the request, the store and the console together and returns the file:line to open. Use when a button does nothing, a form will not submit, data will not load, a page renders blank or stale, a modal will not close, or the user says "it's broken" and the code review says…
skills/debug-broken-ui/SKILL.md on GitHub (opens in a new tab)
design-system-compliance

Check that the UI you actually rendered uses the design system, by reading computed styles in the running app against the project's design tokens. Catches hardcoded hex colors, off-palette backgrounds, invisible or unusable controls, and animations that never ran. Use after building or restyling a component, when a design review is wanted, when a UI looks slightly off but nobody can say why, or w…
skills/design-system-compliance/SKILL.md on GitHub (opens in a new tab)
drive-desktop-app

Drive and verify an Electron or Tauri desktop app from the inside, including the main-process and Rust IPC calls a browser tool cannot see. Use when a desktop app needs testing, when a feature works in the browser but not in the packaged app, when an IPC or invoke call needs proving, when a desktop screenshot or visual diff is wanted, or when you need a headless run of a desktop UI in CI.
skills/drive-desktop-app/SKILL.md on GitHub (opens in a new tab)
false-green-tests

Find out why the tests pass but the app is broken. Catches false greens: a green suite over a feature that does not work, a mocked API standing in for a real one, an assertion that holds no matter what the app does, a click handler wired to nothing. Use when the suite is green and the user says it is broken, when a test never fails, when coverage looks fine but bugs still ship, or before trusting…
skills/false-green-tests/SKILL.md on GitHub (opens in a new tab)
fix-what-i-pointed-at

Pick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the note they typed, and the source file and line. Use when the user says they marked or flagged something, when starting a session on an app someone has been clicking through, when a designer or PM has left feedback in the UI, or when the user describes a problem as "that button there" withou…
skills/fix-what-i-pointed-at/SKILL.md on GitHub (opens in a new tab)
install-and-verify

Verify that a web app change actually works by driving the running app from the inside (DOM, network, routing, console, framework state) instead of screenshots or guessing. Use after any user-facing change, when a fix is claimed but unproven, when a test passes but the UI is broken, or when you need a real verdict rather than "looks right". Also use to install and wire up Reticle in a project tha…
skills/install-and-verify/SKILL.md on GitHub (opens in a new tab)
replay-user-flows

Turn a user journey you just clicked through into a saved regression check that re-runs deterministically, with no model in the loop and no test code to write. Use when you have driven the same flow twice, when the user wants regression coverage without a Playwright suite, when a refactor needs proving against every existing journey, or when re-verifying by hand is costing a full drive every time.
skills/replay-user-flows/SKILL.md on GitHub (opens in a new tab)
test-error-states

Force the states a happy-path run never reaches (a failing API, an empty list, a slow request, a timeout, an expired session, a toast that auto-dismisses) and check the UI actually handles them. Use when error handling was written but never run, when a loading or empty state needs verifying, when a bug only happens on a slow connection, or when a timer, poll, debounce or retry needs testing witho…
skills/test-error-states/SKILL.md on GitHub (opens in a new tab)
verify-cli-run

Prove that a command-line tool actually did what it said, instead of trusting its exit code and its output. Snapshots the filesystem before and after, names the expected consequence in advance, and returns one of four verdicts with what could not be seen. Use after running a build, a migration, a scaffolder, a formatter, a codegen step, or an AI coding CLI; when a command printed success and you…
skills/verify-cli-run/SKILL.md on GitHub (opens in a new tab)
verify-ui-change

Check that a change to a web app actually works in the running app before calling it done. Drives the real page and returns a pass/fail verdict with the request that fired, the state that moved, and the file:line to fix. Use after editing a component, a form, a route, or an API call; when you have said "fixed" but have not opened the app; when the user asks "does it actually work?"; or when a cha…
skills/verify-ui-change/SKILL.md on GitHub (opens in a new tab)
verify-unattended

Install, instrument and verify a web app end to end without pausing for a human. Use in an autonomous or goal-mode agent, in CI, or in any client that asks for approval on every command: it never says "restart your client" or "open a browser", because it takes a route that needs neither. Prefer the normal install-and-verify skill when a human is present and can answer.
skills/verify-unattended/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.

Encoders & Decoders

Hash Generators

Code Formatters

HTML Tools

JavaScript Tools

Network Tools

Database Tools

Development Tools

Miscellaneous Tools

reticle