When should I use the OE Architectural Guardrails?

Consult this skill before modifying routing logic, implementing new detection regex, or debugging workflow issues like ignored inputs.

How does this skill handle LLM signals vs. Regex?

It enforces a hierarchy where unified detection and LLM signals are prioritized to ensure regex doesn't accidentally override complex AI intent.

Does it help with date and unit accuracy?

Yes, it includes guidelines for data anchoring to distinguish between different date types and ensures LLM verbalization matches raw data exactly.

What is the primary purpose of this skill?

It ensures that any modifications to the OpenEvent-AI codebase follow strict architectural rules to prevent routing errors and state corruption.

OpenEvent Architectural Guardrails

Name: OpenEvent Architectural Guardrails
Author: shami-ah

byshami-ah

Desarrollo de API

Enforces architectural standards and workflow logic integrity for the OpenEvent-AI platform.

Acerca de

This skill provides Claude with the essential architectural rules and bug-prevention checklists required to safely modify the OpenEvent-AI workflow system. It ensures that changes to routing, state management, and detection logic adhere to specific pipeline orders and idempotency requirements. By consulting this skill, developers can prevent common pitfalls like 'lost messages' or 'wrong step' bugs when working on complex intake handlers, triggers, and gatekeeper logic, maintaining the reliability of the entire event-processing engine.

Características Principales

Ensures accurate data anchoring for date and price extraction
Enforces strict pipeline execution order for workflow steps
Manages hybrid handling for simultaneous user intents and questions
Provides bug prevention checklists for routing and state modifications
0 GitHub stars
Validates idempotency in confirmation and verification gates

Casos de Uso

Implementing new detection logic or regex-based data capture
Debugging state-related bugs like 'lost messages' or incorrect workflow steps
Modifying event intake, routing logic, or pre-route handlers

Acerca de

Características Principales

Ensures accurate data anchoring for date and price extraction
Enforces strict pipeline execution order for workflow steps
Manages hybrid handling for simultaneous user intents and questions
Provides bug prevention checklists for routing and state modifications
0 GitHub stars
Validates idempotency in confirmation and verification gates

Casos de Uso

Implementing new detection logic or regex-based data capture
Debugging state-related bugs like 'lost messages' or incorrect workflow steps
Modifying event intake, routing logic, or pre-route handlers