doc-view-java-maintenance

Use when implementing or reviewing Java-only Doc View production changes, especially PSI parsing, services, DTOs, UI, integrations, settings, export, or IntelliJ Platform behavior.

Jump to install

Repository: liuzhihang/doc-view
Last source activity: July 11, 2026 at 14:02
Detected SKILL.md language: English
Stars: 207
Forks: 53

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/liuzhihang/doc-view --skill doc-view-java-maintenance

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Doc View Java Maintenance

Use this skill for production plugin work after an observable behavior contract is apply-ready.

Read First

AGENTS.md

docs/architecture.md

Every active apply contextFiles path returned by OpenSpec; runtime work requires proposal/design/spec/tasks context

docs/contract-design.md for PSI, DTO, Markdown, upload, export, settings, writeback, or UI behavior

docs/performance-guide.md for PSI, recursion, cache, background task, rendering, export, upload, or UI responsiveness

docs/intellij-compatibility.md for IntelliJ API, Gradle platform, descriptor, extension, or compatibility work

Steps

Confirm the active OpenSpec change authorizes runtime files and defines expected behavior and validation.

Locate the narrow package boundary: service, utils, dto, ui, integration, config, provider, or action.

Write the failing contract test or fixture before production code.

Preserve Java-only production code and prefer existing services, DTOs, utilities, and public IntelliJ API patterns.

For PSI changes, validate Spring/Feign/Dubbo impact as applicable and guard recursion, invalid elements, Dumb Mode, read actions, and project disposal.

For UI/action work, keep update lightweight and heavy work off EDT.

For integration work, protect secrets and make authentication/network/server failures understandable.

Implement the smallest change, run targeted then full verification, and update OpenSpec tasks only after success.

Guardrails

Do not change generated Markdown shape, payloads, settings, UI, or compatibility without matching OpenSpec requirements.

Do not modify plugin.xml, Gradle, dependencies, or resources unless the approved change explicitly requires them.

Do not add Kotlin, Groovy, scripts, generated runtime sources, or new production languages.

Do not mark tasks complete before code and exact verification are complete.

Do not revert unrelated user changes.