open-design/skills/meeting-notes/SKILL.md
marco 5dd70b5016
Some checks failed
ci / Validate workspace (push) Successful in 12m32s
landing-page-ci / Validate landing page (push) Successful in 9m41s
landing-page-deploy / Deploy landing page (push) Failing after 5m23s
github-metrics / Generate repository metrics SVG (push) Failing after 2m3s
refresh-contributors-wall / Refresh contributors wall cache bust (push) Failing after 11s
Initial import: open-design source for helix-mind.ai distribution
This repository contains the open-design daemon CLI source code, built
and packaged at https://helix-mind.ai/cli/open-design/latest.tgz for use
by the HelixMind /design slash command.

Licenses: Apache-2.0 (root) + MIT (skills/*)
2026-05-06 20:50:24 +02:00

48 lines
1.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
name: meeting-notes
description: |
Meeting notes page — title bar with attendees, agenda checklist, decisions
block, action items table with owners + dates, and a "next meeting" footer.
Use when the brief mentions "meeting notes", "minutes", "1:1 notes",
"all-hands recap", or "会议纪要".
triggers:
- "meeting notes"
- "minutes"
- "1:1 notes"
- "all-hands recap"
- "会议纪要"
od:
mode: prototype
platform: desktop
scenario: operations
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
example_prompt: "Write up notes from a 60-minute Growth squad weekly — agenda, decisions, action items with owners, next meeting."
---
# Meeting Notes Skill
Produce a single-screen meeting notes page.
## Workflow
1. Read DESIGN.md.
2. Layout:
- Header: meeting title, date, time, location/Zoom, attendees row.
- Agenda checklist (46 items).
- Decisions panel — bulleted list with strong styling.
- Action items table with owner, due date, status.
- "Open questions" + "next meeting" footer.
3. Subdued colour palette, clear hierarchy.
## Output contract
```
<artifact identifier="notes-name" type="text/html" title="Meeting Notes">
<!doctype html>...</artifact>
```