Skip to content
FunCoding

Search

Search docs, Skills and MCP

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 "电子指南".

前端开发100kdesign-templates/digital-eguide/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/nexu-io/open-design/digital-eguide/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Digital E-Guide Skill

Produce a two-page digital guide preview side-by-side. Cover on the inline-start, inside spread on the inline-end. Lifestyle creator tone, lots of negative space, serif display headings, careful column rhythm.

Workflow

  1. 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.
  2. 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.
  3. 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" — & and guide italic).
      • 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 to inline-end: for Latin scripts use large italic display and accent color; for Arabic, Persian, and Urdu use regular or light emphasis (no italics); for Hebrew use regular or light emphasis (no italics). Include attribution. (script-aware)
      • Bottom strip with "EXERCISE" callout (mono label + 1 sentence prompt in italic).
      • Footer: chapter title + page 18 mono.
  4. 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-id on cover, spread, toc, pull-quote, exercise.
  5. 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.

Similar Skills

frontend-design
anthropics/skills180k

frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Frontend

web-artifacts-builder
anthropics/skills180k

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

Frontend

performance-optimization
addyosmani/agent-skills103k

performance-optimization

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

Frontend

api-and-interface-design
addyosmani/agent-skills103k

api-and-interface-design

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

Frontend

frontend-ui-engineering
addyosmani/agent-skills103k

frontend-ui-engineering

Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

Frontend

design-is
thedotmack/claude-mem99k

design-is

Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design audit", or asks for a critique that should lead to a plan.

Frontend