chilla

Run mixed Tauri Rust and TypeScript lint, typecheck, formatting, and verification commands. Use when Codex is asked to lint, check, test, verify, or prepare Rust/TypeScript/Tauri changes in this repository, especially after editing src-tauri, src, package.json, Taskfile.yml, flake.nix, or agent lint scripts.

Use when setting up or verifying Apple Developer ID signing credentials, Apple app-specific passwords, kinko secret storage, or local macOS notarization readiness for chilla without recording credential values.

Use when Codex should validate chilla macOS desktop behavior, Tauri app launches, visible UI flows, or browser/app interactions after implementation or bug fixes, and Computer Use tools may be available.

Use when code changes in this repository should be validated by actually launching the local chilla app. After modifying runtime-affecting code, rebuild the debug app when needed and launch `target/debug/chilla` yourself instead of telling the user to run it.

Use when building, signing, notarizing, validating, or publishing macOS `.app` and `.dmg` release artifacts for this repository. Covers the Tauri macOS release config, local `task bundle-macos-dmg`, Apple signing/notarization inputs, GitHub Actions release workflow, and post-release tap follow-up.

Use when building and publishing the Nix tarball release artifacts for this repository with `nix build`. Covers flake target selection, tarball packaging, installer compatibility, GitHub release creation, and Homebrew tap updates for the current tarball-based cask path.

Use when writing, reviewing, or refactoring Rust code. Provides type safety patterns, error handling, project layout, and async programming guidelines.

Use when writing, reviewing, or refactoring TypeScript code. Provides type safety patterns, error handling, project layout, and async programming guidelines.

Use when implementing or reviewing Tauri features that span the Bun/TypeScript frontend and the Rust backend. Provides boundary, verification, and project-structure guidance for desktop app development.

Use when creating or organizing design documents. Provides directory structure, file naming, and content guidelines for design specs and references.

Use when creating implementation plans from design documents. Provides plan structure, status tracking, and progress logging guidelines.

Use this skill when creating or modifying GitHub Actions workflow files (.github/workflows/*.yml). Ensures all actions are pinned by commit SHA, permissions are minimized, script injection is prevented, and other supply chain security best practices are applied.

Use when writing Rust code that interacts with dependencies, handles credentials, executes commands, or manages configuration. Provides supply chain attack countermeasures at the code level including safe dependency usage, credential handling, subprocess hardening, and build.rs/proc-macro awareness. Adapted from Shai-Hulud npm attack lessons.

Use when adding, updating, or auditing Cargo dependencies. Provides supply chain attack countermeasures including Cargo.lock verification, cargo-audit, cargo-deny, cargo-vet, build.rs security, and CI/CD pipeline hardening. Adapted from Shai-Hulud npm attack lessons.

Use when publishing Rust crates to crates.io or managing crate repositories. Provides supply chain attack countermeasures including crates.io token management, CI/CD publishing pipelines, and pre-publish security checklists. Adapted from Shai-Hulud npm attack lessons.