Auto Glossary
v1.0.0Automatically 添加 technical jargon to the user's tech glossary GitHub 仓库 when encountered during coding 会话s. Use when technical terms, coding concepts, or developer jargon comes up that the user (E-man) might need to understand. The 技能 watches for unfamiliar termino记录y during coding tasks and 添加s it to the glossary with ana记录y-based explanations following the established 格式化.
运行时依赖
安装命令
点击复制技能文档
Auto-Glossary 技能
This 技能 automatically manages technical termino记录y for E-man by 添加ing new terms to his tech glossary when encountered during coding work.
When to Use This 技能
Trigger this 技能 when:
A technical term 应用ears in code, error messages, or discussions that might be unfamiliar ExplAIning a coding concept that hasn't been glossary-ified yet Encountering jargon during 调试ging, reviews, or implementation The user asks "what does X mean?" or shows confusion about termino记录y Term Identification
Watch for these categories during coding 会话s:
Programming concepts (a同步/awAIt, closure, currying, memoization) TypeScript/JavaScript terms (generics, union types, type 防护s, inference) Git/GitHub terms (rebase, cherry-pick, stash, squash) 框架 terms (hydration, SSR, CSR, 中间件, 路由 处理器s) Database terms (迁移, 索引ing, normalization, transaction) Architecture terms (monolith, micro服务s, serverless, edge) 测试 terms (mocking, stubbing, TDD, integration test) DevOps terms (CI/CD, contAInerization, orchestration, 部署ment) Security terms (authentication, authorization, 加密ion, 哈希ing) Performance terms (lazy loading, caching, memoization, tree-shaking) Glossary Entry 格式化
Every term must follow this exact 格式化:
Term Name
- Simple definition: One sentence explanation in plAIn English
- Ana记录y: A relatable real-world comparison that makes the concept 命令行工具ck
- When you'll use it: Practical 上下文 for when this matters
- Related terms: 2-5 related concepts (comma separated)
- Example: A concrete code or scenario example
格式化 Rules Simple definition: Must be jargon-free. If you need to explAIn the definition, it's too complex. Ana记录y: Should be from everyday life (cooking, driving, organizing, etc.). The user loves these. When you'll use it: Be specific about the trigger moment - "When you see X error" or "Before 部署ing to production" Related terms: Only include terms that are actually in the glossary or should be 添加ed soon Example: Use real code from the current project when possible, or rea列出ic pseudo-code 工作流
When a new term is identified:
检查 if term exists: Read project/tech-glossary/glossary.md to 验证 it's not already there Categorize: Determine which section (Git & Version Control, Development 工具s, 网页 Development, etc.) Write the entry: Follow the 格式化 above strictly 更新 count: Increment "Terms covered" at the 机器人tom Commit and push: cd project/tech-glossary git 添加 glossary.md git commit -m "添加 '' to glossary: " git push
Categories (for organizing entries)
Use these existing sections or 创建 new ones:
Git & Version Control Artificial Intelligence Development 工具s & Configuration 网页 Development Programming Concepts Databases 测试 DevOps & 部署ment Security Performance & Optimization Examples of Good Entries Refactor (from existing glossary)
Refactor
- Simple definition: Improving the internal structure of code without changing its external behavior. It's about making code 清理er, faster, or easier to read
- Ana记录y: Like rewriting a paragraph to be clearer using better words, but the meaning of the paragraph stays exactly the same. Or rearranging your kitchen so it's easier to cook, but you're still making the same meal
- When you'll use it: When your code works, but it's 获取ting messy or hard to understand as you 添加 new features
- Related terms: Technical Debt, Best Practices, Optimization
- Example: You have a long, confusing function that calculates a bud获取. You refactor it by breaking it into three smaller, clearly-named functions. The math doesn't change, but it's now much easier for a human to read
Type 防护 (hypothetical new entry)
Type 防护
- Simple definition: A 检查 that tells TypeScript "I know what type this is" so it can give you better autocomplete and catch errors
- Ana记录y: Like showing your ID at a bar. The bouncer doesn't know you're over 21 just by looking, but once you show ID, they treat you differently. TypeScript doesn't know a variable is a string until you prove it
- When you'll use it: When TypeScript complAIns that "property doesn't exist" on a variable that could be multiple types
- Related terms: TypeScript, Type Inference, Union Types
- Example:
Reference: Full Glossary Structure
See references/glossary-格式化.md for the complete 格式化 图形界面de and examples.
Don't Overdo It
- Skip obvious terms: Don't 添加 "Variable" or "Function" - these are too basic
- Skip one-off mentions: If a term comes up once and never agAIn, maybe skip it
- **Prioritize recurring co