ant-product-maplisted

# ANT Product Map Use this skill to turn scattered product context into a simple map a non-technical builder can inspect, share, and hand to another agent or developer. The default output is a single static product-map.html file. Keep it readable, local, and evidence-based. ## Core Rules 1. Answer in the user's language. 2. Start from the user's goal, not from architecture. 3. Separate facts from assumptions. Mark unknowns explicitly. 4. Use simple labels: product, user, screens, flow, data, integrations, risks, next step. 5. Prefer a compact HTML map over a long Markdown report when the user wants a scheme/map. 6. Do not invent services, screens, payments, databases, or business logic that are not in evidence. 7. Keep the map useful for humans first and agents second. 8. Ask before publishing, deploying, overwriting an existing file, or using private/secret data. ## Workflow 1. Gather only enough context to map the product: - user notes or prompt; - README/docs if a repo exists; - package/app routes if relevant; - existing screenshots or HTML only when needed. 2. Extract the product shape: - what it is; - who it is for; - main promise; - key screens or states; - main user flow; - data and integrations; - unclear decisions. 3. Create a small HTML map with sections the user can scan. 4. Add short status labels: - known for evidence-backed facts; - assumption for likely but unconfirmed items; - unknown for missing decisions; -