Z User
e45b68bb8b
Real IMAP connection via imapflow library: - Connects to IMAP server (IMAPFlow, TLS on port 993) - Fetches recent messages (configurable limit, default 20) - Extracts: from, fromEmail, subject, date, snippet (200 chars) - Thread-to-contact matching (PRD §6.1): 1. Match sender email against persons table 2. If no person match, extract domain and match against company.website 3. Returns matchedCompany + matchedPerson for each email - Audit-logged (action: crm.mailsync:imap) - Zod validated (host, port, user, password, folder, limit) - 502 on IMAP connection failure with detail - 400 on validation failure Tested: invalid creds → 502 'IMAP connection failed', missing host → 400
3.5 KiB
Executable File
name, description, visibility, mode, carrier, scenario, pattern_source, source_priority, triggers
| name | description | visibility | mode | carrier | scenario | pattern_source | source_priority | triggers | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| project-brief | Notebook-collage weekly digest template — spiral-bound reporter's notebook aesthetic with cobalt tape, mint folder tab, binder clip, receipt block, ruled baseline grid; built for AI-product / team / design weekly digests delivered as a downloadable high-res page. | public | template | long-form-article | weekly-digest | 清言周报-VOL18-notebook.html | skill-first |
|
Project Brief Template
Use this template for weekly / periodic digests that should feel like a hand-assembled reporter's notebook — issue-numbered, taped, clipped, ruled, with a clear physical metaphor.
Use When
- The artifact is a recurring digest (周报 / VOL.NN / Issue N) with multiple grouped entries.
- Sections include: new features, optimizations, bug fixes, links, notes — i.e. a changelog-shaped narrative.
- The voice is product-team or editorial-team-internal, not corporate.
- The deliverable will be exported / shared as a high-res image or PDF, not just a scrolling page.
Avoid When
- The content is a one-off announcement (use a social card or blog-post).
- The audience expects a corporate formal report — this is intentionally crafty and warm.
- The user wants a presentation / deck (use
ppt/). - The content is a marketing landing — wrong carrier entirely.
Required Reading
Read this SKILL.md first. Do not read 清言周报-VOL18-notebook.html by default.
Read the pattern only when you need concrete geometry — spiral hole spacing, tape angle and deckle, binder-clip placement, receipt-grid pattern, the 31px ruled baseline. Extract patterns; do not copy placeholder issue numbers, dates, feature names, or class names wholesale.
Design Strategy
Lock the issue's spine before placing decoration:
- Masthead — logo + date strip + 1-paragraph intro.
- Issue mark — cobalt tape with VOL.NN + binder clip.
- Table of contents — three-column grid pointing to numbered sections.
- Sections — each with a kicker (uppercase Spanish / English label) + Chinese title + indexed entries.
- One "physical" highlight block — receipt for optimizations, taped Polaroid for a feature, mint folder tab for an announcement.
- Closing lockup + colophon — QR / ticket / page-number metadata.
Each issue should follow the same spine — that's how a weekly builds identity over time.
Layout Bias
Prefer:
- mixed serif (FlyFlowerSong / Noto Serif SC) + sans (Noto Sans SC) + mono (JetBrains Mono) — each carries a role
- ruled baseline grid for body copy; entries align to it
- dashed dividers between entries, not solid rules
- one or two "physical" elements per page (tape / clip / receipt / folder tab) — not all of them at once
- index numbers (01 / 02 / 03) on entries; uppercase Latin kickers above CJK section titles
Avoid:
- emoji icons (the physical metaphor already does the warmth work)
- glossy gradients, drop shadows on every element, plastic stickers
- forcing every entry into the same card shape — the charm is in varied physical props
- copying the cobalt blue / mint green palette verbatim if the brand has its own colors — keep the metaphor, retheme the palette
Platform / Size
A4-portrait-leaning long page, designed to render as a single tall artifact (image / PDF). Not optimized for mobile feeds; if the user wants a mobile-shareable version, export sections as separate social cards.