14,555 skills found ¡ Page 281 of 486
GanyuanRan / requesting-code-reviewUse when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.
GanyuanRan / using-git-worktreesUse when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.
GanyuanRan / verification-before-completionUse when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.
GanyuanRan / writing-plansUse when you have an approved spec or written requirements for a multi-step task that needs a durable plan document before touching code. Small, single-owner, or fast-path tasks do not need this skill.
GanyuanRan / goal-framingUse when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or task boundaries before work.
GanyuanRan / systematic-debuggingUse when encountering a bug, test failure, or unexpected behavior, before proposing fixes
GanyuanRan / update-aegisUse when the user says `aegis:update`, asks to update or upgrade an installed Aegis method-pack, wants the latest Aegis version, or asks whether Aegis is current on this host.
GanyuanRan / establishing-project-contextUse when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
GanyuanRan / executing-plansUse when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.
GanyuanRan / long-task-continuationUse when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.
GanyuanRan / recording-architecture-decisionsUse when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.
GanyuanRan / subagent-driven-developmentUse when executing a written implementation plan with independent tasks in the current session where delegation beats inline coordination cost; otherwise inline. Ad-hoc 2+ tasks without a plan use dispatching-parallel-agents.
GanyuanRan / finishing-a-development-branchUse when verified work needs integration or cleanup of an existing task-created branch/worktree, or the user explicitly requests merge, PR, or branch lifecycle handling.
reticlehq / reticleInstall, instrument and verify this running web app from the inside (DOM, network, routing, console and framework state) instead of screenshots or guessing. Drives one real flow end to end and returns a verdict with the file:line to fix
reticlehq / install-and-verifyVerify 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.
reticlehq / verify-cli-runProve 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.
reticlehq / verify-language-switchProve a language switch translates what the user sees, keeps what they had already typed, and is still in force after a reload
reticlehq / verify-unattendedInstall, 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.
reticlehq / verify-form-validationCheck that a form actually rejects bad input: the error message renders, the submit button stays disabled, and no request goes out
reticlehq / replay-user-flowsTurn 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
reticlehq / verify-keyboard-accessVerify that every interactive control on a page can take keyboard focus and that its primary action fires from the keyboard rather than only the mouse, and say plainly that Tab order cannot be verified today
reticlehq / agentic-tddTest-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
reticlehq / audit-my-appSweep 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.
reticlehq / drive-desktop-appDrive and verify an Electron or Tauri desktop app from the inside, including the main-process and Rust IPC calls a browser tool cannot see
reticlehq / test-error-statesForce 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
reticlehq / verify-login-logoutProve sign-in lands the user where they should be, sign-out really ends the session so a protected page sends them back to sign in, and an expired session asks to sign in again instead of breaking
reticlehq / verify-optimistic-updateProve a UI that updates before the server answers puts things back and says so when the request fails, and keeps the change when it succeeds
reticlehq / verify-paginationProve the next page of a list, or the next batch of an infinite scroll, loads NEW rows from the server, repeats none, and that the end of the list is handled
reticlehq / debug-broken-uiFind 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
reticlehq / design-system-complianceCheck 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.
