Results for “terminology”

Cashu: single-mint Chaumian e-cash for Bitcoin Lightning. NUTs (Notation, Usage, and Terminology specs) define mint protocol, payment flow, blind signatures. USE WHEN: integrating Cashu mints/wallets, building NUT-compliant apps, comparing with Fedimint.

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

Applied Topology Design Skill

Design and format publication-quality tables: column order, row grouping, notes, precision, reproducibility.

Manage Category entities — taxonomies and classification schemes that group other entities by type, area, tier, etc. Use when defining a new classification axis (priority levels, bug severity, feature tier, product area) that other entities will be tagged with.

Build ontology logs (ologs) from problem descriptions using categorical foundations. Use when designing problem taxonomies, classifying tasks for routing, building knowledge libraries, establishing formal analogies between domains via functor search, or translating between natural language and database schemas. NOT for OWL/RDF ontology work, query tuning, or graph modeling without functional-arrow discipline.

Grilling

Audits hidden assumptions in decisions or beliefs by classifying them into fact, convention, belief, or interest-driven, ranking by fragility and impact, then rebuilding conclusions from verified premises. Supports English and Chinese.

Implements finite automata, regular expressions, parsers, and lexers for building text processors and pattern matchers.

Converting repository changes into detailed learning documents. Use when turning diffs into teaching materials, recording design decisions, or creating onboarding materials for new members.

融合分类系统与规则抽象能力，构建基于规则的分类体系，支持规则驱动的分类需求和规则执行。

Engineering observability and reliability: SLO/SLI design, distributed tracing, alerting, dashboards, capacity planning, toil automation, reliability review. Use for instrumentation or SLO definition.

First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English.

Comprehensive guide to orb. Master the concepts, implementation, best practices, and real-world applications of orb in professional environments.

Defines structural schemas, data ontologies, and interaction boundaries for autonomous entities and synthetic data architectures.

Defines naming conventions for Apex classes, methods, variables, constants, custom objects, triggers, and test classes.

Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approaches. Use when sizing a market opportunity, estimating addressable market, preparing for investor pitches, or evaluating market entry.

Advanced Topology Design Skill

Publication Specialist - Writing, Review, Pre-registration & Quality Assurance Light VS applied: Avoids template-based writing + audience-specific message design Absorbed G3 (Peer Review Strategist), G4 (Pre-registration Composer), F1-F3 (Quality functions) capabilities Use when: writing abstracts, creating summaries, peer review response, pre-registration, reporting checklists, reproducibility Triggers: abstract, plain language, press release, summary, communication, peer review, revision, pre-registration, OSF, PRISMA, CONSORT, reproducibility

Imported skill __init__ from anthropic

Imported skill _template from vercel

Use to define handoff standards for support transfers and to measure whether context survives the handoff — cold vs warm, required fields, and re-ask rate after transfer. Trigger for "transfer protocol", "warm handoff", "customers repeat themselves after transfer", "ping-pong between teams", "what should agents include when transferring", handoff quality, or re-ask rate after escalation.

Context Management

Expert 10x engineer skill for interpreting and implementing code from shorthand, quasi-code, and natural language descriptions. Use when collaborators provide incomplete code snippets, pseudo-code, or descriptions with potential typos or incorrect terminology. Excels at translating non-technical or semi-technical descriptions into production-quality code.

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.