Concept Ledger
Paste the following prompt into your AI chat to install this skill:
Please install @user_15292d5a/yjkj-concept-ledger according to https://skillhub.cn/install/skillhub.md.
About this skill
Problem Being Solved
When technical discussion moves from brainstorming into implementation contexts such as interfaces or data structures, the same concept can be renamed repeatedly. funnel, sieve, and event filter may point to the same object; fuzzy metaphors such as green channel may be attached to an already Frozen concept like EventFilter. Concept Ledger addresses terminology chaos: synonym loops, definition drift, metaphor overreach, and large numbers of ad-hoc terms generated during vibe coding.
How It Works
The skill treats concepts as a living glossary. The Agent detects naming conflicts, metaphor overreach, and definition drift, then intervenes at appropriate moments in the conversation: proposing unified names, asking for concept boundaries, and confirming whether an item is Forming or Frozen. When an established concept is referenced inconsistently, it flags the mismatch; when a definition shifts, it asks whether the change deepens the same concept or creates a different one. Across sessions, Clear / Forming / Frozen items are restored, while unmarked Vague items are not retained by default.
Boundaries and Notes
It is useful for converging brainstorming, stabilizing unstable naming, and separating code terms from fuzzy metaphors. It is not needed when concepts are already stable and the discussion is pure implementation, or for simple Q&A and information retrieval. Avoid premature Frozen status and do not discard Vague concepts without review. The ledger replaces terminology chaos, not architectural design.
Use Cases
- Product and engineering keep renaming the same module during brainstorming, so `funnel`, `sieve`, and `event filter` need to be unified into a term that can be implemented in code.
- During interface work, a fuzzy metaphor like `green channel` is attached to an already frozen class, so the team needs to decide whether it is an alias, an undefined concept, or a discarded direction.
- `vibe coding` sessions create many ad-hoc terms, so `Clear / Forming / Frozen` concepts need to be retained across sessions while unretained `Vague` items are pruned.
- `message decay` shifts from auto-disappear to priority degradation during discussion, so definition drift must be detected and classified as a deepened concept or a separate concept.
Best For
- Engineers doing `vibe coding` with AI, who need to converge ad-hoc conversation terms into frozen, implementable concepts.
- Product owners responsible for requirement clarification, who need to turn fuzzy brainstorming metaphors into clear module boundaries.
- Engineering leads managing technical discussion, who need to retain stable terms across sessions and detect synonym loops or definition drift.
- Knowledge-management practitioners maintaining project glossaries, who need a living concept ledger that evolves with discussion instead of a one-time document.
Related Skills
Reads conversation-trace files to generate an animal- or mythology-based soul mirror card and Johari Window insights.
A Deling knowledge-base research workflow that clarifies intent, runs broad and vertical searches, supplements with web sources, validates diversity, and traces key claims.
A SiYuan knowledge-base management skill for double-link parent indexes, MOCs, numbered documents, tags, repo sync, and WeChat import workflows.
A structured workflow for academic literature reviews, covering multi-database search, screening, thematic synthesis, citation validation, and PDF output.