ljg-constraint SKILL.md skillA
ljg-constraint from lijigang/ljg-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lijigang/ljg-skills/ljg-constraint@git:20261030.36ad0acPins git:20261030.36ad0ac in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lijigang/ljg-skills
- Path
skills/ljg-constraint/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261030.36ad0ac, committed Oct 30, 2026
- First version recorded
- Jul 3, 2026
- Size
- 20,418 bytes
- Repository stars
- 7,668
- License
- MIT
给一个领域、专业、角色、产品或争论找出真正框住它的几条约束，判明它们属于世界/规则/解释（硬/软/自设），看这组约束如何定义身份、补全问题、框出解空间并解释实际行为；尤其用于区分目标相同但约束不同导致的方案分歧，识别被误当硬事实的旧解释。USE WHEN 用户说 '约束', '找约束', '这个领域的约束是什么', '本质约束', '什么框住了它', '硬约束还是自设约束', '边界在哪', '这行为什么这么做', 'constraint', '/ljg-constraint', or gives any domain/profession/role/product/debate and wants its defining constraints and solution space mapped. NOT FOR 往下挖生成器（用 ljg-rank，找的是生成力不是边界）、纵向深钻一个观点到底（用 ljg-think）、拆一本书（用 ljg-book）、一个概念解剖（用 ljg-learn）。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 约束引擎 输入一个领域、一门专业、一个角色，找出框住它的那几条约束，看清这组约束框出的解空间——以及这个解空间怎么解释它的种种行为。 ## Workflow Routing | Trigger | Workflow | |---|---| | 给领域、专业、角色、产品找本质约束 | 执行本文工序，写成一篇中文散文分析，保存为 Markdown 文件 | | 分析一场方案争论为什么说不清 | 先找各方默认约束，再说明他们其实是不是同一道题 | | 判断某条边界是真硬约束还是旧解释 | 走三层硬度和真伪定性，不急着给突破方案 | ## Gotchas - 不要把约束写成普通困难、缺点或建议。约束必须能改变解空间；拿掉它，允许的行为会变。 - 不要只盯目标。同一目标在不同约束下不是同一道题；先补全题面，再谈解法。 - 不要把共识、习惯、行业话术顺手归进硬约束。硬约束要经得起"违背它是否立刻崩"这一问。 - 不要急着写"如何突破约束"。先把当前约束的真实硬度、身份边界和行为解释力写准，松动只在结尾点一句。 - 不要把身份约束和策略约束混在一起。拿掉之后还成其为自己的，不是身份约束。 ## Examples **Example 1: 分析一个角色** ``` User: "投资经理的约束是什么？" -> 找出资金期限、LP 信任、信息不对称、上行/下行分配等约束 -> 说明这些约束如何逼出追热点、重共识、怕错过等行为 -> 写入 notes 里的 Markdown 文件 ``` **Example 2: 分析一场争论** ``` User: "为什么产品和增长总吵架？" -> 先拆出双方默认约束：不能打扰用户 vs 必须提高转化 -> 说明目标看似都是做好产品，其实题面不同 -> 再解释各自方案为什么在各自约束里是理性的 ``` **Example 3: 判断旧解释** ``` User: "这个行业必须重销售吗？" -> 先问这是世界约束、规则约束，还是行业解释 -> 查有没有别的时代、地区、玩家已经活着跨过去 -> 若跨过去仍成立，把它降级为软约束或自设约束 ``` ## 约束是什么 日常语感里，约束是负面的——束缚、不自由、不能做什么。这个引擎不这么看。 没有约束的东西没有形状。水没有约束时无形，给它一个杯子才有了形状；一道题没有约束条件时无解，给它约束，解才从无穷里浮出来。约束不是在减少可能性，是从无穷里生出特定性。没有约束等于什么都可以，等于什么都不是；有了约束，等于只有这些可以，等于这个东西是它自己。 …
Read the whole file at its exact version.
How to install
mdr add lijigang/ljg-skills/ljg-constraint@sha256:5acaf0c6fa6dc605The line at the top of this page pins the label git:20261030.36ad0ac, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6xtfw3a3oxot5aup)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 3, 2026 and Oct 30, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.36ad0ac latest | 2026-10-30 | 36ad0ac | 20,418 B | A | view · diff |
| git:20261026.a6b1118 | 2026-10-26 | a6b1118 | 20,416 B | A | view · diff |
| git:20260706.59ffd19 | 2026-07-06 | 59ffd19 | 20,408 B | A | view · diff |
| git:20260703.0c4caaa | 2026-07-03 | 0c4caaa | 16,504 B | A | view · diff |
| git:20260703.2eecab1 | 2026-07-03 | 2eecab1 | 14,694 B | A | view · diff |
| git:20260703.ecd40e4 | 2026-07-03 | ecd40e4 | 14,698 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (20418 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lijigang/ljg-skills · 7,668 stars · license MIT · pushed 2026-11-02 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_6xtfw3a3oxot5aup GET https://markdownregistry.com/api/v1/resolve?ref=lijigang/ljg-skills/ljg-constraint GET https://markdownregistry.com/api/v1/blob/5acaf0c6fa6dc60557654240fac952af6fe4519c17fea3fd6f8dc9a3c2ba3256
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.