메뉴
Documentation maintenance rules — which docs map to which code areas, the thin-pointer/no-drift rule, and the graphify-update step. Owned by project-steward. Load for /update-docs and the docs-sync step of the implement-workflow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
| name | docs-standards |
| description | Documentation maintenance rules — which docs map to which code areas, the thin-pointer/no-drift rule, and the graphify-update step. Owned by project-steward. Load for /update-docs and the docs-sync step of the implement-workflow. |
packages/shared/src/ipc/contracts/) → docs/API.md.docs/knowledge/ + docs/ARCHITECTURE.md.docs/EXPORT_TEMPLATES.md + docs/knowledge/resume-domain.md.docs/knowledge/automation-domain.md.docs/DESIGN_SYSTEM.md.landing/architecture-map.html + landing/how-it-works.html, then run pnpm check:landing-drift (CI enforces it via the Lint & Format job).docs/knowledge/decision-records/.Describe shape and contracts; never copy drift-prone literals (scoring weights, template/board/applier counts). Point at the owning source symbol instead (weights → commands/match_resume.rs; templates → export/templates/mod.rs; registries → scraping/boards/mod.rs (SCRAPERS)). Knowledge files capped ~150 lines.
Run graphify update . (AST-only, no API cost) so the graph stays current.
When an Architecture-decision lesson becomes an ADR, remove it from lessons.jsonl — the ADR is then its single source.
docs/knowledge/ points at the owning symbol/file; never copy code literals (they rot). After code changes, re-sync docs + run graphify update ..Common mistakes: a "reference" page drifting into tutorial prose (split it — one need per page); pasting code values/signatures into docs instead of pointing at the source (guaranteed drift).
Shared write-side contract every domain AUTHOR imports — how to implement reliably, the smallest-diff rule, validation gates, and the never-approve-your-own-work rule. The write-side mirror of token-efficiency. Load at the start of any implementation task.
Shared context-discipline contract every agent imports — context-source priority, read budget, confidence-stop, the severity rubric, and terse output. Load at the start of any review or implementation task.
General repo rules enforced by ESLint/TypeScript/CI — PRs-only, never bypass lint, import ordering, type imports, path privacy, commit format. Load for any code change.
Browser-extension + bridge standards — MV3 (Chrome + Firefox), least-privilege permissions, the loopback pairing-token auth model, the shared TS↔Rust wire protocol, and the Chrome Web Store + Firefox AMO store-policy + pre-submission checklist. Load for changes under apps/extension/**, extension_bridge/, and the extension protocol.
React renderer standards — ports & adapters (service hooks), design tokens, motion tokens, @ajh/ui primitives, i18n, feature isolation, React Query, a11y. Load for changes under apps/desktop/src/renderer/**.
Rust/Tauri backend standards — L0–L3 layers, centralized platform/net/error ownership, Rust-first business logic, registries, error handling. Load for changes under apps/desktop/src-tauri/src/**.