skills-manager: Instructions file for Codex

AGENTS.md

This file provides guidance to WARP (warp.dev) when working with code in this repository.

Overview

Skills Manager is a macOS desktop app (Tauri 2 + React) that discovers, imports, edits, and deletes the SKILL.md-based skill packages used by ~12 AI coding agents (Claude Code, Cursor, Codex CLI, Copilot, etc.). All filesystem work happens against per-agent skills directories under the user's home (e.g. ~/.claude/skills/, ~/.codex/skills/).

Commands

package.json is the source of truth for scripts (the README's npm run tauri dev / npx tauri build also work via the Tauri CLI but differ in name):

• npm install — install JS deps (Rust deps build automatically on first Tauri run).
• npm run dev — run the full desktop app in dev mode (tauri dev; spawns Vite via beforeDevCommand).
• npm run dev:client — Vite-only frontend on http://localhost:5173 (no Rust backend; invoke calls will fail).
• npm run build — Vite build of the frontend into dist/ only. This is NOT the app build; it's the beforeBuildCommand Tauri runs.
• npm run tauri:build — full release build, then strips the quarantine attribute (xattr -cr) so the .app opens locally. Output: src-tauri/target/release/bundle/{dmg,macos}/.

There is no test, lint, or formatter tooling configured (no ESLint/Prettier/Vitest, no Rust tests). Do not invent test commands; validate changes by building and running the app.

Release & Versioning

Release versions must stay synchronized across:

1. package.json
2. package-lock.json
3. src-tauri/Cargo.toml
4. src-tauri/tauri.conf.json

Use SemVer:

• Patch (x.y.Z) for fixes only.
• Minor (x.Y.0) for user-facing UI/behavior changes or new functionality.
• Major (X.0.0) for breaking package/install/data compatibility changes.

Release checklist:

1. Decide the next version from the changes since the latest GitHub release.
2. Run npm version <version> --no-git-tag-version to update package.json and package-lock.json.
3. Manually update src-tauri/Cargo.toml and src-tauri/tauri.conf.json to the same version.
4. Add a dated section to CHANGE.md.
5. Confirm Apple Developer ID signing and notarization are configured before publishing a public macOS release. A valid release must not be ad-hoc signed: security find-identity -v -p codesigning should show a Developer ID Application identity, codesign -dv --verbose=4 <app> should show a TeamIdentifier, and spctl -a -vvv -t open <dmg> should accept the DMG.
6. Validate with npm run build and npm run tauri:build.
7. Only after signing/notarization verification passes, commit the version/changelog changes, tag the same commit as v<version>, push the branch and tag, then create a GitHub release from that tag.