Piyabordee

Export n8n workflow nodes as JSON snippets for GUI testing. When the user asks to export, extract, or show a specific node from a workflow JSON file, use this skill. The user pastes the snippet into n8n GUI to test changes themselves. If the result is wrong and the user provides a correction pattern, remember it for future similar cases. Trigger whenever the user wants to work with individual n8n nodes rather than full workflow files.

This skill should be used when documentation version numbers need to be synchronized with workflow JSON files. Triggers include: update docs, check version sync, sync docs with workflows, update docs/, update README.md, update SCREENSHOTS.md, check versions, sync documentation, อัพเดทเอกสาร, sync เวอร์ชัน, เช็คเวอร์ชัน, อัพเดท docs, สรุปการเปลี่ยนแปลง, or when the user asks to verify version consistency between workflow files and documentation after commits.

Sanitize n8n workflows and documentation before publishing to GitHub. Use this skill whenever the user mentions publishing to GitHub, pushing to public repo, sanitizing workflows, removing sensitive data, cleaning credentials, preparing files for GitHub, push to GitHub, publish workflows, ลบข้อมูล sensitive, push GitHub, publish, sanitize, ก่อน push, ก่อน publish, ทำความสะอาดข้อมูล, ลบ credential, or any action involving making n8n workflow files safe for public visibility.

Use when the user wants to test, verify, screenshot, click, fill, or interact with a web app, an HTML mockup (e.g. `docs/mockup/**/*.html`), a local dev server at `127.0.0.1` / `localhost`, or any URL the agent can reach. Triggers on phrases like "test this page", "open in browser", "click the button", "verify the form", "screenshot the dashboard", "check responsive", "playwright test" (redirect to native tools). Use VS Code native browser agent tools (openBrowserPage, readPage, screenshotPage, clickElement, typeInPage, hoverElement, dragElement, handleDialog, navigatePage, runPlaywrightCode) instead of installing Playwright/Puppeteer npm packages.

Reverse engineer undocumented or hidden web APIs by observing browser traffic and building a live client. Use when: the user wants to extract API endpoints from a website (e.g. moba.example.gg, internal dashboards, third-party apps), recover a hidden list endpoint by hooking fetch/XHR in a real browser, build a Python/Node client that calls the real API for a webapp, or document a target site. Triggers: reverse api, api endpoint, แกะ api, ดึง api, undocumented api, hidden endpoint, scrape api, internal api, traffic capture, session replay, เลียนแบบ client.

Use when user asks to update, add, or modify documentation in `docs/` of this repository, when creating a new feature/architecture/reference/project doc, or when an agent is about to write in `docs/` and has not read `CLAUDE.md` and `.claude/rules/*` in the current session. Triggers on "update docs", "document this", "add a doc for X", "เขียน docs", "อัพเดทเอกสาร". Forces read-first discipline to prevent orphan docs, contradicted stable rules, and broken wiki links.

Use when modifying code in any versioned package (VSCode extension, npm, pip, cargo crate) - every code-changing commit must bump the version AND carry a truthful commit message describing what actually changed

Comprehensive test engineering knowledge base for creating, reviewing, and improving test strategies and test cases. Use when writing test cases, designing test strategies, performing security testing, checking OWASP Top 10 vulnerabilities, generating REST API contract tests, writing BDD-Gherkin scenarios for web applications, testing GraphQL queries and mutations, creating mobile app test matrices, testing microservices with circuit breakers and event-driven patterns, setting performance benchmarks, prioritizing tests by risk level, detecting project type for test framework selection, reviewing existing test coverage, generating executable test code (Playwright, Jest, Vitest, pytest, JUnit, etc.) from an approved strategy, or scaffolding CI pipelines for tests. Invoked by test-engineer-agent (strategy generation) and test-codegen-agent (code generation).

Analyze a raw API response and generate a JSONPath mapping for the custom-api-usage VSCode extension. Use when the user wants to add a new provider or fix a broken mapping.