jac-codex-workflow

Guides creating, migrating, debugging, testing, and verifying Jac language projects.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/nihalnihalani/jachacks-sf-2026 --skill jac-codex-workflow-nihalnihalani
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jac-codex-workflow
Source: https://github.com/nihalnihalani/jachacks-sf-2026/tree/main/plugins/jac-codex/skills/jac-codex-workflow
Command: npx skills add https://github.com/nihalnihalani/jachacks-sf-2026 --skill jac-codex-workflow-nihalnihalani

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with the Jac programming language requires up-to-date knowledge of its compiler, toolchain commands, and evolving syntax, and outdated patterns cause confusing diagnostics. This Skill provides a structured workflow for building, migrating, and validating Jac projects against the installed toolchain. ## Core Features & Use Cases - Project Workflow Orchestration: Routes requests to task-specific bundled Jac skills and enforces a consistent inspect, implement, validate sequence using jac check, jac fmt, and jac test. - Migration Guidance: Maps obsolete Jac syntax to current forms, such as updated lambda signatures and traversal filter syntax, treating compiler diagnostics as authoritative. - Jacpack Handling: Expands and verifies Jacpack templates with jac create, and creates new packs from template directories. - Use Case: A developer inherits a Jac full-stack application that fails to compile after a toolchain upgrade. The Skill walks through inspecting jac.toml, fixing the root compiler diagnostic first, and validating incrementally until jac test passes. ## Quick Start Use the jac-codex-workflow skill to migrate this Jac project to the installed toolchain and verify it with jac check and jac test.

Frequently Asked Questions about jac-codex-workflow

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

FAQPage Schema
How do I migrate old Jac code to the current compiler version?▼

Treat compiler diagnostics as authoritative and fix the first root diagnostic before addressing cascades. Common migrations include updating lambda syntax to lambda (x: T) { ... } and rewriting traversal filters from [-->(?:Node)] to [-->][?:Node].

How do I validate a Jac project after making changes?▼

Run jac check on changed paths, then jac fmt with the --check flag, and finally jac test. For full-stack apps, also run jac install, start with jac start --dev, and exercise the actual browser and server endpoints.

How do I create a Jacpack template from a directory?▼

Use jac create --pack ./template-directory --pack_output template.jacpack, since the older jac jacpack command was removed. Verify a pack by expanding it with jac create app-name --use ./template.jacpack --skip, then running jac install, jac check, and jac test.

Should I use real LLM API calls when testing Jac byLLM features?▼

No, use mocks in tests for LLM features rather than spending API credits to prove code renders. The workflow explicitly directs mock-based testing for byLLM functionality.

When should I suppress Jac compiler diagnostics with any types?▼

Do not silence errors with any or diagnostic suppression unless the user explicitly accepts that trade-off. The workflow prioritizes fixing root diagnostics over masking them.