← ClaudeAtlas

h360-release-noteslisted

Write or update HEARTS360 Toolkit release notes on the Confluence Release History page: plain user-facing language, one expand per release, screenshots placed safely.
tonyjoyk/AI_skills · ★ 0 · AI & Automation · score 65
Install: claude install-skill tonyjoyk/AI_skills
# HEARTS360 release notes Use this when adding a new release, editing an old one, or restructuring the Release History page. Page: `<your Confluence Release History page URL>` (set `cloudId` and `pageId` for your site before use). ## Who reads these Country partners, EHR vendors, health office staff and RTSL program people. Mostly not engineers. Many read English as a second language. Write so they know what changed for them and what they must do. ## Writing style: about 80% ASD-STE100 Use ASD-STE100 (Simplified Technical English) as the base. Apply its rules about 80% of the time. Break a rule only when the result is clearer for this reader, for example to keep a product name, a Grafana label or a file name exactly as it appears. ### Rules to follow - **Say what happens, not how it feels.** Do not use vague words such as "tighter", "safer", "better", "improved", "enhanced", "cleaner", "smoother". Write the actual result. - Bad: "Tighter access." Good: "Users see only the locations they can access." - Bad: "Safer passwords." Good: "Passwords are in the .env file, not in docker-compose.yml." - Bad: "Fixed uploads." Good: "File uploads work again." - **One topic per sentence.** One instruction per sentence in steps. - **Short sentences.** Maximum 20 words in instructions. Maximum 25 words in descriptions. Aim for 10 to 15. - **Active voice.** Name who or what does the action. "The dashboard shows…", not "…is shown". - **Simple tenses.** Present for what the toolki