digital-eguide
A two-spread digital e-guide preview — page 1 is a cover (display title, author, "What's inside" stats, table of contents teaser); page 2 is a spread (lesson body with pull-quote and a step list). Lifestyle / creator brand tone. Use when the brief asks for an "e-guide", "digital guide", "lookbook", "lead magnet", "creator guide", "playbook", "PDF guide", or "电子指南".
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- od
- { "mode": "prototype", "craft": { "requires": [ "typography", "typography-hierarchy", "typography-hierarchy-editorial", "rtl-and-bidi" ] }, "preview": { "type": "html", "entry": "index.html" }, "featured": 6, "platform": "desktop", "scenario": "marketing", "design_system": { "requires": true, "sections": [ "color", "typography", "layout", "components" ] }, "example_prompt": "Design 'The Creator's Style & Format Guide' — cover page and one inside spread, lifestyle creator brand." }
- name
- digital-eguide
- triggers
- [ "e-guide", "digital guide", "lead magnet", "lookbook", "creator guide", "playbook", "pdf guide", "ebook", "电子指南", "电子书" ]
- description
- A two-spread digital e-guide preview — page 1 is a cover (display title, author, "What's inside" stats, table of contents teaser); page 2 is a spread (lesson body with pull-quote and a step list). Lifestyle / creator brand tone. Use when the brief asks for an "e-guide", "digital guide", "lookbook", "lead magnet", "creator guide", "playbook", "PDF guide", or "电子指南".
02 资源文件 2
- 参考文档example.html11.4 KB
- 参考文档open-design.json11.0 KB
03 SKILL.md 正文
Digital E-Guide Skill
Produce a two-page digital guide preview side-by-side. Cover on the left, inside spread on the right. Lifestyle creator tone, lots of negative space, serif display headings, careful column rhythm.
Workflow
- Read the active DESIGN.md (injected above). Pick a serif display token for the title (italic ligatures encouraged), a body serif for long-form, and a mono token for stats / labels.
- Pick the topic + author from the brief. Generate a real title (e.g. "The Creator's Style & Format Guide"), a real subtitle, and a one-line author byline.
- Layout — center two pages on a tinted backdrop:
- Page 1 — cover:
- Eyebrow ("STYLE & FORMAT GUIDE FOR CREATORS").
- Display title with mixed weights and one italic flourish word
("The Creator's Style & Format guide" —
&andguideitalic). - 3-cell stat row ("16 PRINCIPLES OF STYLE", "38 DOS & DON'TS",
"1 BLOCK, ZERO TEMPLATES") in mono, separated by
·. - "What's inside" header with a 2-column TOC (chapters + page numbers in mono, leader dots).
- Footer: "FIND YOUR VOICE" + page 01 mono.
- Subtle decorative dot or sticker (CSS) in a corner.
- Page 2 — spread:
- Eyebrow with chapter number + name ("CHAPTER 02 · TONE").
- Display sub-title ("Write like you talk — only sharper.").
- 2-column body: opening paragraph + a numbered 4-step list ("01 Pick the rule", "02 Drop the filler"…).
- Pull-quote pinned right-side: large italic display, accent color, with attribution.
- Bottom strip with "EXERCISE" callout (mono label + 1 sentence prompt in italic).
- Footer: chapter title + page 18 mono.
- Page 1 — cover:
- Write a single HTML document:
<!doctype html>through</html>, CSS inline.- Pages are 600×860 paper-tone cards with 6px shadow, slight rotation opposing each other (±0.6deg) for a magazine-on-desk feel.
data-od-idon cover, spread, toc, pull-quote, exercise.
- Self-check:
- Type hierarchy is editorial — title owns page 1, sub-title owns page 2.
- Italic accent appears once per page.
- Mono used only for labels, stats, and TOC numbers.
Output contract
Emit between <artifact> tags:
<artifact identifier="eguide-slug" type="text/html" title="E-Guide — Title">
<!doctype html>
<html>...</html>
</artifact>
One sentence before the artifact, nothing after.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.