logix-best-practices

Enforce Logix owner-lane routing and runtime verification boundaries in code.

4|1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/yoyooyooo/logix --skill logix-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logix-best-practices
Source: https://github.com/yoyooyooo/logix/tree/main/skills/logix-best-practices
Command: npx skills add https://github.com/yoyooyooo/logix --skill logix-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reduces broken Logix API usage and runtime/red-line violations by enforcing a single owner-lane workflow for generating, reviewing, and refactoring Logix code with evidence-friendly verification boundaries.

Core Features & Use Cases

  • Owner-lane API Guardrails: Enforces correct separation between remote facts (source), local soft facts (companion.lower), and final truth (rule/root/list/submit), plus React read/write routing.
  • Runtime Verification Boundaries: Keeps verification control-plane calls (Runtime.check/trial/compare via CLI) out of business authoring, preventing forbidden artifacts like report/evidence/scenario in production code.
  • Evidence-First Diagnostics Discipline: Directs how to validate transactions and diagnostics via stable anchors and slim JsonValue exports, and how to delegate live inspection to logix-cli.

Quick Start

Ask the AI to use logix-best-practices to review a Logix module and React/Form code for owner-lane correctness and verification boundary compliance.

Frequently Asked Questions about logix-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Logix code to follow the Module.logic to Program.make to Runtime.make workflow?

Logix code requires adhering to the Module.logic to Program.make to Runtime.make pipeline to enforce owner-lane routing and maintain runtime red-line compliance during API generation and refactoring.

What are the verification boundaries for Runtime.check, trial, and compare in Logix?

Runtime.check, trial, and compare calls must be restricted to verification control-plane contexts via CLI, keeping them out of business authoring to prevent forbidden artifacts like report, evidence, or scenario in production code.

How do I manage React Form read/write selectors and owner-lane routing in Logix?

React Form integration requires following strict read/write selector rules and owner-lane separation between remote facts, local soft facts via companion.lower, and final truth at rule, root, list, or submit levels.

Why am I getting forbidden artifacts like evidence or scenario in my Logix production code?

Forbidden artifacts appear when verification control-plane calls leak into business authoring; you must restrict Runtime diagnostics to appropriate verification contexts and delegate live inspection to logix-cli.

Can I use this approach to review existing Logix modules for owner-lane correctness?

Yes, you can review and refactor existing Logix modules and React Form code by applying agent-first guardrails to validate owner-lane correctness and verification boundary compliance across business, test, and CI workflows.