Menu
Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note. Writes explicit "None" style sections whenever the user does not provide details.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
A presentation system for agent-made PPTs โ born for the talk, not just the template. It turns raw material into an AST (audience-state-transfer) outline with per-page visual-enhancement decisions (image / SVG diagram / video), hands a production brief to a downstream renderer (HTML-PPT skills or native PPTX), then runs a capped 3-round presentation checkup (ๆผ่ฎฒไฝๆฃ) on the rendered deck. It never renders slides itself. Use before generating PPT/HTML slides from raw material, and after rendering when the user says things like "็ป่ฟไปฝ deck ๅๆผ่ฎฒไฝๆฃ" or "PPT ๆธฒๆ่ดจๆฃ". If all you want is one beautiful template page with no outline and no checkup, a rendering skill alone is enough.
A first-30-days onboarding module for new hospitality hires โ the behaviors, the practice, the checks, and the manager follow-up. Built as a decision-grade professional training deck for new hires, managers.
Open Design's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.
Open Design + BYOK: choosing and wiring your own model, hands-on โ cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
Open Design's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
Open Design's enterprise AI-adoption brief: local-first agents at work, the risk controls, the ROI, and the rollout plan. Built as a decision-grade AI literacy deck for leadership, IT, security.
| name | release-notes-one-pager |
| description | Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note. Writes explicit "None" style sections whenever the user does not provide details. |
| triggers | ["release notes","changelog","what's new","version update","change log","release summary"] |
| od | {"mode":"prototype","platform":"desktop","scenario":"engineering","preview":{"type":"html","entry":"index.html"},"design_system":{"requires":true,"sections":["color","typography","layout","components"]},"example_prompt":"Write release notes for v2.3.1 with Added, Fixed, Breaking changes, Known issues, and an Upgrade note."} |
Produce a single-page release notes document in HTML.
release-notes-one-pager/
โโโ SKILL.md โ this file
โโโ example.html โ quality bar and style reference
โโโ assets/
โ โโโ template.html โ local seed file to copy to project index.html
โโโ references/
โโโ checklist.md โ P0 / P1 / P2 gates
โโโ layouts.md โ local section skeletons
Do not write CSS from scratch unless the user explicitly asks for a bespoke structure.
assets/template.html.references/layouts.md.DESIGN.md and map it to the six :root variables.Copy assets/template.html to project index.html.
Update:
<title>#added, #fixed, #upgrade-note)href destination, or omit the topnav CTA entirely if no real destination existsid attributesInside <main id="content">, compose this section order:
id="added").id="fixed").id="breaking-changes").id="known-issues").id="upgrade-note").For every CTA in the emitted HTML (topnav, hero, closing strip), replace both the visible label and the href destination with real, safe values. If no real destination is available, omit the CTA entirelyโdo not use a placeholder such as href="#", a misleading page-anchor, or REPLACE_WITH_REAL_URL. Hero CTAs are optional; only add them when real destinations exist.
If the user does not provide details, do not invent them. Write explicit placeholders:
No summary provided.No additions providedNo fixes providedNoneNone reportedNo upgrade actions required based on provided informationIf release version or date is missing, use โ and label the field rather than guessing.
Run references/checklist.md. Every P0 must pass.
Wrap output as:
<artifact identifier="release-notes-one-pager" type="text/html" title="Release Notes">
<!doctype html>
<html>...</html>
</artifact>
One sentence before the artifact. Nothing after </artifact>.