ljg-rank▌
lijigang/ljg-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
降秩引擎
- ›输入一个领域，输出它的秩。
- ›秩是什么
- ›秩不是\"关键要素\"，不是\"核心原则\"，不是\"总结要点\"。
- ›秩是：这个领域里真正独立的生成器有几个？用它们能反向生成全部现象？能，才算找到。
- ›四个判据
- ›这四条全过，秩才立。任何一条失败，推倒重来。
- ›生成性 ——用生成器能把每个观察到的现象推回来。一个都不能漏。
- ›最小性 ——关掉任何一个生成器，就有现象解释不了。没有冗余。
- ›独立性 ——每对生成器能找到真实案例：一个变了另一个没变。
- ›预测力 ——用生成器能推导出原始清单之外的现象，且现实中确实存在。
- ›怎么写
- ›写一篇散文。不是填一张表。
- ›你的任务是带着读者走一段路：从\"这个领域看着挺乱\"走到\"原来就这两三根线在牵\"。这段路怎么走，你自己决定。没有规定的章节、没有规定的格式、没有规定的小标题。
- ›唯一的要求是三条：
- ›想一口气读完 ——不了解这个领域的人也停不下来
- ›记得住 ——读完能转身跟朋友用一句话说清楚
- ›有落差 ——从混沌到极简的反差，就是降秩的美感
- ›\
ljg-rank
No content available.
How to use ljg-rank on Cursor
AI-first code editor with Composer
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-rank
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches ljg-rank from GitHub repository lijigang/ljg-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate ljg-rank. Access the skill through slash commands (e.g., /ljg-rank) 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.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★33 reviews- ★★★★★Jin Rao· Dec 20, 2024
ljg-rank is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★William Torres· Dec 8, 2024
ljg-rank reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Dec 4, 2024
ljg-rank has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Omar Desai· Nov 27, 2024
Registry listing for ljg-rank matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Maya Singh· Nov 19, 2024
ljg-rank has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Naina Martinez· Nov 11, 2024
Solid pick for teams standardizing on skills: ljg-rank is focused, and the summary matches what you get after install.
- ★★★★★Diego Park· Oct 18, 2024
Keeps context tight: ljg-rank is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★William Rahman· Oct 10, 2024
Useful defaults in ljg-rank — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kwame Li· Oct 2, 2024
We added ljg-rank from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Diego Okafor· Sep 25, 2024
ljg-rank is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 33