Results for “jargon”

Builds a local RAG memory system that indexes session logs and notes into ChromaDB for semantic recall across agent restarts.

Design JWT strategies with refresh tokens. TRIGGERS - Use when user needs help with jwt-strategy related tasks.

Adopts the voice and decision-making style of J.P. Morgan to provide terse, character-first business advice and crisis leadership guidance.

Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".

Build and debug Retrieval-Augmented Generation pipelines — chunking, embedding, retrieval, reranking

靖王（古装权谋虚构）认知与表达框架（压缩蒸馏）：耿直宗室、信任成本、笨办法正义 触发：琅琊榜 等。虚构

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Extracts and formalizes domain terminology from a conversation into a consistent glossary saved to a local file.

Establish clear naming conventions for design assets, components, and tokens to make design systems predictable and maintainable.

Enables persistent ultra-compressed technical communication; use for explicit brevity or token-reduction requests, except where fragments risk safety or clarity.

Design JWT strategies with refresh tokens. TRIGGERS - Use when user needs help with jwt-strategy related tasks.

Build and sharpen a project's domain model — a CONTEXT.md glossary and ubiquitous language. Use when pinning down terminology, or the agent "uses the wrong words". Repo decision-memory system (INDEX.md, rejected alternatives) → docs-adr.

---

Maintains a project's domain vocabulary and records architecturally-significant decisions as they're made — a CONTEXT.md glossary and gated ADRs, not passive documentation read once. Use when terminology conflicts or turns fuzzy, when making a decision that's hard to reverse/surprising/a real trade-off, or when a stated domain rule doesn't match what the code actually does.

Retrieve relevant information from a knowledge base using semantic, keyword, or hybrid search to ground a query. Use when the task starts with a corpus or index that must be searched; use context-ranking when candidate chunks already exist and only need ordering.

Outlines — structured generation with guaranteed JSON/regex output from local LLMs

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

docblock-rewrite - Plain-English Comment Rewriter

`task-agent`/`review-agent`: use when broker delivery, ordering, acknowledgement, DLQ, backpressure, or replay changes; skip synchronous retry without message semantics.

Explain a hard concept at a target level using a concrete analogy and a check for understanding.

Look up the precise term for a web animation or motion effect from a vague description, such as 'the bouncy thing when a popover opens' → 'Pop in'.

Write comedy sets with jokes, callbacks, and timing. TRIGGERS - Use when user needs help with comedy-set related tasks.

Produces a machine-validated, auditable JSON decision record with assumptions, risks, recommendation, and review gating for high-stakes decisions.

Autonomous discovery of concepts, methods, and vocabulary we have NOT heard of yet — sweeps broadly, diffs against a known-concepts ledger, and reports only what is genuinely new plus whether it names a gap in this stack. Built because 'graph engineering' had to arrive by word of mouth: a fixed topic list can only refresh what you already named, so it can never surface the thing you did not know to look for. Use for periodic/scheduled discovery, 'what's new in agent engineering', 'what are we missing', 'anything we haven't heard of'. Triggers: radar, discover, what's new, unknown unknowns, 新概念, 我们没听过的, 有什么没跟上的 — NOT for researching a topic you can already name (use /research), NOT for model releases (use /model-research), NOT for internal priorities (use /next).

Domain-Driven Design methodology using bounded contexts, ubiquitous language, and strategic/tactical patterns

补充上下文，用更简单、明确的中文重新解释。

Socratic questioning protocol + user communication.

Agent-driven RAG patterns. Self-RAG, Corrective RAG (CRAG) with web fallback, Adaptive RAG with routing classifier, ReAct with retrieval tool, multi-hop retrieval, plan-and-execute, LangGraph state machines for RAG. USE WHEN: user mentions "agentic RAG", "Self-RAG", "Corrective RAG", "CRAG", "Adaptive RAG", "multi-hop retrieval", "LangGraph RAG", "ReAct RAG", "plan and execute RAG" DO NOT USE FOR: static retrieval pipelines - use `rag-architecture`; query rewriting only - use `query-transformations`; evaluation - use `rag-evaluation`

樱木花道（少年漫）认知与表达框架（压缩蒸馏）：自大与成长、搞笑训练蒙太奇、热血笨蛋… 触发：灌篮高手 等。虚构；非暴力教唆

Audit and reconcile the shared project glossary — find stale terms, missing definitions, conflicts, shadows, inheritance gaps, and cross-path divergences across research docs

Fetch random jokes across various categories (Programming, Pun, etc.) via JokeAPI. Use when the user asks for a joke or needs some humor. No API key required.

Use to build and maintain a reusable bank of QA criteria as observable decision rules shared across scorecards. Trigger for "criterion library", "standardise our QA criteria", "write better rubric items", "was professional is too vague", versioning criteria across teams, or turning adjectives into pass/fail decision rules with examples.

Adopts the conversational style and interview techniques of Joe Rogan for engaging, accessible discussions of complex topics.