@massa-ai/cursor-plugin 1.22.0 → 1.23.0

package/.cursor-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "massa-ai",
-  "version": "1.22.0",
+  "version": "1.23.0",
   "description": "massa-ai — semantic code search, memory, and context compression for Cursor"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@massa-ai/cursor-plugin",
-  "version": "1.22.0",
+  "version": "1.23.0",
   "description": "massa-ai plugin for Cursor — semantic code search, memory, and context compression",
   "files": [
     "agents",

package/skills/massa-ai/SKILL.md

@@ -60,6 +60,14 @@ Before reading any massa-ai file:
 - Persist only durable, useful knowledge. Do not fabricate memories to satisfy
   process. Use `memory_update` to correct stale memories and `memory_delete`
   to remove obsolete ones.
+- Expand every word abbreviation on first use in user-facing output — e.g.
+  "PR (Pull Request)", "AC (Acceptance Criteria)", "KMP (Kotlin Multiplatform)"
+  — including workflow-specific shorthands and finding-ID families.
+- Use one uniform vocabulary for separating batches of work in every workflow:
+  a **Task** is the atomic unit; a **Phase** is an ordered group of Tasks.
+  Report a phase's size as `1 Phase = X Tasks` and a plan's total as
+  `Y Phases = Z Tasks`. Do not substitute synonyms such as batch, wave, stage,
+  or chunk for these units in agent prose.
 - Emit concise user-facing status updates at meaningful workflow boundaries
   when the Conversation Feedback Policy is active.
 - Verify, don't assume: every factual claim that drives a decision is
@@ -275,6 +283,7 @@ Load only when a selected workflow asks for them:
 - `references/debug-diagnosis-loop.md`
 - `references/mobile-context.md`
 - `references/mobile-diagnosis.md`
+- `references/figma-pre-analysis.md`
 - `references/mobile-figma-matcher/`
 - `references/lessons.md`
 - `references/naming-standards.md`

package/skills/massa-ai/references/figma-pre-analysis.md

@@ -0,0 +1,69 @@
+# Figma Pre-Analysis And Sequential Retrieval
+
+Load this reference whenever a workflow receives one or more Figma links, node
+IDs, or a readable desktop selection as a design source — the Figma audit/fix
+family (`mobile-figma-audit`, `mobile-figma-fix`), `design`, and the
+design-source gates of implementation workflows (`feature`, `spec-driven`).
+This reference owns the orchestration protocol only; Figma Evidence Packet
+field contracts stay in `references/mobile-figma-matcher/core.md`.
+
+The protocol is the single normative copy. Workflows point here; they do not
+restate it.
+
+## Why Two Stages
+
+Full Figma extraction on unscoped links overloads one context with mixed
+screens, buries feature boundaries, and makes evidence non-attributable. A
+cheap pre-analysis pass first maps what the links contain, so each retrieval
+pass reads one coherent slice.
+
+## Stage 1 — Pre-Analysis (always first, exactly one subagent)
+
+Dispatch one read-only subagent (investigator-class; Figma MCP — Model Context
+Protocol — access, no repository mutation) over the user-provided Figma links.
+Its job is understanding, **not** extraction:
+
+- Summarize composition: pages, screens, frames, component sets, shared tokens.
+- Summarize product context: what the screens are for, the features they serve,
+  and the user flows connecting them.
+- It does not build Figma Evidence Packet fields, does not resolve variables or
+  exact geometry, and does not compare against source code.
+
+Its output is a compact packet:
+
+1. **Context summary** — screens/features/flows in prose, sized for the main
+   agent's context budget.
+2. **Partition proposal** — how many retrieval subagents should read which
+   links/nodes/screen groups, partitioned by:
+   - **Size:** each slice must fit one subagent's context comfortably.
+   - **Coupling:** screens sharing tokens, components, or a design system
+     section stay in one slice.
+   - **Feature flow:** one user flow per slice when possible, so evidence
+     stays attributable to a feature.
+   A single small screen legitimately yields a one-slice proposal.
+
+The main agent reviews the proposal, adjusts slice boundaries if project
+knowledge contradicts them, and records the final partition before Stage 2.
+
+## Stage 2 — Sequential Retrieval (N subagents, one at a time)
+
+The main agent orchestrates the retrieval subagents **strictly sequentially —
+never in parallel**. For each slice, in the recorded order:
+
+1. Dispatch one read-only retrieval subagent scoped to that slice's
+   links/nodes, carrying the Stage 1 context summary and the slice's purpose.
+2. Wait for completion; fold its output into the workflow's Figma Evidence
+   Packet (or Screenshot Context Packet rows) before dispatching the next.
+3. Let each completed slice inform the next dispatch prompt — resolved shared
+   tokens, discovered variants, and naming conventions carry forward.
+
+Sequential dispatch is a hard rule, not a tuning choice: it respects Figma MCP
+session/rate limits, and it is what lets slice N+1 reuse what slice N learned.
+Retrieval subagents never spawn further subagents.
+
+## Fallback
+
+If subagent spawning is unavailable (forbidden, plugin missing, unknown agent
+type), run both stages inline in the main agent in the same order — pre-analysis
+summary first, then per-slice retrieval — and record the skipped delegation
+with its reason. Do not skip Stage 1 because delegation is unavailable.

package/skills/massa-ai/references/implementation-delivery.md

@@ -90,6 +90,18 @@ title: `[SA-100] Phase 1: search facade split`. The per-task commit prefixes on
 the branch are owned by `workflows/commit.md`; this stage owns only the PR-level
 phase prefix. Non-phased work keeps the existing PR title behavior unchanged.
 
+### Stages 3–7 — the PR description stays current
+
+The PR description is a living artifact, not a creation-time snapshot. After
+**every push requested while the PR exists** — repair iterations, follow-up
+tasks, review-requested changes — update the PR description with
+`gh pr edit <number> --body <b>` so it reflects the branch's current commit
+set, scope, and evidence **before** returning to Watch. The description must be
+current before the merge decision is requested; a merge may never be proposed
+over a description that describes an older state of the branch. When generated
+or bundled files are regenerated alongside source edits, the description names
+that blast radius explicitly so reviewers do not undercount the diff.
+
 ### Stage 7 — merge is never automatic
 
 Do not run `gh pr merge` without explicit user approval given in the current
@@ -126,6 +138,8 @@ silently did not run is worse than one that loudly failed.
 - Merging because CI passed. CI passing is the precondition for asking, not the
   approval itself.
 - Reporting "done" while the branch is unpushed.
+- Proposing or performing a merge while the PR description still describes an
+  older commit set — update it after each requested push, before merging.
 
 ## Completion Evidence
 

package/skills/massa-ai/references/mobile-context.md

@@ -76,6 +76,25 @@ For design, mobile Figma audit, or mobile Figma fix, load `references/mobile-fig
 
 Never rely on model self-evaluation. If device access, signing, credentials, provisioning, or hardware is unavailable, state the missing dependency and use the strongest available artifact or static proof.
 
+## Compose Screen Previews
+
+In every implementation workflow, when the target surface is Android Jetpack
+Compose or KMP (Kotlin Multiplatform) Compose Multiplatform, every created or
+updated screen-level composable ships with `@Preview` composables in the same
+change:
+
+- Cover the representative states the change touches (default content, loading,
+  error, and empty where they exist), using preview parameter providers when
+  the project already uses them.
+- Follow the project's existing preview conventions (naming, placement,
+  multipreview annotations, theme wrappers) rather than inventing new ones.
+- Previews are validation assets: never delete or weaken an existing preview to
+  make a change compile, and treat a screen edit that leaves its previews stale
+  as incomplete work.
+- On KMP, place previews in the source set where the project renders them
+  (commonMain multiplatform previews or per-platform preview hosts), matching
+  established project layout.
+
 ## Tests Lens
 
 When auditing or executing test work, check mobile-specific coverage for:

package/skills/massa-ai/references/mobile-diagnosis.md

@@ -4,7 +4,7 @@ Use this reference when `workflows/debug.md` handles broken behavior involving K
 
 This extends `references/debug-diagnosis-loop.md`. Do not use it instead of the general debug loop.
 
-For non-debug mobile feature, refactor, tests, or security work, keep the intent-specific workflow and load `references/mobile-context.md` instead. Use `references/mobile-context.md` from Debug only when shared mobile vocabulary or non-bug parity/security/test framing is needed.
+For non-debug mobile feature, refactor, tests, or security work, keep the intent-specific workflow and load `references/mobile-context.md` instead. Use `references/mobile-context.md` from Debug only when shared mobile vocabulary or non-bug parity/security/test framing is needed — and always when a fix creates or updates a Compose screen, because its Compose Screen Previews rule (`@Preview` coverage) applies to debug-path edits too.
 
 ## Mobile Intake
 

package/skills/massa-ai/workflows/design.md

@@ -9,7 +9,7 @@ Before the first repository mutation, load `references/implementation-delivery.m
 Do not use this workflow for Flutter, React Native, web UI, generic Figma exploration, variable-only queries, or MCP troubleshooting.
 
 1. Resolve/reuse `workflowSessionId`: `design-[entity]`.
-2. Load `references/mobile-figma-matcher/repository-detection.md`, `references/mobile-figma-matcher/core.md`, `references/mobile-context.md`, `references/codebase-investigation.md`, and `references/verification-ladder.md`. Load `references/context-firewall.md` before large design/runtime artifacts and `references/synapse-policy.md` when repeated massa-ai searches are expected.
+2. Load `references/mobile-figma-matcher/repository-detection.md`, `references/mobile-figma-matcher/core.md`, `references/mobile-context.md`, `references/codebase-investigation.md`, and `references/verification-ladder.md`. When Figma links or node IDs are provided, load `references/figma-pre-analysis.md` and run its two-stage sequential retrieval protocol before building the Figma Evidence Packet. Load `references/context-firewall.md` before large design/runtime artifacts and `references/synapse-policy.md` when repeated massa-ai searches are expected.
 3. `recall` -> load current component conventions, design-system rules, approved platform/accessibility deviations, prior Figma mappings, asset pipelines, and reusable render recipes. Memory is context, not proof.
 4. Require a concrete feature/module target plus at least one design source: readable Figma node/selection or supplied screenshots. Resolve required visual and interactive states plus a requirements source for behavior not represented in the design source. Ask only when target ownership, runtime platforms, platform-frame mappings, or screenshot authority remain ambiguous after source inspection.
 5. Build the immutable Target Surface Packet before loading stack guidance. Classify each selected surface and load only its contracts:

package/skills/massa-ai/workflows/feature.md

@@ -22,7 +22,7 @@ Before the first repository mutation, load `references/implementation-delivery.m
    - Ask for one or more Figma links, node IDs, a readable desktop selection, supplied screenshots, or explicit `none`.
    - Do not ask for clear backend, CLI, docs, infrastructure, or non-UI work.
    - Treat `none` as a first-class answer. Record `Figma Source: none by user choice` and do not re-ask unless the mobile UI scope changes.
-   - If Figma sources or screenshots are supplied for supported Android, iOS, or KMP Compose Multiplatform UI implementation/update work, keep this workflow as the parent and invoke `workflows/design.md` for the affected UI slice.
+   - If Figma sources or screenshots are supplied for supported Android, iOS, or KMP Compose Multiplatform UI implementation/update work, keep this workflow as the parent and invoke `workflows/design.md` for the affected UI slice. When Figma links or node IDs are supplied, load `references/figma-pre-analysis.md` and run its two-stage sequential retrieval protocol before consuming the design evidence.
    - Preserve mobile Figma routing by intent: compare/audit wording uses `workflows/mobile-figma/mobile-figma-audit.md`; saved `MFM-*` findings use `workflows/mobile-figma/mobile-figma-fix.md`.
    - If Figma sources are supplied for unsupported targets such as Flutter, React Native, web, desktop, or generic design exploration, do not run mobile Figma. Record that the Figma source is outside mobile Figma scope and continue the normal feature workflow.
    - Figma defines visible design intent and represented variants only. Screenshots are context-only unless paired with structured Figma evidence; do not claim exact Figma parity, tokens, variables, or dimensions from screenshots alone. Product behavior not represented by the design source still requires a separate requirements source.

package/skills/massa-ai/workflows/mobile-figma/mobile-figma-audit.md

@@ -10,6 +10,7 @@ Do not edit code. Route direct design implementation to `design`. Do not use thi
 2. Load shared references:
    - `references/mobile-figma-matcher/repository-detection.md` before platform guidance.
    - `references/mobile-figma-matcher/core.md` for Figma, assets, mapping, comparison, Maestro, and claim contracts.
+   - `references/figma-pre-analysis.md` when Figma links or node IDs are provided — run its two-stage sequential retrieval protocol before Figma extraction.
    - `references/mobile-context.md` for mobile boundaries, parity, and verification context.
    - `references/audit-scope.md` for target resolution and freshness.
    - `references/audit-report-io.md` before producing the report.

package/skills/massa-ai/workflows/mobile-figma/mobile-figma-fix.md

@@ -12,6 +12,7 @@ Do not execute from chat summaries, screenshots alone, remembered findings, or a
 2. Load shared references:
    - `references/mobile-figma-matcher/repository-detection.md` before platform guidance.
    - `references/mobile-figma-matcher/core.md` for Figma, assets, mapping, Maestro, matrix, and claim contracts.
+   - `references/figma-pre-analysis.md` when the findings span multiple Figma links or nodes — run its two-stage sequential retrieval protocol for the re-read.
    - `references/lessons.md` to load confirmed project lessons
    - `references/mobile-context.md` for mobile boundary and verification guidance.
    - `references/audit-report-io.md` before any source or validation-asset edit.

package/skills/massa-ai/workflows/spec-driven.md

@@ -40,7 +40,7 @@ Complexity determines depth, not a fixed pipeline. Assess scope first, apply onl
 | Large | >10 tasks OR multi-component feature | Full spec + requirement IDs | Architecture + components | Full breakdown + deps | Implement + verify per task |
 | Complex | Ambiguity or new domain (unfamiliar vocabulary, no prior pattern) | Full spec + discuss gray areas | Research + architecture | Breakdown + phase plan | Implement + interactive UAT |
 
-A "phase" is a group of tasks sharing a dependency boundary or a checkpoint commit — it is distinct from a single task or atomic step. The sub-agent offer fires when a formal `tasks.md` has more than 3 tasks — packing itself still uses ~7-task batches; a 4–8-task feature is offered as a single batch worker.
+A "Phase" is an ordered group of Tasks sharing a dependency boundary or a checkpoint commit — it is distinct from a single Task or atomic step. Report sizing in the uniform vocabulary: `1 Phase = X Tasks`; the whole plan is `Y Phases = Z Tasks`. The sub-agent offer fires when a formal `tasks.md` has more than 3 Tasks — packing itself still uses ~7-Task Phase groups; a 4–8-Task feature is offered as a single Phase-group worker.
 
 - Specify and Execute are always required.
 - Design is skipped when straightforward (no architectural decisions, no new patterns).
@@ -85,7 +85,7 @@ Quick artifacts live under `.specs/quick/NNN-slug/` with a `TASK.md` (one-line i
 3. Run `Specify` with `references/spec-driven/specify.md`.
    - Capture stable requirement IDs, testable acceptance criteria, edge cases, and explicit out-of-scope items.
    - Run `references/spec-driven/discuss.md` inside Specify when gray areas, implicit requirements, persistence/state, external calls, auth, payments, concurrency, or state transitions affect behavior.
-   - For Android, iOS, or KMP Compose Multiplatform UI work, load `references/mobile-context.md` and run the optional design-source gate: ask for one or more Figma links, node IDs, a readable desktop selection, supplied screenshots, or explicit `none`; record `Figma Source: none by user choice` when declined. Screenshots are context-only unless paired with structured Figma evidence. For unsupported targets, record the source as outside mobile Figma scope and do not run mobile Figma.
+   - For Android, iOS, or KMP Compose Multiplatform UI work, load `references/mobile-context.md` and run the optional design-source gate: ask for one or more Figma links, node IDs, a readable desktop selection, supplied screenshots, or explicit `none`; record `Figma Source: none by user choice` when declined. When Figma links or node IDs are supplied, load `references/figma-pre-analysis.md` and run its two-stage sequential retrieval protocol before consuming the design evidence. Screenshots are context-only unless paired with structured Figma evidence. For unsupported targets, record the source as outside mobile Figma scope and do not run mobile Figma.
    - Apply the Requirement Closure Gate: every open requirement question is resolved with the user or recorded as an accepted assumption before execution begins.
 4. Decide whether `Design` is required. If yes, run `references/spec-driven/design.md`; if no, record why the skip is valid. When Design is skipped and a design concern appears later, stop and create `design.md` before continuing.
 5. Decide whether `Tasks` is required. If yes, run `references/spec-driven/tasks.md`; if no, list the inline atomic execution steps before editing. If the inline list reveals more than 5 steps or complex dependencies, stop and create `tasks.md` — the Tasks phase was wrongly skipped (safety valve).
@@ -94,7 +94,7 @@ Quick artifacts live under `.specs/quick/NNN-slug/` with a `TASK.md` (one-line i
    - Run repo-rules discovery from `references/repo-rules-discovery.md` before the first repository mutation: record the harness sources loaded (or `repo-rules: none present`), and implement so every new or changed file conforms to the target repo's module layout, unit-test location, and testing-area conventions. A repo rule wins over a skill default for placement and gate commands; record any deviation with an explicit reason. Never fabricate rules or create `.claude/`/`.cursor/` directories the repo lacks.
    - Use the Test Coverage Matrix and Gate Check Commands from `tasks.md`, or state their inline equivalents when Tasks was skipped.
    - Ask the MCP and skill question in Tasks or inline Execute when tool choice can change correctness or verification.
-   - If a formal `tasks.md` has more than 3 tasks, present the sub-agent offer from `references/spec-driven/sub-agents.md` before starting Execute — even when packing yields a single batch (a 4–8-task feature is offered as one batch worker). Offer-then-confirm — never auto-spawn; the user must accept before any sub-agent is dispatched. One worker per batch (~7 tasks, whole phases): each batch worker executes all its tasks in order (implement → gate → atomic commit), then reports a compact summary (tasks done, commit hashes, test counts, deviations). Workers never spawn further sub-agents.
+   - If a formal `tasks.md` has more than 3 Tasks, present the sub-agent offer from `references/spec-driven/sub-agents.md` before starting Execute — even when packing yields a single Phase group (a 4–8-Task feature is offered as one Phase-group worker). Offer-then-confirm — never auto-spawn; the user must accept before any sub-agent is dispatched. One worker per Phase group (~7 Tasks, whole Phases): each worker executes all its Tasks in order (implement → gate → atomic commit), then reports a compact summary (Tasks done, commit hashes, test counts, deviations). Workers never spawn further sub-agents.
    - Implement one atomic step or approved task at a time.
    - For long-running task sequences, create a checkpoint via `create_checkpoint` at task boundaries with `taskId`, `description`, `progressPercent`, `currentStep`, `nextAction`, `fileChanges`, and `checkpointType: "manual"` so progress is resumable after interruption.
    - If resuming after interruption, call `list_checkpoints` with the `taskId` and `restore_checkpoint` to recover task state before continuing. If `create_checkpoint` is unavailable (e.g. `task_checkpoints` table missing), continue with `.specs/` artifact state as the fallback.