메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | docs-update |
| description | 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 product docs live on Mintlify (docs.bagofwords.com), managed through the
Mintlify MCP server — not in this repo. docs/ here contains internal
design docs only.
After a user-facing change merges: new feature, changed flow, renamed UI, changed configuration. Skip for internal refactors.
checkout the deployment
(this opens an isolated editing session/branch — surface the returned
editorUrl to the user), then search / read / list_nodes for pages
mentioning the touched feature. List affected pages before editing.tools/agent/boot_stack.sh && cd backend && uv run python ../tools/agent/seed_org.py --demo
cd ../frontend && node ../tools/agent/capture.mjs http://localhost:3000/<page> shot.png
docs/screenshots/pending-changes/<page-slug>/ in this
repo so they're reviewable alongside the docs PR. Match the style of
existing docs images (clean seeded data, 1440px wide, no dev toolbars).edit_page (string replace) or write_page (full rewrite)update_node, never edit_pagecreate_node; site config → update_configdocs/screenshots/pending-changes/<page-slug>/ must be uploaded via the
Mintlify editor (editorUrl) before merge. Do not publish pages pointing
at broken image paths.diff / get_session_state), then save — this opens
a docs PR. Never use Mintlify code-mode (execute_code) for content
work: it writes straight to the live deployment with no PR safety net.editorUrl.locales/en.json) — the UI string is the source of truth for feature names.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.
Build a runnable reproduce→fix→verify loop for a bug or feature in a fresh sandbox, and record it as a feedback-loop doc. Use when investigating a reported bug, validating a root cause, or proving a fix works — before and after the change.
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.
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.
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.