I think we can provide a template for analyzing the match, but I should clarify details like the opponent, match date, and injuries. The user hasn't specified the opponent or timeframe, so maybe I could mention terms like [[NEWS.CONTENT_HTML]]quot;bogey team[[NEWS.CONTENT_HTML]]quot; to indicate potential opponents. It's a bit risky to assume, so I'll offer a generic analysis framework while asking for specifics. I can also include general data points and propose to write a match preview in Chinese, asking them for any other details they might want.Constructing match analysis guidelines
I need to be concise while avoiding heavy formatting. Maybe I should offer a short analysis with placeholders. I could provide scenarios, like if the opponent is Man City, and mention that Arsenal beat them in the 2023 community shield and October league match, signaling a shift in dynamics. Against Liverpool, it's trickier since results have been mixed. To play it safe, I should ask for the opponent and match date, while offering a flexible skeleton and possible analysis angles. This way, I can adapt quickly once I get their confirmation.Drafting match preview guidelines
Based on the guidelines, I shouldn’t over-format, but using bullets is fine. I can start by asking, [[NEWS.CONTENT_HTML]]quot;What format are you looking for? (Pre-match preview/analysis/betting angle)?[[NEWS.CONTENT_HTML]]quot; I should list key elements like injury reports, data comparisons (xG/xGA, PPDA, set-pieces), crucial matchups, and tactical strategies.
If the user wants a quick article, I can provide a fill-in-the-blank draft. I think it’s best to create a short three-paragraph piece with neutral language, avoiding specific numbers, and referring to a “strong opponent/bogey team.” I’ll also ensure we ask for the opponent and match time while offering to deliver a structured preview with sections covering key information, data highlights, tactical insights, and predicted lineups.