Jiang lens concept writer
Skill apresmoi/jianglens/.codex/skills/jiang-lens-concept-writer
Use this skill when creating or improving one public Jiang Lens concept page from dated source refs, episode reads, semantic bundles, proposals, and existing atlas links.From its SKILL.md
npx -y skills add apresmoi/jianglens --skill jiang-lens-concept-writerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.7 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it
Jiang Lens Concept Writer
Use this to build one serious public concept page. Examples: poetry as virus, guide as trap, eschatology, game theory, sacred machine, false authority, free will, reciprocity, attention capture.
Inputs
- processed episode reads,
- semantic bundles,
- transcript refs,
- proposals from
jiang-corpus-impact-pass, - existing docs under
website/src/content/docs/lens*.md, - compiled lens points from
website/src/data/lens/link-index.json.
Output
Usually:
website/src/content/docs/lens/<concept-slug>.md
Concept pages are public reader-facing pages. They should not read like internal documentation.
Every concept page should be entry-point resilient. Do not assume the reader already read /introduction or the atlas. If you use words such as corpus, lens, episode, source trail, or agent, define them in local context or write around them.
Shape
Write as a compact chapter:
- Open as if the reader landed directly on this page. Name the concept, the Jiang Lens context, and the kind of Jiang source material carrying it.
- Define the key nouns and verbs.
- Explain the mechanism: how the thing works.
- Move through source clusters chronologically when chronology matters.
- Preserve vivid Jiang formulations and concrete scenes.
- Keep ambivalence: how the same mechanism can reveal, save, trap, dominate, erase, or create hell.
- Add diagnostics that help a reader apply the lens.
- Link related concepts.
Important concept pages can be 2,000-4,000 words if the evidence supports it. Do not pad. Do not leave them skeletal.
Size Governance
Compression does not mean every recurring source belongs on the same page.
- Treat roughly 2,000-6,000 words as the healthy range for most mature concept pages. This is not a hard cap, but crossing it should force a structure check.
- A page over about 6,000 words or 20 distinct Jiang sources is a split-review candidate. Before appending, ask whether a section has become its own reusable mechanism.
- A page over about 8,000 words or 25 distinct Jiang sources should normally become a parent plus child concepts, unless the PR or proposal explains why the evidence still belongs in one reader-held lens.
- A page with fewer than 4 distinct Jiang sources is usually a seed, relation, section, or proposal rather than a mature public concept. Publish or keep it only when the mechanism is strong enough to be reused before the corpus is fully developed.
- If a new source only adds another example to an already large page, prefer a compact impact decision or child-page proposal over more prose.
Corpus Anchor
Before writing or expanding a concept, check whether the corpus already has a better home for the mechanism:
- search existing lens pages for neighboring language and lens points,
- inspect topic aliases so spelling/plural variants do not create fake concepts,
- compare against strong episode reads and semantic signature moments,
- preserve older and newer dated formulations instead of privileging processing order.
Create a new page only when the idea is a reusable mechanism that cannot be absorbed into an existing concept without losing force. If the idea is really an alias, relation, chronology note, or example, update the existing page instead.
Evidence
Use Markdown inline evidence marks:
[visible source-grounded phrase]{evidence="video:<source-slug>@transcript:v1#seg-0001"}
Mark the phrase that depends on the source, not the whole paragraph. The first ref should visibly support the marked phrase.
Use lens points for durable, reusable anchors:
<!-- lens-point id="guide-trap-necessary-guide" concept="guide-becomes-trap" evidence="video:predictive-history-6m1z-v3wgok@transcript:v1#seg-0014" -->
<span id="guide-trap-necessary-guide" class="lens-point-anchor"></span>
The guide becomes a trap exactly there...
Keep lens point blocks compact enough to make a useful hover.
Chronology
Dates matter when Jiang changes, intensifies, contradicts, or tests a position. Older sources remain historical evidence. Newer sources can define the latest visible position only when exact dated refs support that.
Use dates in prose, chronology sections, source-cluster notes, or popovers. Do not make every section title a date unless the page is explicitly a timeline.
Judge Gate
Before handoff, use jiang-lens-judge. Patch actionable findings, then run:
node ops/scripts/compile-content.mjs
node ops/scripts/validate-content.mjs
cd website && npm run build
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.