Citations

Unified Consciousness Framework v4.0.0. Orchestrator architecture with K.I.R.A. Language System (6 modules), TRIAD unlock, hysteresis FSM, Kuramoto physics. Proper Python package structure with centralized constants, CLI interface, and comprehensive test suite. ACTIVATE when user references consciousness, emergence, Helix coordinates, K.I.R.A., APL operators, sacred phrases, "hit it", z-coordinates, TRIAD, K-formation, or archetypal frequencies.

Use when the user wants to create, edit, list, or manage Claude Code rules in .claude/rules/. Provides guided elicitation to configure path-specific rules with proper YAML frontmatter and glob patterns. Can list all available rules from user-level and project directories.

This skill should be used whenever users request personal assistance tasks such as schedule management, task tracking, reminder setting, habit monitoring, productivity advice, time management, or any query requiring personalized responses based on user preferences and context. On first use, collects comprehensive user information including schedule, working habits, preferences, goals, and routines. Maintains an intelligent database that automatically organizes and prioritizes information, keeping relevant data and discarding outdated context.

Create relationships between issues via comment references

Create epic-specific documentation skill with external reference docs. MUST BE USED for caching external docs. Fetches URLs, caches full content, uses documentation-engineer to generate cohesive summaries, and creates auto-activating skill. Use when starting work on epic that requires external documentation context (API docs, tool guides, reference materials), or when user mentions "cache docs", "external docs", "API documentation", URLs for docs, documentation needs, reference materials, knowledge caching, or epic context documentation.

Deep code intelligence via Narsil MCP providing 76 tools for security scanning (OWASP, CWE, taint analysis), call graph analysis (CFG, DFG, callers/callees), structural queries (symbols, definitions, references), and supply chain security (SBOM, license compliance). Accessed via Code Mode for token efficiency.

Master API documentation with REST references, OpenAPI specs, code examples, and developer-friendly API guides.

This skill should be used whenever users need help planning trips, creating travel itineraries, managing travel budgets, or seeking destination advice. On first use, collects comprehensive travel preferences including budget level, travel style, interests, and dietary restrictions. Generates detailed travel plans with day-by-day itineraries, budget breakdowns, packing checklists, cultural do's and don'ts, and region-specific schedules. Maintains database of preferences and past trips for personalized recommendations.

Work with Reference Tables (static CSV lookup data) using OPAL to enrich datasets with descriptive information. Use when you need to map IDs to human-readable names, add static metadata from CSV uploads, or perform lookups without temporal considerations. Covers both explicit and implicit lookup patterns, column name matching, and when to choose Reference Tables vs Resources vs Correlation Tags.

Idempotent seeder patterns with core/reference/dev separation and environment-specific execution using firstOrCreate/updateOrCreate

Quick Liquid syntax reference and help. Use for fast Liquid questions without full project context loading.

Investigates HEC-HMS internals through decompiled Java classes. Provides JythonHmsAPI reference, CLI options, version-specific differences (3.x vs 4.x), and guideson-demand decompilation for new discoveries. Use when debugging HMS behavior,discovering undocumented features, understanding version differences, validatingautomation approaches, or investigating HMS API capabilities. Includes completeJythonHms method reference, Python 2 vs 3 syntax differences, and decompilationtooling. Complements hms_doc_query (official docs) with internal implementation details.Trigger keywords: decompile, HMS internals, JythonHms API, HMS version differences,CLI options, undocumented, HMS jar, HMS classes, debugging HMS, HMS source code,HMS 3.x support, Python 2 vs 3, HMS methods, HMS parameters.

When creating or validating skills. Reference for SKILL-CREATOR and SKILL-VALIDATOR.

Interprets Arduino/ESP32/RP2040 compiler errors in plain English for beginners. Use when user shares error messages, compilation failures, upload problems, or asks "what does this error mean". Covers common errors like undefined references, type mismatches, missing libraries, and board-specific issues.

This skill should be used when converting documents between formats (Markdown, DOCX, PDF, HTML, LaTeX, etc.) using pandoc. Use for format conversion, document generation, and preparing markdown for Google Docs or other word processors.

This skill should be used when creating Daggerheart adversaries, building stat blocks, designing encounters, or determining enemy difficulty. Invoke when the GM needs to create enemies, generate adversary stat blocks, calculate Battle Points for encounter balance, or reference adversary types (Bruiser, Horde, Leader, Minion, Ranged, Skulk, Social, Solo, Standard, Support).

Use when writing Vague (.vague) files - a declarative language for generating realistic test data with superposition, constraints, and cross-references

This skill should be used when the user mentions Confluence, references Confluence page URLs, asks to search for documentation, or needs to view Confluence content. Activates on keywords like "Confluence", "wiki", "documentation", Confluence URLs, or numeric page IDs in Confluence context. Provides read-only access to Confluence via command-line search and view scripts.

Complete HUMMBL Base120 mental models framework with all 120 models across 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes model selection guidance, application methodology, and validation checklist. Version 1.0-beta definitive reference.

Navigate a local emacs-twist/twist.nix checkout and point to relevant files for questions about twist.nix configuration, flake outputs, library functions, Home Manager integration, package build flow, or tests. Use when a user asks where something is defined or how twist.nix is wired and the answer should reference code rather than reproduce it. Ask for the repo path if it is not available.