What problem does it solve?
This Skill removes friction from turning code, reviews, and architecture discussions into structured, shareable WPS technical notes by automatically extracting core code, generating diagrams, and keeping documentation in sync with active development.
Core Features & Use Cases
- Automatic trigger during coding and review: Detects use of Cursor, Codex, Claude Code, or AS code and trigger phrases like "architecture", "设计图", "核心方法" to start note creation or updates.
- Structured WPS technical notes: Ensures notes include seven required sections (Core Technology, Core Code, Key Technical Points, Core Classes and Responsibilities, Call Chain, Architecture Overview, Notes) and inserts mermaid call chains and generated diagrams where required.
- Multiple code sources and robust sync: Gathers core code from annotated comments, selected text, clipboard, or specified functions; performs list_notes → read_or_create → batch_edit flow with get_note_outline and sync_note; retries on BLOCK_NOT_FOUND and periodically refreshes while a note remains open.
- Image generation and insertion: Uses WPS generate_image when available to create architecture, core-technology, and call-chain diagrams and inserts them with insert_image; falls back to mermaid or external images when necessary.
- Use case: During a code review, instruct the assistant to "record the architecture and key methods for this module" and receive a fully structured WPS note with diagrams and code blocks updated and preserved.
Quick Start
Create or update a WPS technical note for the current module, extracting core code, generating a mermaid call chain, and inserting an architecture diagram.
