Frontend testing debugging

01 / WHAT TO TRY

Start with the right material.

Publisher description excerpt: “Use when testing, debugging, or making targeted improvements to rendered frontend apps through the Build Web Apps or…” Source ↗

Suggested preparation

• The relevant project and requirements
• Runtime, access constraints, and acceptance criteria
• The complete skill folder and any required supporting files

These are Fieldwork’s preparation notes. Follow the source’s full input checklist for the specific task.

The intended handover

An implementation plan, review, or tested change

This is a source-inspected starting point. Fieldwork has not run-tested this skill or measured time savings.

02 / CHECK THE FIT

Your platform. Your context.

Platforms

Codex

Published in OpenAI’s Codex plugin examples. Requires the complete plugin and its documented app/MCP/runtime access; this is not automatically a ChatGPT web installation.

Australian and worldwide use

Geography-neutral workflow. Set Australian spelling, AUD, dates and business context explicitly; local compliance is not supplied by this label.

Setup type: Local tooling / APIs

No named business app was detected in the inspected instructions.

Dependencies

• The source references local code or command-line tooling; check its runtime and package requirements before use.

Public instructions do not imply free access to Claude, ChatGPT, paid apps, API usage or generation services.

03 / SET IT UP

Keep the complete workflow.

1. Review the linked source and the publisher’s current README before installing.
2. Download or install the complete plugin/skill folder, preserving references and scripts. Do not paste a terminal command intended for another app.
3. Use the setup path for the platform you actually have; configure only the required apps and permissions.
4. Start with a permitted sample and the starter prompt. Check the first result against your own normal review process.

Pinned source snapshot; review publisher release and installation notes.

Replace the brackets and supply the required inputs. This prompt is Fieldwork’s example, not a tested guarantee or a replacement for installation.

Use frontend-testing-debugging for [business task]. Our business is in [country and state/territory], our currency is [currency], and the intended reader is [audience]. Use only the attached authorised inputs and approved policies. First identify missing information and unavailable tools. Prepare a draft for human review; cite the supplied evidence, separate assumptions, and do not send, publish, lodge, purchase or change records.