# Suggestion Schema

When this skill produces review output, prefer two files:

- Markdown summary for humans
- JSON suggestions for deterministic follow-up edits

Recommended JSON shape:

```json
{
  "date": "2026-03-27",
  "based_on_days": 7,
  "alias_suggestions": [
    {
      "from": "Agent",
      "to": "AI Agent",
      "reason": "High overlap with existing repository terminology."
    }
  ],
  "stopword_suggestions": [
    {
      "term": "??",
      "reason": "Too generic to be useful for filtering."
    }
  ],
  "interest_keyword_suggestions": [
    {
      "term": "MCP",
      "reason": "Repeated high-frequency term aligned with current learning focus."
    }
  ],
  "watch_terms": [
    {
      "term": "OpenClaw",
      "reason": "Trending recently but not enough history yet."
    }
  ]
}
```

Rules:

- Only output suggestions, never claim they are already applied.
- Avoid suggesting changes that would directly edit `filter_rules.json`.
- Prefer small, reviewable batches over large refactors.
- If evidence is weak, put the term in `watch_terms` instead of alias or stopword suggestions.