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.

Ir a la instalación

Repositorio: IvanLi-CN/flux-purr
Última actividad en el origen: 17 de junio de 2026 a las 18:18
Idioma detectado de SKILL.md: inglés
Estrellas: 0
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

2 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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

Ver todos los de este repositorio

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.