메뉴
Use when defining or reviewing Doc View behavior contracts before changing PSI parsing, DTOs, Markdown output, uploads, exports, settings, UI-visible behavior, or IntelliJ compatibility.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | doc-view-contract-design |
| description | Use when defining or reviewing Doc View behavior contracts before changing PSI parsing, DTOs, Markdown output, uploads, exports, settings, UI-visible behavior, or IntelliJ compatibility. |
Use this skill before implementation work that changes user-visible or integration-visible behavior. OpenSpec owns proposal/design/spec/tasks; this skill supplies Doc View domain checks.
AGENTS.mddocs/contract-design.mdcontextFiles path returned by openspec instructions apply --change <name> --jsondocs/architecture.md when package, service, DTO, settings, extension, or data flow boundaries are involveddocs/performance-guide.md when PSI, UI, rendering, export, upload, recursion, or cache performance can changedocs/intellij-compatibility.md when IntelliJ API, Gradle platform, descriptor, extension, or compatibility behavior is involvedspecs/**, not docs/contracts/**.DocView/Body/Param/Header, Markdown, payload, UI, notification, or compatibility outputs.runIde, or Plugin Verifier.docs/contracts/**; OpenSpec specs are normative.Use when creating or updating Doc View repository documentation, AGENTS.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills.
Use when implementing or reviewing Java-only Doc View production changes, especially PSI parsing, services, DTOs, UI, integrations, settings, export, or IntelliJ Platform behavior.
Use when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and rollback notes.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.