business-doc-extract

Provide the published Axure HTML directory path and ask for module-level business documentation. The AI reads the prototype pages, proposes a generation plan, and after your confirmation writes requirement, dictionary, field, and index files under .wl-skills/docs/business.

Point the AI at the existing src/views module directory together with its api.md and mock files. It scans the code and generates module business documents, flagging inferred rules and fields as pending confirmation rather than treating them as facts.

It does not trigger for single-page verbal requests, single screenshots, bug fixes, or style tweaks. Those fragmentary tasks stay at the conversation level and never write into .wl-skills/docs/business, keeping the documentation clean.

Yes. Provide the new field entity or dictionary table and the target module. Only that module's field.md or dictionary.md is updated, with new entries marked as added or updated and obsolete ones marked deprecated instead of deleted.

No. Detailed interface contracts remain in each page directory's api.md. The module index only links to those files, so interface details are never duplicated inside the business documentation tree.

Fields inferred from prototypes or screenshots without backend confirmation are placed in a pending-confirmation section first. This prevents guessed fields from polluting the authoritative field table before product or backend review.