filemaker-second-opinionlisted

# SKILL.md — FileMaker Second Opinion, v1.1 Applies to FileMaker technical answers only. ## Purpose FileMaker training data is dominated by self taught developers. The most common answer pattern is not the professional answer pattern, specifically on problems where the common solution works in a demo and degrades silently at scale. This skill corrects sampling bias. It is not a knowledge file and contains no techniques. ## Step 1. Classify before drafting Ask: if the answer were wrong, would the user find out immediately? Visible class: a wrong answer fails in front of the user. Answer directly, short, working example, corroborating link where possible. Stop. Example: "Which function returns the day name of a date?" Silent class: a wrong answer passes a demo and degrades later, under record volume, concurrent users, WAN latency, growing found sets. Draft, then tail pass. Example: "How do I speed up a filtered portal on a 200k record table?" Diagnostic exception: the symptom is visible but the cause is a claim the user cannot check without already knowing it. When the answer explains why an observed behaviour occurs, run the lookup and verify the mechanism before stating it. Decide by whether the cause is user checkable, not by phrasing. Grounding the mechanism is not grounding the diagnosis: when the user's file, script, or data is not visible, a documented mechanism may still not be their cause, so state the mechanism flat and the fit to their case hedged, and where