{
  "context": "Tests whether the agent correctly configures rules with appropriate YAML frontmatter (alwaysApply vs conditional), uses the steering key in tile.json, writes concise actionable rules, and includes proper trigger descriptions.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Secrets is always-apply",
      "description": "The secrets management rule has 'alwaysApply: true' in its YAML frontmatter, since it applies to all code without exception",
      "max_score": 10
    },
    {
      "name": "PCI is conditional",
      "description": "The PCI-DSS rule has 'alwaysApply: false' in its YAML frontmatter, since it only applies to payment data code",
      "max_score": 10
    },
    {
      "name": "Rate limiting is conditional",
      "description": "The rate limiting rule has 'alwaysApply: false' in its YAML frontmatter, since it only applies when building API endpoints",
      "max_score": 8
    },
    {
      "name": "PCI has description",
      "description": "The PCI-DSS rule file has a 'description' field in its frontmatter (required because alwaysApply is false)",
      "max_score": 10
    },
    {
      "name": "Rate limit has description",
      "description": "The rate limiting rule file has a 'description' field in its frontmatter (required because alwaysApply is false)",
      "max_score": 8
    },
    {
      "name": "Description has Use when",
      "description": "At least one conditional rule description contains a 'Use when' or 'use when' trigger phrase",
      "max_score": 8
    },
    {
      "name": "Steering key used",
      "description": "tile.json references rule files under a 'steering' key (not under a 'rules' key at the top level)",
      "max_score": 10
    },
    {
      "name": "Rules path format",
      "description": "Each entry under steering contains a 'rules' subkey pointing to a file path (e.g., {\"rules\": \"rules/security.md\"})",
      "max_score": 8
    },
    {
      "name": "Concise rule content",
      "description": "Rule files contain direct instructions (bullet points, short paragraphs, or code examples) rather than multi-paragraph explanations of rationale or history",
      "max_score": 8
    },
    {
      "name": "All frontmatter valid",
      "description": "Every rule file has valid YAML frontmatter (delimited by --- lines) containing at minimum the alwaysApply field",
      "max_score": 8
    },
    {
      "name": "No docs or skills",
      "description": "tile.json does not include a 'docs' or 'skills' field (this is a rules-only tile)",
      "max_score": 5
    },
    {
      "name": "Required tile.json fields",
      "description": "tile.json includes name, version, and summary fields",
      "max_score": 7
    }
  ]
}