explainx.ainewsletter3.4k
Productivity

ljg-card▌

lijigang/ljg-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/lijigang/ljg-skills --skill ljg-card
0 commentsdiscussion
summary

将内容铸成可见的形态。内容进去，PNG 出来。模具决定形状。

skill.md

ljg-card: 铸

将内容铸成可见的形态。内容进去，PNG 出来。模具决定形状。

参数

参数 模具 尺寸 说明
-l（默认） 长图 1080 x auto 单张阅读卡，内容自动撑高
-i 信息图 1080 x auto 内容驱动的自适应视觉布局
-m 多卡 1080 x 1440 自动切分为多张阅读卡片
-v 视觉笔记 1080 x auto 手绘风格 sketchnote，动态选择风格路线
-c 漫画 1080 x auto 日式黑白漫画风格，动态选择漫画家视觉语言
-w 白板 1080 x auto 白板马克笔风格，结构化框图+箭头+彩色标记

约束

本 skill 输出为视觉文件（PNG），不适用 L0 中的 Org-mode、Denote 和 ASCII-only 规范。

共享基础

获取内容

  • URL --> WebFetch 获取
  • 粘贴文本 --> 直接使用
  • 文件路径 --> Read 获取

文件命名

从内容提取标题或核心思想作为 {name}（中文直接用，去标点，≤ 20 字符）。

截图工具

node ~/.claude/skills/ljg-card/assets/capture.js <html> <png> <width> <height> [fullpage]

依赖：~/.claude/skills/ljg-card/node_modules/ 中的 playwright。如报错：

cd ~/.claude/skills/ljg-card && npm install playwright && npx playwright install chromium

Footer

  • 左侧：logo + 李继刚（已硬编码在模板中）
  • 右侧：内容来源（可选）——有明确来源时显示（如作者名、arxiv ID、网站名等），无来源时留空。使用 {{SOURCE_LINE}} 变量：有来源时填 <span class="info-source">来源文字</span>，否则空字符串。适用于 -l、-i、-v、-c、-w 模具（-m 多卡无 footer，不适用）。

交付

  1. 报告文件路径

品味准则

所有模具共享。执行任何模具前，先 Read references/taste.md，作为视觉质量底线贯穿全流程。

核心：反 AI 生成痕迹——禁 Inter 字体、禁纯黑、禁三等分卡片、禁居中 Hero、禁 AI 文案腔、禁假数据。

执行

根据参数选择模具，Read references/taste.md + 对应的 mode 文件，按步骤执行：

-l（默认）：长图

Read references/mode-long.md，按其步骤执行。

模板：assets/long_template.html

-i：信息图

Read references/mode-infograph.md，按其步骤执行。

模板：assets/infograph_template.html

-m：多卡

Read references/mode-poster.md，按其步骤执行。

模板：assets/poster_template.html

-v：视觉笔记

Read references/mode-sketchnote.md，按其步骤执行。

模板：assets/sketchnote_template.html

-c：漫画

Read references/mode-comic.md，按其步骤执行。

模板：assets/comic_template.html

-w：白板

Read references/mode-whiteboard.md，按其步骤执行。

模板：assets/whiteboard_template.html

how to use ljg-card

How to use ljg-card on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add ljg-card
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/lijigang/ljg-skills --skill ljg-card

The skills CLI fetches ljg-card from GitHub repository lijigang/ljg-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ljg-card

Reload or restart Cursor to activate ljg-card. Access the skill through slash commands (e.g., /ljg-card) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.6★★★★★65 reviews
  • ★★★★★Ira Ramirez· Dec 24, 2024

    ljg-card has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Min Lopez· Dec 12, 2024

    Keeps context tight: ljg-card is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Aanya Srinivasan· Dec 8, 2024

    ljg-card reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Xiao Gupta· Dec 8, 2024

    Useful defaults in ljg-card — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Aarav Taylor· Nov 27, 2024

    Registry listing for ljg-card matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Sofia Garcia· Nov 27, 2024

    ljg-card is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Sakshi Patil· Nov 15, 2024

    Solid pick for teams standardizing on skills: ljg-card is focused, and the summary matches what you get after install.

  • ★★★★★Zaid Jain· Nov 15, 2024

    Keeps context tight: ljg-card is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Jin Srinivasan· Nov 3, 2024

    ljg-card has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Jin Iyer· Oct 22, 2024

    ljg-card fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 65

1 / 7