flux-purr-developer-policy

Apply Flux Purr repository-wide developer policy. Use when Codex is acting as a developer inside this source tree and needs the repo-level rules before routing into developer operations, user operations, or other specialist skills.

Aller à l'installation

Dépôt: IvanLi-CN/flux-purr
Dernière activité de la source: 17 juin 2026 à 18:18
Langue détectée de SKILL.md: anglais
Étoiles: 0
Forks: 0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/IvanLi-CN/flux-purr --skill flux-purr-developer-policy

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

2 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

flux-purr-developer-operations

Run Flux Purr repository-internal developer operations safely. Use when Codex is already operating under the repo-level developer policy and needs devd, CLI, firmware/Web integration, release automation, calibration, artifact verification, mock HIL, or real HIL workflows from the source tree.

2026-06-17

flux-purr-user-operations

Operate released Flux Purr hardware as an end user. Use when Codex needs to guide or execute ordinary hardware operations through released flux-purr CLI/devd, browser Web Serial, USB port memory, firmware update checks, status/runtime/WiFi commands, or release-manifest-based upgrade decisions.

2026-05-30

Tout voir dans ce dépôt

Flux Purr Developer Policy

This is the repo-level policy layer for developer-role agents working inside the Flux Purr source tree.

The human-facing source of truth is docs/guides/flux-purr-developer-policy.md. Repo AGENTS.md keeps routing and non-bypassable hard gates. skills/flux-purr-developer-operations remains the repository-internal developer operations/HIL counterpart to the installed or released user surface; it is not the repo-wide developer policy.

Use this skill when

The task is source-tree development in this repository: firmware, web, devd, docs, specs, release automation, or source-level validation.

The agent is acting as a developer rather than an end user operating released tools.

Required routing

Read docs/guides/flux-purr-developer-policy.md first for the repo-wide developer rules and vocabulary.

For devd, CLI, Web/native bridge, release automation, calibration, artifact verify, dry-run flash, real flash, mock HIL, or real hardware validation, also read skills/flux-purr-developer-operations/SKILL.md.

For owner-facing operations through released flux-purr, released flux-purr-devd, or browser Web Serial, use skills/flux-purr-user-operations/SKILL.md instead of source-tree shortcuts.

If Flux Purr uses IsolaPurr as the external HUB or bench source, read $isolapurr-developer-operations only for the external device side.

Hard agent rules

Respect repo AGENTS.md for routing and non-bypassable hard gates.

Prefer repo checkout tooling; do not substitute global flux-purr or flux-purr-devd binaries for source-tree developer work.

Finish non-hardware validation before any real device or HIL step.

Do not perform flash, reset, serial write, selector changes, or port switching without an exact owner-authorized USB port.

Do not report mock smoke as hardware validation.

Keep specs, solutions, and project docs aligned when behavior, contracts, release policy, or safety boundaries change.

Do not change git remotes, upstreams, push targets, or credentials unless the owner explicitly asks.