Skip to main content

design-editor-repro

Reproduce and verify Design editor issues against the application itself.

소스 정보

저장소
BuilderIO/agent-native
최근 소스 활동
2026년 10월 9일 11:49
감지된 SKILL.md 언어
영어
스타
7,449
포크
681

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
18 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
design-editor-repro
description
Reproduce and verify Design editor issues against the application itself.
# Reproduce Design editor issues Use this skill for defects that need a real Design editor session. Work from a local or production copy of an Agent-Native design and describe the observed application behavior directly. ## Setup 1. Start the worktree's Design app with .agents/skills/design-editor-repro/harness/start-dev.sh. 2. Run node .agents/skills/design-editor-repro/harness/doctor.mjs until the local app and editor session are ready. 3. Copy a source design with node .agents/skills/design-editor-repro/scripts/copy-design.mjs <design-id>. Use a production copy only when DESIGN_TEST_EMAIL and DESIGN_TEST_PASSWORD are configured. Remove that copy when finished. 4. Reproduce the reported steps before changing application code. Save only task-relevant files under templates/design/.tmp/editor-repro/. ## Investigation - Use the helpers in harness/dlib.mjs to open the editor, select layers, inspect fields, trigger actions, and read persisted files. - Prefer Playwright input through the app page. Use the OS input helper only when browser input cannot exercise the reported path. - Capture screenshots with harness/shot.mjs when visual evidence will help explain the application state. The helper returns local paths for inspection. - Check the relevant implementation and neighboring tests before changing code. Keep fixes at the application boundary and add a regression test where the existing suite supports it. - Keep diagnostic data local to the task. Do not commit screenshots, copied user designs, session data, credentials, or temporary exports. ## Verification - Reproduce the original steps on the changed build. - Run the narrowest relevant unit or browser tests, then the required Design interaction lane when the change affects canvas behavior. - Inspect the rendered application when the fix changes visible behavior. - Close the editor page and delete any temporary production copy before reporting completion. For details, see harness-recipes.md, reference/input-and-osmouse.md, reference/fixing.md, reference/tests-and-blast-radius.md, and reference/performance.md.
GitHub에서 보기