Add initial project structure with essential files

- 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.
This commit is contained in:
pftom
2026-04-28 12:25:59 +08:00
commit a98096a042
258 changed files with 67862 additions and 0 deletions
+47
View File
@@ -0,0 +1,47 @@
---
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"
- "会议纪要"
ocd:
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>
```