@smartsoft001-mobilems/claude-plugins 2.73.0 → 2.75.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smartsoft001-mobilems/claude-plugins",
-  "version": "2.73.0",
+  "version": "2.75.0",
   "publishConfig": {
     "access": "public"
   },

package/plugins/flow/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "flow",
   "description": "Development flow skills for Linear-driven development workflow",
-  "version": "2.73.0"
+  "version": "2.75.0"
 }

package/plugins/flow/agents/angular-component-scaffolder.md

@@ -2,7 +2,7 @@
 name: angular-component-scaffolder
 description: Create Angular standalone components with signals and modern patterns. Use when scaffolding new components following Angular 20+ best practices.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow/agents/angular-directive-builder.md

@@ -2,7 +2,7 @@
 name: angular-directive-builder
 description: Create Angular standalone directives. Use when building attribute or structural directives.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow/agents/angular-guard-builder.md

@@ -2,7 +2,7 @@
 name: angular-guard-builder
 description: Create Angular functional guards. Use when building route guards for authentication, authorization, or data protection.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow/agents/angular-pipe-builder.md

@@ -2,7 +2,7 @@
 name: angular-pipe-builder
 description: Create Angular standalone pipes. Use when building transform pipes for templates.
 tools: Read, Write, Glob, Grep
-model: opus
+model: haiku
 color: "#DD0031"
 ---
 

package/plugins/flow/agents/angular-resolver-builder.md

@@ -2,7 +2,7 @@
 name: angular-resolver-builder
 description: Create Angular functional resolvers. Use when building route resolvers for data preloading.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow/agents/angular-service-builder.md

@@ -2,7 +2,7 @@
 name: angular-service-builder
 description: Create Angular injectable services with signals and modern patterns. Use when building services for data management and business logic.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow/agents/angular-testbed-configurator.md

@@ -2,7 +2,7 @@
 name: angular-testbed-configurator
 description: Create and configure Angular TestBed setups. Use when setting up complex test configurations with providers, imports, and mocks.
 tools: Read, Write, Edit, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow/agents/shared-build-verifier.md

@@ -2,7 +2,7 @@
 name: shared-build-verifier
 description: Verify that builds complete successfully. Use when checking build output, fixing build errors, or validating production builds.
 tools: Bash, Read, Grep, Glob
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-config-updater.md

@@ -2,7 +2,7 @@
 name: shared-config-updater
 description: Update configuration files safely. Use when modifying project.json, tsconfig, nx.json, package.json, or ESLint configuration files.
 tools: Read, Edit, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-coverage-enforcer.md

@@ -2,7 +2,7 @@
 name: shared-coverage-enforcer
 description: Enforce test coverage requirements. Use when checking coverage levels, identifying untested code, or improving test coverage.
 tools: Bash, Read, Grep, Glob
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-error-handler.md

@@ -2,7 +2,7 @@
 name: shared-error-handler
 description: Standardize error handling patterns across the application. Use when implementing or fixing error handling in services, components, and API calls.
 tools: Read, Edit, Glob, Grep
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-file-creator.md

@@ -2,7 +2,7 @@
 name: shared-file-creator
 description: Create new files with proper templates and boilerplate. Use when creating components, services, modules, or any new source files.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-impl-reporter.md

@@ -2,7 +2,7 @@
 name: shared-impl-reporter
 description: Generate implementation reports for Linear comments. Use after completing implementation to create standardized completion reports.
 tools: Read, Glob, Grep
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-linear-subtask-iterator.md

@@ -2,7 +2,7 @@
 name: shared-linear-subtask-iterator
 description: Manage Linear task and subtask iteration. Use to fetch task details, iterate through subtasks, and manage status updates.
 tools: Read, Glob, Grep
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-performance-validator.md

@@ -2,7 +2,7 @@
 name: shared-performance-validator
 description: Validate performance metrics and bundle sizes. Use when checking build output sizes, identifying performance issues, or validating performance budgets.
 tools: Bash, Read, Glob, Grep
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-project-standardizer.md

@@ -2,7 +2,7 @@
 name: shared-project-standardizer
 description: Apply project standards and conventions. Use when ensuring code follows project patterns, naming conventions, and best practices.
 tools: Read, Edit, Glob, Grep
-model: opus
+model: haiku
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-style-enforcer.md

@@ -2,7 +2,7 @@
 name: shared-style-enforcer
 description: Enforce code style with ESLint and Prettier. Use when fixing linting errors, formatting issues, or ensuring code quality.
 tools: Read, Edit, Bash, Glob, Grep
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-ui-classifier.md

@@ -2,7 +2,7 @@
 name: shared-ui-classifier
 description: Classify if a task involves UI changes. Use before implementation to determine if screenshots are required.
 tools: Read, Glob, Grep
-model: opus
+model: haiku
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/shared-verification-orchestrator.md

@@ -2,7 +2,7 @@
 name: shared-verification-orchestrator
 description: Orchestrate the full verification pipeline. Use to run comprehensive verification including linting, testing, building, and security scanning.
 tools: Bash, Read, Glob, Grep
-model: opus
+model: sonnet
 color: "#2563EB"
 ---
 

package/plugins/flow/agents/ui-a11y-validator.md

@@ -3,7 +3,7 @@ name: ui-a11y-validator
 description: Validate website accessibility (WCAG compliance). Use when checking accessibility issues, auditing pages, or fixing a11y problems.
 tools: Read, Grep, Glob, Bash
 skills: a11y-audit
-model: opus
+model: sonnet
 color: "#7C3AED"
 ---
 

package/plugins/flow/agents/ui-screenshot-reporter.md

@@ -3,7 +3,7 @@ name: ui-screenshot-reporter
 description: Capture before/after screenshots for UI changes, create visual comparison reports, and post them as Linear comments. Run in parallel with implementation work.
 tools: Read, Glob, Grep, mcp__linear-server__create_comment, mcp__linear-server__get_issue
 skills: browser-capture, maia-files-upload, maia-files-delete
-model: opus
+model: sonnet
 color: "#7C3AED"
 ---
 

package/plugins/flow/agents/ui-web-designer.md

@@ -3,7 +3,7 @@ name: ui-web-designer
 description: Style components and views with Tailwind CSS according to project standards. Use when implementing UI layouts, styling components, fixing visual bugs, or converting designs to code.
 tools: Read, Edit, Write, Glob, Grep
 skills: browser-capture
-model: opus
+model: sonnet
 color: "#7C3AED"
 ---
 

package/plugins/flow/skills/commit/SKILL.md

@@ -47,13 +47,24 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 **MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
 
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
 **At skill start**: Create tasks for each checklist step using `TaskCreate`:
 
 ```
 TaskCreate({
-  subject: "Fetch Linear task",
+  subject: "MM-123 Fetch Linear task",
   description: "Get title, description, labels/type from MCP Linear server",
-  activeForm: "Fetching Linear task"
+  activeForm: "MM-123 Fetching Linear task"
+})
+TaskCreate({
+  subject: "MM-123 Analyze staged changes",
+  description: "Run git diff --cached to understand scope",
+  activeForm: "MM-123 Analyzing staged changes"
 })
 ```
 

package/plugins/flow/skills/impl/SKILL.md

@@ -62,23 +62,39 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 **MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
 
-**At skill start**: Create tasks for the initial setup and each subtask processing round using `TaskCreate`:
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID (parent or subtask):
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for the initial setup using `TaskCreate`:
 
 ```
 TaskCreate({
-  subject: "Fetch task and subtasks",
+  subject: "MM-123 Fetch task and subtasks",
   description: "Delegate to shared-linear-subtask-iterator agent",
-  activeForm: "Fetching task and subtasks"
+  activeForm: "MM-123 Fetching task and subtasks"
 })
 ```
 
-**Per subtask**: Create a parent task for the subtask, then child tasks for each step:
+**Per subtask**: Create a parent task for the subtask, then child tasks for each step — all prefixed with the subtask ID:
 
 ```
 TaskCreate({
-  subject: "Implement subtask MOB-123",
+  subject: "MM-123-1 Implement subtask",
   description: "Full implementation cycle: classify → orchestrate → implement → verify",
-  activeForm: "Implementing subtask MOB-123"
+  activeForm: "MM-123-1 Implementing subtask"
+})
+TaskCreate({
+  subject: "MM-123-1 UI change classification",
+  description: "Delegate to shared-ui-classifier agent",
+  activeForm: "MM-123-1 Classifying UI changes"
+})
+TaskCreate({
+  subject: "MM-123-1 Verify implementation",
+  description: "Run tests, lint, build check",
+  activeForm: "MM-123-1 Verifying implementation"
 })
 ```
 

package/plugins/flow/skills/plan/SKILL.md

@@ -45,13 +45,24 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 **MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
 
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
 **At skill start**: Create tasks for each checklist step using `TaskCreate`:
 
 ```
 TaskCreate({
-  subject: "Fetch Linear task",
+  subject: "MM-123 Fetch Linear task",
   description: "Get title, description, labels, priority, estimate from MCP Linear server",
-  activeForm: "Fetching Linear task"
+  activeForm: "MM-123 Fetching Linear task"
+})
+TaskCreate({
+  subject: "MM-123 Analyze codebase",
+  description: "Explore affected files, patterns, dependencies, and test coverage",
+  activeForm: "MM-123 Analyzing codebase"
 })
 ```
 

package/plugins/flow/skills/push/SKILL.md

@@ -66,13 +66,24 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 **MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
 
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
 **At skill start**: Create tasks for each checklist step using `TaskCreate`:
 
 ```
 TaskCreate({
-  subject: "Check git status",
+  subject: "MM-123 Check git status",
   description: "Verify branch, commits ahead, warn about uncommitted changes",
-  activeForm: "Checking git status"
+  activeForm: "MM-123 Checking git status"
+})
+TaskCreate({
+  subject: "MM-123 Push to remote",
+  description: "Execute git push and handle errors",
+  activeForm: "MM-123 Pushing to remote"
 })
 ```
 

package/plugins/flow-legacy/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "flow-legacy",
   "description": "Development flow skills for legacy Angular 14 projects with Linear-driven workflow",
-  "version": "2.73.0"
+  "version": "2.75.0"
 }

package/plugins/flow-legacy/agents/angular-component-scaffolder.md

@@ -2,7 +2,7 @@
 name: angular-component-scaffolder
 description: Create Angular 14 components with NgModules and legacy patterns. Use when scaffolding new components following Angular 14 best practices (*ngIf/*ngFor, constructor DI, @Input/@Output).
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow-legacy/agents/angular-directive-builder.md

@@ -2,7 +2,7 @@
 name: angular-directive-builder
 description: Create Angular 14 directives with constructor DI. Use when building attribute or structural directives for legacy projects.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow-legacy/agents/angular-guard-builder.md

@@ -2,7 +2,7 @@
 name: angular-guard-builder
 description: Create Angular 14 route guards with constructor DI. Use when building CanActivate, CanDeactivate, or other guards for legacy projects.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow-legacy/agents/angular-pipe-builder.md

@@ -2,7 +2,7 @@
 name: angular-pipe-builder
 description: Create Angular 14 pipes with constructor DI. Use when building transform pipes for templates in legacy projects.
 tools: Read, Write, Glob, Grep
-model: opus
+model: haiku
 color: "#DD0031"
 ---
 

package/plugins/flow-legacy/agents/angular-resolver-builder.md

@@ -2,7 +2,7 @@
 name: angular-resolver-builder
 description: Create Angular 14 route resolvers with constructor DI. Use when pre-fetching data before route activation in legacy projects.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow-legacy/agents/angular-service-builder.md

@@ -2,7 +2,7 @@
 name: angular-service-builder
 description: Create Angular 14 injectable services with BehaviorSubject and constructor DI. Use when building services for data management and business logic in legacy projects.
 tools: Read, Write, Glob, Grep
-model: opus
+model: sonnet
 color: "#DD0031"
 ---
 

package/plugins/flow-legacy/agents/shared-linear-subtask-iterator.md

@@ -2,7 +2,7 @@
 name: shared-linear-subtask-iterator
 description: Iterate through Linear subtasks, managing status transitions and providing implementation context.
 tools: Read, Glob, Grep
-model: opus
+model: sonnet
 color: "#5E6AD2"
 ---
 

package/plugins/flow-legacy/agents/shared-test-runner.md

@@ -2,7 +2,7 @@
 name: shared-test-runner
 description: Run tests for specified projects and report results.
 tools: Bash, Read, Glob
-model: sonnet
+model: haiku
 color: "#22C55E"
 ---
 

package/plugins/flow-legacy/skills/commit/SKILL.md

@@ -47,13 +47,24 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 **MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
 
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
 **At skill start**: Create tasks for each checklist step using `TaskCreate`:
 
 ```
 TaskCreate({
-  subject: "Fetch Linear task",
+  subject: "MM-123 Fetch Linear task",
   description: "Get title, description, labels/type from MCP Linear server",
-  activeForm: "Fetching Linear task"
+  activeForm: "MM-123 Fetching Linear task"
+})
+TaskCreate({
+  subject: "MM-123 Analyze staged changes",
+  description: "Run git diff --cached to understand scope",
+  activeForm: "MM-123 Analyzing staged changes"
 })
 ```
 

package/plugins/flow-legacy/skills/impl/SKILL.md

@@ -62,23 +62,39 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 **MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
 
-**At skill start**: Create tasks for the initial setup and each subtask processing round using `TaskCreate`:
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID (parent or subtask):
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for the initial setup using `TaskCreate`:
 
 ```
 TaskCreate({
-  subject: "Fetch task and subtasks",
+  subject: "MM-123 Fetch task and subtasks",
   description: "Delegate to shared-linear-subtask-iterator agent",
-  activeForm: "Fetching task and subtasks"
+  activeForm: "MM-123 Fetching task and subtasks"
 })
 ```
 
-**Per subtask**: Create a parent task for the subtask, then child tasks for each step:
+**Per subtask**: Create a parent task for the subtask, then child tasks for each step — all prefixed with the subtask ID:
 
 ```
 TaskCreate({
-  subject: "Implement subtask MOB-123",
+  subject: "MM-123-1 Implement subtask",
   description: "Full implementation cycle: classify → orchestrate → implement → verify",
-  activeForm: "Implementing subtask MOB-123"
+  activeForm: "MM-123-1 Implementing subtask"
+})
+TaskCreate({
+  subject: "MM-123-1 UI change classification",
+  description: "Delegate to shared-ui-classifier agent",
+  activeForm: "MM-123-1 Classifying UI changes"
+})
+TaskCreate({
+  subject: "MM-123-1 Verify implementation",
+  description: "Run tests, lint, build check",
+  activeForm: "MM-123-1 Verifying implementation"
 })
 ```
 

package/plugins/flow-legacy/skills/plan/SKILL.md

@@ -46,13 +46,24 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 **MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
 
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
 **At skill start**: Create tasks for each checklist step using `TaskCreate`:
 
 ```
 TaskCreate({
-  subject: "Fetch Linear task",
+  subject: "MM-123 Fetch Linear task",
   description: "Get title, description, labels, priority, estimate from MCP Linear server",
-  activeForm: "Fetching Linear task"
+  activeForm: "MM-123 Fetching Linear task"
+})
+TaskCreate({
+  subject: "MM-123 Analyze codebase",
+  description: "Explore affected files, patterns, dependencies, and test coverage",
+  activeForm: "MM-123 Analyzing codebase"
 })
 ```
 

package/plugins/flow-legacy/skills/push/SKILL.md

@@ -66,13 +66,24 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 **MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
 
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
 **At skill start**: Create tasks for each checklist step using `TaskCreate`:
 
 ```
 TaskCreate({
-  subject: "Check git status",
+  subject: "MM-123 Check git status",
   description: "Verify branch, commits ahead, warn about uncommitted changes",
-  activeForm: "Checking git status"
+  activeForm: "MM-123 Checking git status"
+})
+TaskCreate({
+  subject: "MM-123 Push to remote",
+  description: "Execute git push and handle errors",
+  activeForm: "MM-123 Pushing to remote"
 })
 ```