Capture mandatory before/after screenshots (and videos/GIFs for flows) for any change touching UI/UX, and attach them to the PR. Use whenever a change touches frontend/pages, components, layouts, or assets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Any PR touching frontend/{pages,components,layouts,assets}/** must show what
changed visually: before/after screenshots in the PR description, plus a
GIF/video when the change is a flow or animation. Only skip this for refactors
with zero visual effect — and say so explicitly in the PR description.
tools/agent/boot_stack.sh
cd backend && uv run python ../tools/agent/seed_org.py --demo
export PLAYWRIGHT_BROWSERS_PATH=/opt/pw-browsers # cloud sandboxes
cd frontend
node ../tools/agent/capture.mjs http://localhost:3000/<page> before.png
# apply change / unstash, rebuild if prod mode:
node ../tools/agent/capture.mjs http://localhost:3000/<page> after.png
context.storageState({ path: 'state.json' }), then pass --state state.json.he as well as en (set the locale via
the picker in /settings/general or the X-Locale header).Static shots can't show a flow. Record one:
node ../tools/agent/capture.mjs http://localhost:3000/<page> flow.webm --video 10
# or drive a multi-step flow in a throwaway spec with recordVideo, then:
ffmpeg -i flow.webm -vf "fps=10,scale=960:-1:flags=lanczos" flow.gif
GitHub renders GIFs inline; .webm cannot be attached via the API.
Commit the files under media/pr/<branch-slug>/ and reference them in the PR
body by their raw URL so they render inline:
## UI changes
| Before | After |
|--------|-------|
|  |  |
Rules:
media/pr/ files may be deleted after the PR merges; they are evidence, not assets.아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Add a new data source / connection type (e.g. a SQL Server-like database) end to end — client with get_schemas/execute_query, config + credentials schemas, registry entry, icon, tests — plus the verification steps. Also covers adding or updating an MCP connector (a preset, not a new type). Use when adding or significantly extending a connector.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add a new LLM model to the preset catalog, or a whole new LLM provider — with the mandatory pre-flight verification of model id, pricing, and context window against the provider's official docs. Use when asked to add/update LLM models, providers, or pricing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query, visualize, and analyze data in a Bag of Words (BOW) workspace via the bagofwords MCP tools. Use for creating reports, running tracked queries, and building dashboards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update the product docs at docs.bagofwords.com (Mintlify) with text and fresh screenshots after a user-facing change ships. Use when a merged change alters user-visible behavior, adds a feature, or when asked to update/refresh documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The locale/i18n architecture of bagofwords — catalogs, resolution order, RTL, backend contracts — and the procedures for adding strings, adding a locale, or translating UI. Use when adding/changing user-facing strings, working on RTL, emails, localized errors, or anything locale-related.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a live QA pass over the app — first map all user-facing functionality, then boot the full stack and manually exercise flows with Playwright, recording pass/fail evidence and filing a QA report. Use for release QA, post-merge smoke passes, or "QA the app / this area" requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.