pftom
a98096a042
- Created .gitignore to exclude build artifacts and dependencies. - Added index.html as the main entry point for the application. - Included LICENSE file with Apache 2.0 terms. - Initialized package.json and package-lock.json for project dependencies. - Added pnpm-lock.yaml for package management. - Created QUICKSTART.md for setup instructions. - Added README.md and README.zh-CN.md for project documentation in English and Chinese.
1.3 KiB
1.3 KiB
name, description, triggers, ocd
| name | description | triggers | ocd | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 Skill
Produce a single-screen meeting notes page.
Workflow
- Read DESIGN.md.
- 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.
- Subdued colour palette, clear hierarchy.
Output contract
<artifact identifier="notes-name" type="text/html" title="Meeting Notes">
<!doctype html>...</artifact>