Home-School Notice Optimizer

Problem

Teachers often post class-group notices from a few raw fields: time, place, reminders, and audience. Copying raw notes can feel abrupt, while drafting multiple versions manually risks missing safety reminders, leaking personal data, or using an inappropriate tone.

How it works

home-school-notice-optimizer reduces input to minimum fields such as topic, audience, stage, time, location, preparations, and style. It classifies the notice, extracts fields, and selects output from style_presets.yaml. It supports styles like formal, warm, brief, encouraging, safety, and low_interrupt; if one style is requested, it outputs only that style, otherwise it defaults to warm reminder, brief efficient, and a checklist. Safety-related cases append a serious safety supplement of 80–120 characters, avoiding panic language. It also adjusts wording by school stage: elementary notices are more concrete, junior-high notices stress rule awareness, and senior-high notices stress self-management and responsibility.

Boundaries

• Outputs copy-ready group messages without explaining the generation process.
• Keeps checklists to 5 items or fewer, action-only.
• If input is incomplete, lists at most 3 optional items, avoiding repeated follow-up.
• If names, phone numbers, or addresses appear, it reminds the user to desensitize them and keeps them out of the notice body.