From thinking-frameworks-skills
Checks technical terms in substacker draft claims against writer's glossary.md and field standards, flagging divergences as aligned, diverged-safe, or diverged-risky.
npx claudepluginhub lyndonkl/claude --plugin thinking-frameworks-skillsThis skill uses the workspace's default tool permissions.
```
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Per claim:
- [ ] Step 1: Tokenize claim for candidate terms (named concepts, TLAs, math)
- [ ] Step 2: Grep shared-context/glossary.md for each term
- [ ] Step 3: If found, pull writer's definition
- [ ] Step 4: Compare to field-standard (prior knowledge + optional WebSearch)
- [ ] Step 5: Emit: aligned | diverged-safe | diverged-risky
Term: "attention"
Writer's glossary: "the mechanism that lets tokens exchange information, including the residual bypass."
Field-standard: "the weighted sum softmax(QK^T/√d)V, excluding the residual."
Status: diverged-risky if post asserts "attention is O(n²)" — true under field definition, false-or-unclear under the writer's.
Output note: "Writer's glossary includes residual in 'attention'; field-standard excludes. Post's claim 'attention is O(n²) in memory' is true under field but misleading under writer's glossary. Consider disambiguating in-post or tightening the glossary."
aligned without actually checking the glossary file this run.no-glossary and treat field definition as governing.diverged-safe over diverged-risky — err toward non-blocking.