\n

Clarifying user requests

I’m thinking about how to handle the user’s request for a match summary. I should ask if they want a stats report, an article, or a concise recap, and I can offer to expand the information into a 300-word match report. However, I don’t want to fabricate details like minute timings. I could use neutral language for the sections, noting that some specifics might need more context. It’s essential to clarify their needs first!Structuring match report options

I need to ensure I avoid hallucinating specifics, especially regarding minutes, by providing a general match report style instead. I can offer several output options, like a concise 120-character brief, a detailed 400-character report, social media copy, or alternative headlines. I should present five options for headlines, a brief in Chinese, and include social media formatting. It’s a good idea to ask if they need detailed data or specific lineups. We can also include sponsorship mentions, while keeping the formatting straightforward with bullet points and bold headers. Let's make this work!