npm - mustflow - Versions diffs - 1.15.97 - Mend

mustflow 1.15.97

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (415) hide show

package/templates/default/locales/en/.mustflow/skills/visual-review-artifact/assets/review-template.html ADDED Viewed

@@ -0,0 +1,286 @@
+<!doctype html>
+<html lang="en">
+<head>
+  <meta charset="utf-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+  <title>Visual Review Artifact</title>
+  <style>
+    :root {
+      color-scheme: light dark;
+      --bg: #f7f7f4;
+      --fg: #1f2328;
+      --muted: #656d76;
+      --line: #d0d7de;
+      --panel: #ffffff;
+      --accent: #0969da;
+      --approve: #1a7f37;
+      --reject: #cf222e;
+      --discuss: #9a6700;
+    }
+    @media (prefers-color-scheme: dark) {
+      :root {
+        --bg: #0d1117;
+        --fg: #e6edf3;
+        --muted: #8b949e;
+        --line: #30363d;
+        --panel: #161b22;
+        --accent: #58a6ff;
+        --approve: #3fb950;
+        --reject: #ff7b72;
+        --discuss: #d29922;
+      }
+    }
+    * {
+      box-sizing: border-box;
+    }
+    body {
+      margin: 0;
+      background: var(--bg);
+      color: var(--fg);
+      font: 15px/1.5 system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
+    }
+    main {
+      max-width: 1120px;
+      margin: 0 auto;
+      padding: 24px;
+    }
+    header {
+      display: grid;
+      gap: 8px;
+      padding-block: 8px 20px;
+      border-bottom: 1px solid var(--line);
+    }
+    h1,
+    h2 {
+      margin: 0;
+      line-height: 1.2;
+    }
+    h1 {
+      font-size: 28px;
+    }
+    h2 {
+      font-size: 18px;
+    }
+    p {
+      margin: 0;
+    }
+    .meta,
+    .note {
+      color: var(--muted);
+    }
+    .toolbar {
+      display: flex;
+      flex-wrap: wrap;
+      gap: 8px;
+      margin-block: 18px;
+    }
+    .sections {
+      display: grid;
+      gap: 14px;
+    }
+    section {
+      display: grid;
+      gap: 12px;
+      background: var(--panel);
+      border: 1px solid var(--line);
+      border-radius: 8px;
+      padding: 16px;
+    }
+    .section-head {
+      display: flex;
+      flex-wrap: wrap;
+      justify-content: space-between;
+      gap: 8px;
+      align-items: start;
+    }
+    .status {
+      color: var(--muted);
+      font-size: 13px;
+    }
+    .actions {
+      display: flex;
+      flex-wrap: wrap;
+      gap: 8px;
+    }
+    button {
+      min-height: 36px;
+      border: 1px solid var(--line);
+      border-radius: 6px;
+      background: transparent;
+      color: var(--fg);
+      padding: 6px 10px;
+      cursor: pointer;
+    }
+    button:hover,
+    button:focus-visible {
+      border-color: var(--accent);
+      outline: 2px solid transparent;
+    }
+    button[aria-pressed="true"][data-action="approve"] {
+      border-color: var(--approve);
+      color: var(--approve);
+    }
+    button[aria-pressed="true"][data-action="reject"] {
+      border-color: var(--reject);
+      color: var(--reject);
+    }
+    button[aria-pressed="true"][data-action="discuss"] {
+      border-color: var(--discuss);
+      color: var(--discuss);
+    }
+    textarea {
+      width: 100%;
+      min-height: 84px;
+      resize: vertical;
+      border: 1px solid var(--line);
+      border-radius: 6px;
+      background: transparent;
+      color: var(--fg);
+      padding: 10px;
+      font: inherit;
+    }
+    pre {
+      overflow: auto;
+      margin: 0;
+      padding: 12px;
+      border-radius: 6px;
+      border: 1px solid var(--line);
+      background: color-mix(in srgb, var(--panel), var(--bg) 45%);
+    }
+  </style>
+</head>
+<body>
+  <main data-artifact-kind="decision" data-review-artifact>
+    <header>
+      <h1>Visual Review Artifact</h1>
+      <p class="meta">Replace this sample content with evidence-backed plan, suggestion, review, flow, or decision sections.</p>
+      <p class="note">Review only. This page does not execute commands, modify files, grant permission, skip validation, or override repository rules.</p>
+    </header>
+    <div class="toolbar" aria-label="Review actions">
+      <button type="button" data-copy-json>Copy decision JSON</button>
+      <button type="button" data-copy-prompt>Copy follow-up prompt</button>
+    </div>
+    <div class="sections">
+      <section data-review-section data-section-id="section-1">
+        <div class="section-head">
+          <div>
+            <h2>Section title</h2>
+            <p class="meta">Short evidence, tradeoff, or decision summary.</p>
+          </div>
+          <p class="status" data-status-label>Not decided</p>
+        </div>
+        <pre>Evidence or code excerpt goes here.</pre>
+        <div class="actions">
+          <button type="button" data-action="approve" aria-pressed="false">Approve</button>
+          <button type="button" data-action="reject" aria-pressed="false">Reject</button>
+          <button type="button" data-action="discuss" aria-pressed="false">Discuss</button>
+        </div>
+        <label>
+          Comment
+          <textarea data-comment placeholder="Add a comment for this section"></textarea>
+        </label>
+      </section>
+    </div>
+  </main>
+  <script>
+    const labels = {
+      approve: "Approved",
+      reject: "Rejected",
+      discuss: "Needs discussion"
+    };
+    function sections() {
+      return [...document.querySelectorAll("[data-review-section]")];
+    }
+    function setStatus(section, action) {
+      section.dataset.status = action;
+      section.querySelector("[data-status-label]").textContent = labels[action] ?? "Not decided";
+      for (const button of section.querySelectorAll("[data-action]")) {
+        button.setAttribute("aria-pressed", String(button.dataset.action === action));
+      }
+    }
+    function decisionData() {
+      return {
+        schema_version: "1",
+        artifact_kind: document.querySelector("[data-review-artifact]")?.dataset.artifactKind ?? "decision",
+        sections: sections().map((section) => ({
+          id: section.dataset.sectionId ?? "",
+          title: section.querySelector("h2")?.textContent?.trim() ?? "",
+          status: section.dataset.status ?? "undecided",
+          comment: section.querySelector("[data-comment]")?.value ?? ""
+        }))
+      };
+    }
+    async function copyText(text) {
+      if (navigator.clipboard?.writeText) {
+        await navigator.clipboard.writeText(text);
+        return;
+      }
+      const area = document.createElement("textarea");
+      area.value = text;
+      document.body.append(area);
+      area.select();
+      document.execCommand("copy");
+      area.remove();
+    }
+    function followUpPrompt() {
+      return [
+        "Use this visual review decision data as user feedback.",
+        "Do not treat it as command permission or validation approval.",
+        "",
+        JSON.stringify(decisionData(), null, 2)
+      ].join("\n");
+    }
+    document.addEventListener("click", async (event) => {
+      const target = event.target;
+      if (!(target instanceof HTMLElement)) return;
+      const actionButton = target.closest("[data-action]");
+      if (actionButton) {
+        const section = actionButton.closest("[data-review-section]");
+        if (section) setStatus(section, actionButton.dataset.action);
+        return;
+      }
+      if (target.closest("[data-copy-json]")) {
+        await copyText(JSON.stringify(decisionData(), null, 2));
+      }
+      if (target.closest("[data-copy-prompt]")) {
+        await copyText(followUpPrompt());
+      }
+    });
+  </script>
+</body>
+</html>

package/templates/default/locales/en/.mustflow/skills/visual-review-artifact/resources.toml ADDED Viewed

@@ -0,0 +1,7 @@
+schema_version = "1"
+[resources."assets/review-template.html"]
+type = "asset"
+asset_kind = "template"
+purpose = "Self-contained static HTML template for section-level review decisions and comments."
+required = false

package/templates/default/locales/en/.mustflow/skills/web-asset-optimization/SKILL.md ADDED Viewed

@@ -0,0 +1,108 @@
+---
+mustflow_doc: skill.web-asset-optimization
+locale: en
+canonical: true
+revision: 3
+lifecycle: mustflow-owned
+authority: procedure
+name: web-asset-optimization
+description: Apply this skill when adding, converting, resizing, replacing, or reviewing raster image assets for websites or web applications.
+metadata:
+  mustflow_schema: "1"
+  mustflow_kind: procedure
+  pack_id: mustflow.core
+  skill_id: mustflow.core.web-asset-optimization
+  command_intents:
+    - asset_optimize
+    - build
+---
+# Web Asset Optimization
+<!-- mustflow-section: purpose -->
+## Purpose
+Keep web image assets small, format-appropriate, and correctly referenced without inventing an image pipeline for the project.
+<!-- mustflow-section: use-when -->
+## Use When
+- A generated PNG, JPEG, WebP, AVIF, GIF, or other raster image is added to a website or web app.
+- An existing web image is replaced, resized, compressed, or converted.
+- A page, component, stylesheet, or metadata file changes image references.
+- A user asks to reduce image size, convert to WebP or AVIF, or prepare generated images for production use.
+<!-- mustflow-section: do-not-use-when -->
+## Do Not Use When
+- The asset is a vector source such as SVG, icon font, or design-token file.
+- The image is an archival, print, source, or evidence artifact where preserving the original bytes matters more than web delivery size.
+- The repository already has a more specific media, design-system, or framework asset procedure.
+- The task is only to generate a new image and not to install or reference it in the repository.
+<!-- mustflow-section: required-inputs -->
+## Required Inputs
+- The image file paths and their current or intended references.
+- The expected display size, transparency needs, animation needs, and quality requirements.
+- Existing framework image conventions, static asset folders, and import style.
+- `.mustflow/config/commands.toml` entries for `asset_optimize` and `build`.
+<!-- mustflow-section: preconditions -->
+## Preconditions
+- The task matches the Use When conditions and does not match the Do Not Use When exclusions.
+- Required inputs are available, or missing inputs can be reported without guessing.
+- Higher-priority instructions and `.mustflow/config/commands.toml` have been checked for the current scope.
+<!-- mustflow-section: allowed-edits -->
+## Allowed Edits
+- Keep edits within the scope described by this skill, the user request, and the matching route in `.mustflow/skills/INDEX.md`.
+- Do not broaden command permission, invent project facts, or change unrelated workflow files.
+<!-- mustflow-section: procedure -->
+## Procedure
+1. Identify every changed image asset and every page, component, style, metadata, or manifest reference that depends on it.
+2. Check the original file size, dimensions, format, transparency, and animation before changing the asset.
+3. Prefer the repository's existing image pipeline, framework image component, or configured `asset_optimize` intent when one exists.
+4. Do not add a new dependency, online service, or ad hoc conversion tool unless the user explicitly approves it or the repository already uses it.
+5. Choose the output format based on actual needs: WebP or AVIF for most photographic and generated bitmap website assets, PNG when lossless transparency or exact pixels matter, and SVG only for real vector artwork.
+6. Keep source and derived assets separate when the repository already has that convention. Otherwise, avoid adding duplicate originals unless future editing requires them.
+7. Update imports, static paths, metadata references, dimensions, and cache-sensitive filenames according to the local style.
+8. Compare before and after file sizes and note any quality, transparency, animation, browser-support, or fallback tradeoff.
+<!-- mustflow-section: postconditions -->
+## Postconditions
+- The expected output can be produced with clear evidence, executed command intents, skipped checks, and remaining risks.
+- Any missing command intent, unknown input, or authority conflict is reported instead of hidden.
+<!-- mustflow-section: verification -->
+## Verification
+Use configured oneshot command intents when available:
+- `asset_optimize`
+- `build`
+Do not infer missing image optimization commands. If `asset_optimize` is unknown, missing, manual-only, or not agent-runnable, report that status and describe the intended optimization without executing an unconfigured tool.
+<!-- mustflow-section: failure-handling -->
+## Failure Handling
+- If optimization visibly degrades the image or breaks transparency, restore or keep the better asset and report the tradeoff.
+- If image references break, fix the nearest import, path, metadata, or build configuration that owns the reference.
+- If the repository lacks an optimization command, propose the smallest project-specific command intent instead of running an external website or guessed package command.
+- If the build fails after asset changes, investigate the first asset-related failure before touching unrelated code.
+<!-- mustflow-section: output-format -->
+## Output Format
+- Images reviewed or changed
+- Format and size changes
+- References updated
+- Command intents run
+- Skipped command intents and reasons
+- Remaining image quality or browser-support risks

package/templates/default/locales/en/AGENTS.md ADDED Viewed

@@ -0,0 +1,114 @@
+---
+mustflow_doc: agents.root
+locale: en
+canonical: true
+revision: 11
+lifecycle: user-editable
+authority: binding
+---
+# AGENTS.md
+This file is the first working agreement an LLM coding agent should read in this repository.
+This repository follows the mustflow agent workflow.
+mustflow-managed details are under `.mustflow/`.
+## Read Order
+1. `AGENTS.md`
+2. `.mustflow/docs/agent-workflow.md`
+3. `.mustflow/config/mustflow.toml`
+4. `.mustflow/config/commands.toml`
+5. `.mustflow/config/preferences.toml` if present
+6. `.mustflow/skills/INDEX.md`
+7. `.mustflow/context/INDEX.md` only when the task needs project, product, domain,
+   UI, backend, data, security, or operations context
+8. The matching `.mustflow/context/<name>.md` files, only when selected by the context index
+9. The matching `.mustflow/skills/<name>/SKILL.md`
+10. `REPO_MAP.md` only when broader repository navigation is needed
+11. Relevant source, test, and documentation files
+## Core Rules
+- Do not revert existing user changes.
+- Do not infer commands from package manager files.
+- Run only command definitions whose `status` is `configured`, `lifecycle` is `oneshot`,
+  and `run_policy` is `agent_allowed`.
+- Prefer `mf run <intent>` for configured oneshot commands.
+- Run `mf run` command intents serially. Do not start another `mf run` while a configured
+  intent is still running, especially when an intent declares non-empty `writes` such as `dist/`.
+- Choose the narrowest configured verification intent that covers the risk. Prefer related or
+  fast checks over broad suites when the command contract exposes them, and report missing
+  narrower intents instead of defaulting silently to slow full-suite tests.
+- Do not directly start development servers, watchers, browser interfaces, interactive prompts,
+  or background processes.
+- Do not start autonomous loops, worker processes, persona systems, or long-running harness
+  processes unless this repository explicitly configures them.
+- Follow `[budget]`, `[approval]`, and `[isolation]` in `.mustflow/config/mustflow.toml` when a
+  task may run for a long time or affect sensitive state.
+- Use `mf doctor` or `mf doctor --json` for a read-only health check before broad changes.
+- `mf context --json` may help with machine-readable orientation, but it does not replace the rules
+  and command specification.
+- Preferences in `.mustflow/config/preferences.toml` have lower priority than direct user
+  instructions and existing project style.
+- When code, templates, schemas, CLI behavior, package metadata, user-visible docs, installation
+  output, or tests change, check `[release.versioning]` in `.mustflow/config/preferences.toml`
+  before the final report. Version files may be changed only according to those preferences:
+  apply an automatic bump when `auto_bump = true` and `require_user_confirmation = false`;
+  otherwise suggest the bump or ask before editing as configured. Do not assume the version
+  source is `package.json`; locate the repository-specific version source before suggesting or
+  editing versions.
+- Context files in `.mustflow/context/` explain project direction and domain conventions. Treat
+  them as task-specific context, not as a replacement for code, tests, commands, or user instructions.
+- If `DESIGN.md` exists, read it only for UI, visual design, layout, design-token, or accessibility
+  work. Do not create a `DESIGN.md` if one does not exist.
+- Read the matching skill document when one applies to the task.
+- Before editing, use `.mustflow/skills/INDEX.md` to decide whether one or more skills apply.
+- If a skill becomes relevant after new evidence, such as a command failure or a documentation
+  change, read the matching `SKILL.md` before continuing that part of the work.
+- Skill documents guide procedure. They do not authorize commands outside
+  `.mustflow/config/commands.toml` or override user, host, repository, or safety rules.
+- Do not modify generated files, external dependencies, or secrets files unless explicitly requested.
+- Do not treat root `config/`, `docs/`, or `skills/` directories as mustflow documents.
+## Parent and Child Rule Priority
+- The nearest `AGENTS.md` to the edited files is the more specific rule.
+- If workflow, style, tests, or command rules conflict, follow the child repository's `AGENTS.md`
+  and `.mustflow/config/commands.toml`.
+- Safety rules for secrets, privacy, destructive commands, and permitted edit paths are cumulative.
+  Follow the stricter rule.
+- When navigating to a nested repository, reread that repository's `AGENTS.md` and
+  `.mustflow/config/*.toml` before editing.
+- Do not edit outside the selected child repository unless explicitly requested.
+## Host-Specific Instruction Compatibility
+Some coding hosts may read additional host-specific instruction files or enforce their own
+approval, sandbox, checkpoint, and command execution policies.
+Treat those host policies as additive safety and execution constraints. They do not replace this
+repository's mustflow command contract. When host instructions conflict with mustflow rules:
+- Direct user instructions define the task goal unless unsafe.
+- Host safety and approval gates remain binding.
+- Repository work rules come from the nearest `AGENTS.md` and `.mustflow/config/*.toml`.
+- Project verification commands must use configured mustflow intents.
+- Stricter privacy, secret, destructive-command, and Git push rules win.
+- Generated state, summaries, and caches never override current files or current user instructions.
+When the effective rule is unclear, stop and report the conflict instead of guessing.
+## Instruction Refresh Checkpoints
+- In long sessions, reread mustflow instructions before the first edit, before command execution
+  when the current command intent does not already have a fresh command refresh, after context
+  compaction, after changing `AGENTS.md` or `.mustflow/**`, after switching project roots, and
+  before writing the final report.
+- Use the `[refresh]` policy in `.mustflow/config/mustflow.toml` to decide whether a light, a
+  command, a skill, or a full refresh is needed.
+- Do not store conversation turn counts or session activity in project files. Session refresh state
+  belongs in local cache or the host application.
+Detailed workflow, command policy, failure handling, and security rules are in
+`.mustflow/docs/agent-workflow.md`.

package/templates/default/locales/es/.mustflow/context/INDEX.md ADDED Viewed

@@ -0,0 +1,39 @@
+---
+mustflow_doc: context.index
+kind: mustflow-context
+locale: es
+canonical: false
+revision: 1
+lifecycle: mustflow-owned
+name: context-index
+authority: router
+stability: medium
+review_status: needs_human_review
+---
+# Índice de Contexto
+Consulta este archivo para identificar qué archivos de contexto del proyecto son relevantes para la tarea actual.
+Evita leer todos los archivos de contexto por defecto para minimizar el ruido.
+## Contexto Disponible
+| Contexto | Usar cuando | Ruta |
+| --- | --- | --- |
+| project | La tarea puede afectar la dirección del proyecto, el alcance, el comportamiento público, los no-objetivos o convenciones de todo el repositorio. | `.mustflow/context/PROJECT.md` |
+## Referencias Externas Opcionales
+| Ancla | Usar cuando | Ruta |
+| --- | --- | --- |
+| human overview | Se requiere una visión pública del proyecto o una guía de instalación. Trátalo como contexto general y no como política obligatoria. | `README.md` |
+| roadmap | Se necesita contexto sobre planificación, prioridades, hitos o no-objetivos del proyecto. Trátalo como contexto de planificación, no como política mustflow instalada. | `ROADMAP.md` |
+| visual design | La tarea implica cambios en la interfaz, identidad visual, tokens de diseño, maquetación o accesibilidad. | `DESIGN.md` |
+## Reglas de Lectura
+- Consulta solo los archivos de contexto relevantes para la tarea actual.
+- Trata los archivos de contexto como guía, salvo que se indique explícitamente que están respaldados por una fuente de mayor autoridad.
+- Si el contexto entra en conflicto con código, pruebas, especificaciones de comandos o instrucciones explícitas del usuario, reporta el conflicto y prioriza la fuente de mayor autoridad.
+- No supongas ni inventes objetivos faltantes del proyecto, no-objetivos, tokens de diseño, contratos de API o reglas de datos.
+- No dupliques tokens de diseño de `DESIGN.md` dentro de `.mustflow/context/`.

package/templates/default/locales/es/.mustflow/context/PROJECT.md ADDED Viewed

@@ -0,0 +1,63 @@
+---
+mustflow_doc: context.project
+kind: mustflow-context
+locale: es
+canonical: false
+revision: 1
+lifecycle: user-editable
+name: project
+authority: contextual
+stability: medium
+review_status: needs_human_review
+source_refs:
+  - AGENTS.md
+  - .mustflow/config/mustflow.toml
+  - .mustflow/config/commands.toml
+---
+# Contexto del Proyecto
+Este archivo documenta el contexto específico del proyecto para agentes de codificación.
+Si algún campo es desconocido, déjalo sin completar; no supongas ni inventes detalles.
+## Límites de Autoridad
+- Este archivo puede registrar contexto respaldado, incógnitas y conflictos.
+- No debe otorgar permisos para ejecutar comandos, definir prohibiciones de edición de archivos, reemplazar `AGENTS.md` o `.mustflow/config/*.toml`, ni prometer funciones que no estén respaldadas por las fuentes actuales.
+- Traslada las reglas operativas duraderas a `AGENTS.md`, `.mustflow/docs/agent-workflow.md` o al archivo de configuración correspondiente en lugar de guardarlas aquí.
+## Objetivo Actual
+Sin definir. Sustituye este texto por el objetivo actual del proyecto cuando la persona responsable lo proporcione.
+## No-Objetivos
+Sin definir. Enumera áreas u objetivos que el agente no debe perseguir en tareas no relacionadas.
+## Promesas Principales
+- Sigue `AGENTS.md` para las reglas operativas obligatorias.
+- Considera `.mustflow/config/commands.toml` como la fuente de verdad para comandos.
+- Considera `.mustflow/config/mustflow.toml` como la fuente de verdad para límites de flujo de trabajo y documentos.
+- Usa `REPO_MAP.md` como mapa de navegación superficial cuando se requiera una vista más amplia del repositorio.
+## Términos del Dominio
+Sin definir. Agrega solo términos que afecten decisiones de implementación.
+## Áreas de Cuidado Especial
+Sin definir. Lista rutas, API públicas, archivos generados, migraciones, secretos o superficies de compatibilidad que requieran atención especial.
+## Lectura Recomendada
+- `AGENTS.md`
+- `.mustflow/docs/agent-workflow.md`
+- `.mustflow/config/mustflow.toml`
+- `.mustflow/config/commands.toml`
+- `.mustflow/skills/INDEX.md`
+## Verificación de Obsolescencia
+- Si este archivo entra en conflicto con el código actual, pruebas, contratos de comandos o instrucciones del usuario, trátalo como desactualizado y reporta el conflicto.
+- Actualiza este archivo solo cuando cambie realmente la dirección del proyecto, los no-objetivos o las promesas de alcance del repositorio.