loci-preflight

Analyze compiled callees for CFG, timing, and energy risks in design plans.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/auroralabs-loci/loci-claude --skill loci-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loci-preflight
Source: https://github.com/auroralabs-loci/loci-claude/tree/main/skills/loci-preflight
Command: npx skills add https://github.com/auroralabs-loci/loci-claude --skill loci-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execution-aware preflight analysis for code changes, surfacing timing, energy, and control-flow risks on compiled callees before you write code.

Core Features & Use Cases

  • Plan-aware analysis: uses compiled artifacts to evaluate how a change will affect runtime behavior on hardware.
  • CFG, timing, and energy evaluation: provides actionable metrics to guide design decisions.
  • Guardrails for plan mode: ensures you only run preflight in planning context and before edits.

Quick Start

Describe a plan with a new function, then run loci-preflight in /plan mode to generate a complete preflight report.

Frequently Asked Questions about loci-preflight

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

FAQPage Schema
How do I check timing and energy risks before writing new code?

Hardware-aware preflight analysis identifies timing and energy risks by evaluating your design plan against compiled artifacts. It analyzes control flow graphs and existing callees to flag feasibility hazards and suggest adjustments before you write code.

What is execution-aware preflight for code planning?

Execution-aware preflight analyzes compiled artifacts to predict how planned code changes affect runtime behavior on hardware. It provides control flow, timing, and energy metrics to guide design decisions and ensure feasibility before implementation.

How do I run preflight analysis on a new function plan?

Describe your plan with the new function, then run the preflight analysis in plan mode to evaluate compiled callees. This generates a complete report with control flow, timing, and energy metrics, providing actionable guidance for your design.

Can I use preflight analysis after I have started editing code?

No, preflight analysis includes guardrails that restrict it to planning context before edits. It evaluates compiled artifacts and design plans to provide feasibility feedback, rather than analyzing code already being written or modified.

Does preflight static analysis work without compiled artifacts?

No, preflight analysis requires compiled artifacts to ground its hardware evaluation of existing callees. Without compiled artifacts, it cannot accurately assess control flow, timing, and energy risks or provide feasibility feedback.

What is the best way to evaluate hardware feasibility during software design?

Hardware-aware preflight analysis evaluates design plans against hardware constraints by checking compiled artifacts. It surfaces control flow, timing, and energy risks, providing actionable metrics to adjust your plan before implementation begins.