Karvey browse

Skill MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-browse

Karvey — método spec-driven development agnóstico de stack (Afán, selknam). Plugin de Claude Code. © HainTech, Apache 2.0.

Install

npx -y skills add MauricioQuezadaHaintech/karvey --skill karvey-browse

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Give the agent eyes in the target's real runtime for the Karvey method. Real browser (web), simulator/device (mobile), terminal (CLI) — click, screenshot, inspect. Imports session cookies for authenticated views. Triggers include "karvey browse", "dar ojos", "navegador real", "screenshot", "inspeccionar UI", "abrir la app".

SKILL.md

3.6 KB, as published. Nobody here has run it

karvey-browse — Give the agent eyes

Purpose

A cross-cutting skill of the Karvey Method: a support layer, NOT a phase. It does not advance the method nor change spec.json:phase. It can be invoked from any phase when the agent needs to see with its own eyes what is happening in the target's real runtime.

Its role is simple: give it eyes. The agent stops reasoning blindly about the code and starts observing the real behavior — open, click, screenshot and inspect state. Inspired by gstack /browse + /setup-browser-cookies.

Stack-agnostic

It operates on the real runtime of the target declared in project.json:targets (see karvey/rules/targets.md). It does not assume a fixed stack:

Target	Real runtime	How it is observed
`web`	Headless browser (e.g. Playwright)	navigate, click, screenshot, read DOM/console
`ios` / `android`	Simulator / device	open the app, interact, screenshot, read logs
`cli`	Process / terminal	run, capture stdout/stderr, inspect state
`api`	HTTP client	send requests, capture responses and headers

Capabilities

Navigate / open the target in its real runtime.
Click / interact (forms, buttons, gestures depending on the target).
Capture screenshots as visual evidence.
Read state / console (DOM, logs, process output, responses).

Findings (feed the iteration loop)

When browsing surfaces a defect or a gap (something looks wrong, behaves wrong, or contradicts/exceeds the spec), and a change-id is in context, append it to docs/spec/changes/{change-id}/findings.md classified as bug / spec-gap / emergent (see karvey/rules/iteration-loop.md). Browse only observes and classifies — routing is karvey-iterate's job. This is how "I saw it break with my own eyes" becomes tracked work instead of a passing comment.

Session handling (web target)

When the target is web, it can import cookies/session from a real browser to test authenticated views without manual re-login. This makes it possible to inspect screens behind login using the user's already-active session.

Steps

Determine the target. Read project.json:targets (and karvey/rules/targets.md). If the user passed --target, use that; if not, infer it from the destination or from the project's main target.
Bring up the corresponding runtime. Headless browser for web, simulator/device for mobile, process/terminal for CLI, HTTP client for API. If it is authenticated web, import the real browser's cookies/session before navigating.
Execute the requested actions. Navigate/open, click/interact, capture and read state as requested.
Return evidence. Screenshots, DOM/state, console logs or process output — everything that backs up what was observed.

Reminders

Close the runtime/browser when finished. Do not leave processes or browsers hanging.
It does not advance the phase. This skill is cross-cutting support; it never modifies spec.json:phase nor makes method transitions.

Part of the Karvey™ Method — © HainTech, by Mauricio Quezada Ibáñez · Apache 2.0 · see karvey/LICENSE and karvey/TRADEMARK.md.