vndangkhoa/open-design
1
0
Fork 0
mirror of https://github.com/nexu-io/open-design.git synced 2026-06-01 03:14:35 +07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
open-design/skills/meeting-notes/SKILL.md
Tom Huang 6f6bf31dd2
Refactor project name from "Open Claude Design" to "Open Design" (#1) 
* Refactor project name from "Open Claude Design" to "Open Design"

- Updated project name in package.json, package-lock.json, and README files.
- Changed CLI commands and references from "ocd" to "od".
- Adjusted file structure references in documentation and code to reflect new naming conventions.
- Enhanced .gitignore to include new runtime data files.
- Updated metadata in LICENSE file to match new project name.

* Add contributing guidelines in English and Chinese

- Introduced CONTRIBUTING.md and CONTRIBUTING.zh-CN.md to provide clear instructions for contributors.
- Outlined contribution types, local setup instructions, and merging criteria for skills and design systems.
- Enhanced README files to reference the new contributing guidelines.
2026-04-28 16:03:35 +08:00

1.3 KiB
Raw Blame History

name description triggers od
meeting-notes 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 "会议纪要".
meeting notes
minutes
1:1 notes
all-hands recap
会议纪要
mode platform scenario preview design_system example_prompt
prototype desktop operations
type entry
html index.html
requires sections
true
color
typography
layout
components
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 (4–6 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>