Use when source data and receiving code may disagree on fields, shape, optionality, enum values, or business meaning. Trigger for real data wiring, mock replacement, field/schema/type mismatch, snake_case/camelCase, 接口对接, 字段对齐, 类型对不上. Do not use for styling, copy, imports, or no-boundary renames.
Use when the user explicitly asks to clean, compact, prune, trim, deduplicate, optimize, or reduce Wingman memory, or asks to resolve stale or conflicting memory rules.
Use when Wingman memory is already known enabled in the current repository and starting non-trivial coding, debugging, planning, review, API integration, or business-logic work, or when the user explicitly asks to load or read Wingman memory.
Use when the user explicitly invokes `/memory-setup` or explicitly asks to initialize Wingman memory files in the current repository. Do not use for ordinary work, memory loading, memory syncing, or setup of unrelated tools.
Use when Wingman memory is already known enabled in the current repository and progress, decisions, business logic, API contracts, state flow, field mappings, or durable project knowledge should be recorded, or when the user explicitly asks to sync Wingman memory.
Use when recording, registering, or updating a project feature, flow, page, component, module, utility, pattern, contract, domain, or business concept into Wingman's project map for future discovery and reuse/reference decisions. Trigger for 登记, 记录, 加入项目地图, 以后 AI 能找到, catalog, register, record, add to project map, feature inventory, capability map, or reusable capability. Do not use for explaining code, editing code, summarizing a file, or writing memory/history unless the user asks to add project-map knowledge.
Use when locating existing project features, flows, pages, modules, components, utilities, patterns, contracts, business concepts, or similar functionality before answering where something is or before building related functionality. Trigger for 项目里有没有做过, 在哪里, 类似功能, 已有功能, 复用, 不要重复造轮子, 项目里叫什么, 哪些文件, 找一下, existing feature, similar functionality, where is, reuse, avoid rebuilding, project concept, feature inventory, capability map, or implementation already exists. Do not use for pure styling, isolated bug fixes, code explanation, or tests unless the user asks for existing/related capability discovery.
Use when starting a Wingman-enabled coding session, adapting Wingman across AI coding platforms, deciding which Wingman skill applies, or interpreting Wingman plugin-level instructions versus project-local instructions.