omni-code

Use when designing UI with OpenPencil — creating layouts via op CLI, batch design DSL, or MCP tools. Covers PenNode schema, semantic roles, typography, color, spacing, and common component patterns.

Work with Figma .fig design files and the running OpenPencil editor — inspect structure, query nodes, analyze design tokens, export images/SVG/JSX, and modify designs programmatically. Use when asked to open, inspect, export, analyze, or edit .fig files, or to control the running OpenPencil app.

Use when creating, updating, prioritizing, or querying GitHub Project todo items for omni-stream-ai/omni-code, especially backlog drafts, issue promotion, status changes, labels, and priority edits.

Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.

Entrypoint structure, exit codes, cross-platform scripts. Use when building command line utilities, scripts, or applications.

Collect coverage using the coverage packge and create an LCOV report

Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.

Define and generate mock objects for external dependencies using `package:mockito` and `build_runner`. Use when unit testing classes that depend on complex external services like APIs or databases.

Replace the usage of `expect` and similar functions from `package:matcher` to `package:checks` equivalents.

Workflow for fixing package version conflicts. Use this when `pub get` fails due to incompatible package versions.

Execute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.

Use switch expressions and pattern matching where appropriate