بنقرة واحدة
verify
Verify UI changes in microlink/www by driving the Gatsby dev server with agent-browser.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Verify UI changes in microlink/www by driving the Gatsby dev server with agent-browser.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create or improve competitor alternative pages under src/pages/alternative/.
Scaffold a customer story page under src/pages/use-cases/ from the CustomerStory module.
Create or improve use-case landing pages under src/pages/use-cases/ from the UseCaseStory module.
Generate concise, user-facing changelog entries for Microlink by inspecting git commits across relevant repositories.
Make designs responsive across screen sizes, devices, and platforms.
Add animations, micro-interactions, and motion effects to a feature.
| name | verify |
| description | Verify UI changes in microlink/www by driving the Gatsby dev server with agent-browser. |
Kiko usually has npm run dev already running on port 8000 — check with
lsof -nP -iTCP:8000 -sTCP:LISTEN before starting one (it serves this repo and
hot-reloads edits). If nothing is listening, run npm run dev in the background;
predev fetches remote data first, allow ~1-2 min until pages compile.
Gatsby dev renders client-side, so curl won't show page content — use the
agent-browser skill:
agent-browser open http://localhost:8000/<page>
agent-browser wait --load networkidle # first hit compiles the page; retry screenshot if it shows "Preparing requested page"
agent-browser screenshot out.png
agent-browser set viewport 480 800 # mobile check
agent-browser set media light reduced-motion # a11y motion check
agent-browser eval "<js>" # inspect DOM state
[error] 404 page could not be found in the console is a Gatsby dev artifact, not a bug.Link then window.history.back() via eval.npx standard <files>.