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.

Ir a la instalación

Repositorio: liuzhihang/doc-view
Última actividad en el origen: 11 de julio de 2026 a las 14:02
Idioma detectado de SKILL.md: inglés
Estrellas: 207
Forks: 53

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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.