Content
30%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a thin skeleton: section headers and capability lists with no code, commands, or sequenced workflow, and several sections (Patterns, Anti-Patterns) are bare stubs. It is concise but largely unactionable and lacks any validation guidance for Firebase's risky operations (security rules, listeners, admin ops).
Suggestions
Add executable examples for the named capabilities, e.g. a security-rules snippet, a Firestore query pattern, and a modular SDK import example.
Fill in the Anti-Patterns sections with concrete do/don't pairs and validation checkpoints (e.g. test rules with the emulator before deploy).
Replace the truncated narrative intro with a brief overview and expand 'When to Use' with specific Firebase triggers instead of the generic placeholder.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and mostly lean, but it repeats the frontmatter narrative verbatim and that narrative is truncated mid-sentence ('You advocate for Firebase w'), so it is efficient yet includes redundant/unfinished padding that could be trimmed. | 3 / 5 |
Actionability | Only high-level hints are given ('Import only what you need for smaller bundles', 'Secure your data with proper rules from day one') with no code, commands, or specific steps, matching the minimal-concrete-guidance anchor. | 2 / 5 |
Workflow Clarity | There is no multi-step sequence at all, only flat section headers, so steps and validation checkpoints are entirely absent. | 1 / 5 |
Progressive Disclosure | Sections exist (Capabilities, Patterns, Anti-Patterns, Related, When to Use) with no bundle files to organize, but the Patterns and Anti-Patterns sections are empty stubs, leaving the organization incomplete. | 3 / 5 |
Total | 9 / 20 Passed |