@smartsoft001-mobilems/claude-plugins 2.85.0 → 2.87.0

package/plugins/flow-external/skills/angular-patterns/SKILL.md

@@ -1,170 +0,0 @@
----
-name: angular-patterns
-description: Angular 6-11 legacy patterns including *ngIf/*ngFor directives, constructor DI, @Input/@Output decorators, and NgRx state management
----
-
-# Angular 6-11 Patterns
-
-This skill provides guidance on Angular 6-11 patterns for standalone projects.
-
-## CRITICAL: Use Legacy Patterns ONLY
-
-**DO NOT use modern Angular features (Angular 14+):**
-
-| Feature | CORRECT (Angular 6-11) | WRONG (Modern) |
-|---------|------------------------|----------------|
-| Control flow | `*ngIf`, `*ngFor`, `[ngSwitch]` | `@if`, `@for`, `@switch` |
-| DI | Constructor injection | `inject()` |
-| Inputs | `@Input()` decorator | `input()` function |
-| Outputs | `@Output()` decorator | `output()` function |
-| Two-way | `@Input()` + `@Output()` | `model()` |
-| State | BehaviorSubject, NgRx | signals, `signal()` |
-| Derived | `pipe(map())`, getters | `computed()` |
-| Side effects | `subscribe()`, NgRx effects | `effect()` |
-| Components | NgModule-based | standalone |
-
-## 1. Control Flow
-
-```html
-<!-- *ngIf with else -->
-<div *ngIf="isLoading; else content">
-  <app-spinner></app-spinner>
-</div>
-<ng-template #content>
-  <ul>
-    <li *ngFor="let item of items; trackBy: trackById">{{ item.name }}</li>
-  </ul>
-</ng-template>
-```
-
-```typescript
-trackById(index: number, item: Item): string {
-  return item.id;
-}
-```
-
-## 2. BehaviorSubject State Management
-
-```typescript
-@Injectable({ providedIn: 'root' })
-export class StateService {
-  private readonly _items = new BehaviorSubject<Item[]>([]);
-  readonly items$ = this._items.asObservable();
-
-  readonly count$ = this._items.pipe(
-    map(items => items.length)
-  );
-
-  setItems(items: Item[]): void {
-    this._items.next(items);
-  }
-}
-```
-
-## 3. Constructor Injection
-
-```typescript
-@Component({
-  selector: 'app-feature',
-  templateUrl: './feature.component.html',
-})
-export class FeatureComponent implements OnInit, OnDestroy {
-  private readonly destroy$ = new Subject<void>();
-
-  constructor(
-    private readonly service: FeatureService,
-    private readonly router: Router
-  ) {}
-
-  ngOnInit(): void {
-    this.service.items$
-      .pipe(takeUntil(this.destroy$))
-      .subscribe(items => this.items = items);
-  }
-
-  ngOnDestroy(): void {
-    this.destroy$.next();
-    this.destroy$.complete();
-  }
-}
-```
-
-## 4. Input/Output Decorators
-
-```typescript
-@Component({
-  selector: 'app-card',
-  templateUrl: './card.component.html',
-})
-export class CardComponent {
-  @Input() item!: Item;
-  @Input() showActions = true;
-  @Output() selected = new EventEmitter<Item>();
-
-  // Two-way binding
-  @Input() value = '';
-  @Output() valueChange = new EventEmitter<string>();
-}
-```
-
-## 5. NgModule
-
-```typescript
-@NgModule({
-  declarations: [FeatureComponent, CardComponent],
-  imports: [CommonModule, TranslateModule, NgbModule],
-  exports: [FeatureComponent],
-})
-export class FeatureModule {}
-```
-
-## 6. NgRx Patterns
-
-```typescript
-// Actions
-export const loadItems = createAction('[Items] Load');
-export const loadItemsSuccess = createAction('[Items] Load Success', props<{ items: Item[] }>());
-
-// Reducer
-export const reducer = createReducer(
-  initialState,
-  on(loadItems, state => ({ ...state, loading: true })),
-  on(loadItemsSuccess, (state, { items }) => ({ ...state, items, loading: false }))
-);
-
-// Effects
-@Injectable()
-export class ItemEffects {
-  constructor(private actions$: Actions, private service: ItemService) {}
-
-  load$ = createEffect(() => this.actions$.pipe(
-    ofType(loadItems),
-    mergeMap(() => this.service.getAll().pipe(
-      map(items => loadItemsSuccess({ items })),
-      catchError(error => of(loadItemsFailure({ error: error.message })))
-    ))
-  ));
-}
-```
-
-## 7. Async Pipe
-
-```html
-<div *ngIf="isLoading$ | async; else content">Loading...</div>
-<ng-template #content>
-  <li *ngFor="let item of items$ | async; trackBy: trackById">
-    {{ item.name }}
-  </li>
-</ng-template>
-```
-
-## 8. PR Checklist
-
-- [ ] Using `*ngIf`/`*ngFor` (NOT `@if`/`@for`)
-- [ ] Every `*ngFor` has `trackBy`
-- [ ] Using constructor DI (NOT `inject()`)
-- [ ] Using `@Input()`/`@Output()` (NOT `input()`/`output()`)
-- [ ] Using BehaviorSubject/NgRx for state (NOT signals)
-- [ ] Component declared in NgModule
-- [ ] Using `async` pipe in templates
-- [ ] `OnDestroy` with `takeUntil` pattern

package/plugins/flow-external/skills/browser-capture/SKILL.md

@@ -1,68 +0,0 @@
----
-name: browser-capture
-description: Manage browser sessions and capture screenshots. Ensures dev server is running, navigates to pages, and captures responsive screenshots.
-allowed-tools:
-  - Bash
-  - Read
-  - Glob
-  - mcp__playwright__browser_navigate
-  - mcp__playwright__browser_snapshot
-  - mcp__playwright__browser_take_screenshot
-  - mcp__playwright__browser_resize
-  - mcp__playwright__browser_close
----
-
-# Browser Capture Skill
-
-Capture screenshots of web pages at multiple viewport sizes.
-
-## Server Management
-
-### Detect Port
-
-```bash
-# Check angular.json location and read port
-if [ -f "angular.json" ]; then
-  grep -o '"port":[^,}]*' angular.json | head -1
-elif [ -f "app/angular.json" ]; then
-  grep -o '"port":[^,}]*' app/angular.json | head -1
-fi
-# Default: 4200
-```
-
-### Start Server if Needed
-
-```bash
-lsof -i :4200 -t || (npm start & for i in {1..15}; do curl -s http://localhost:4200 > /dev/null && break; sleep 2; done)
-```
-
-## Capture Process
-
-1. Ensure server is running
-2. Navigate to URL with `mcp__playwright__browser_navigate`
-3. For each viewport:
-   - `mcp__playwright__browser_resize` → set dimensions
-   - `mcp__playwright__browser_take_screenshot` → capture
-
-### Viewport Sizes
-
-| Name | Width | Height |
-|------|-------|--------|
-| Desktop | 1920 | 1080 |
-| Tablet | 768 | 1024 |
-| Mobile | 375 | 667 |
-
-## Upload
-
-Delegate to `maia-api` agent for upload to temporary storage.
-
-## Output
-
-```json
-{
-  "screenshots": [
-    { "viewport": "desktop", "url": "https://maia-ai-api.smartsoft.biz.pl/files/abc123" },
-    { "viewport": "mobile", "url": "https://maia-ai-api.smartsoft.biz.pl/files/def456" }
-  ]
-}
-```

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

@@ -1,114 +0,0 @@
----
-name: commit
-description: Create a conventional commit message based on Linear task and staged changes. Fetches task details, analyzes changes, and generates commit message.
-allowed-tools:
-  - Bash
-  - Read
-  - Glob
-  - Grep
-  - AskUserQuestion
-  - mcp__linear__get_issue
-  - mcp__linear__list_comments
----
-
-# Commit Skill
-
-Create a conventional commit message based on Linear task and staged changes.
-
-## Usage
-
-```
-/commit [linearTaskId]
-```
-
-## Parameters
-
-- `linearTaskId` - Linear task ID (e.g., MOB-123)
-
-## Execution Checklist
-
-- [ ] **1. Fetch Linear task** — get title, description, labels/type from MCP Linear server
-- [ ] **2. Analyze staged changes** — run `git diff --cached` to understand scope
-- [ ] **3. Verify completeness** — compare task requirements with staged changes; if incomplete, ask user whether to continue or stop
-- [ ] **4. Determine commit type and scope** — based on changes and task type
-- [ ] **5. Generate commit message** — draft `<type>(<scope>): <subject>` with body and `Refs: <linearTaskId>`
-- [ ] **6. Show message to user** — present commit message for approval before proceeding
-- [ ] **7. Create commit** — execute `git commit` with the approved message
-
-## Commit Message Format
-
-```
-<type>(<scope>): <subject>
-
-<body>
-
-Refs: <linearTaskId>
-```
-
-### Type
-
-| Type       | Use when                                   |
-| ---------- | ------------------------------------------ |
-| `feat`     | New feature or functionality               |
-| `fix`      | Bug fix                                    |
-| `refactor` | Code restructuring without behavior change |
-| `style`    | Styling/CSS changes only                   |
-| `docs`     | Documentation changes                      |
-| `chore`    | Maintenance, config, dependencies          |
-| `perf`     | Performance improvements                   |
-
-### Scope
-
-Determine scope from the changed files and project structure. Common scopes for external projects:
-
-- Component name (e.g., `gallery`, `articles`, `navigation`)
-- Feature area (e.g., `wcag`, `i18n`, `auth`)
-- Infrastructure (e.g., `config`, `docker`)
-
-### Subject
-
-- Imperative mood ("add feature" not "added feature")
-- Lowercase first letter
-- No period at end
-- Max 72 characters
-
-### Body
-
-- Explain WHAT changed and WHY
-- Reference Linear task
-- List affected files if helpful
-
-## Example
-
-```
-feat(gallery): add lightbox for exhibition photos
-
-Add lightbox modal for viewing gallery photos in full screen.
-Uses ng-bootstrap modal with keyboard navigation support.
-
-Refs: MOB-548
-```
-
-## Error Handling
-
-### No Staged Changes
-
-```markdown
-## No staged changes
-
-Run `git add` to stage your changes before committing.
-```
-
-### Linear Task Not Found
-
-If linearTaskId is not provided or task not found:
-
-- Try to detect from branch name
-- If still not found, proceed without Linear context
-
-## Guidelines
-
-1. **Always show commit message for approval** before creating the commit
-2. **Use Polish branch naming** if branch follows MOB-XXX pattern
-3. **Include Refs:** with Linear task ID when available
-4. **Keep subject line under 72 characters**

package/plugins/flow-external/skills/debug-helper/SKILL.md

@@ -1,131 +0,0 @@
----
-name: debug-helper
-description: Debugging workflows for Angular 6-11 standalone projects
----
-
-# Debug Helper (Angular 6-11)
-
-Debugging workflows for standalone Angular CLI projects.
-
-## 1. Angular Debugging
-
-### Component Not Rendering
-
-1. Check selector matches template usage
-2. Check NgModule declarations - is component declared?
-3. Check NgModule exports - is it exported for external use?
-4. Check NgModule imports - is the feature module imported?
-
-### BehaviorSubject Issues
-
-```typescript
-// Wrong: mutating array (won't trigger update)
-const items = this._items.getValue();
-items.push(newItem);
-this._items.next(items);
-
-// Correct: create new reference
-this._items.next([...this._items.getValue(), newItem]);
-```
-
-### Memory Leaks
-
-```typescript
-// Always use takeUntil pattern
-private readonly destroy$ = new Subject<void>();
-
-ngOnInit(): void {
-  this.service.data$
-    .pipe(takeUntil(this.destroy$))
-    .subscribe(data => this.data = data);
-}
-
-ngOnDestroy(): void {
-  this.destroy$.next();
-  this.destroy$.complete();
-}
-```
-
-### Change Detection
-
-```typescript
-constructor(private cdr: ChangeDetectorRef) {}
-
-// Force detection
-this.cdr.detectChanges();
-
-// Mark for check (OnPush)
-this.cdr.markForCheck();
-```
-
-### Template Debugging
-
-```html
-<pre>{{ data | json }}</pre>
-<p>isLoading: {{ isLoading }}</p>
-```
-
-## 2. NgRx Debugging
-
-### State Not Updating
-
-1. Verify action is dispatched: add `tap(action => console.log(action))` to effects
-2. Verify reducer handles the action
-3. Verify selector reads correct state slice
-4. Check Redux DevTools (install Chrome extension)
-
-### Effects Not Running
-
-1. Check effect is registered in `EffectsModule.forFeature([Effects])`
-2. Check `ofType` matches dispatched action
-3. Check effect observable completes (use `mergeMap` not `switchMap` for parallel)
-
-## 3. Common Errors
-
-### "Cannot read property of undefined"
-
-```typescript
-// Use optional chaining
-const name = user?.profile?.name ?? 'Unknown';
-
-// In templates
-{{ user?.profile?.name }}
-```
-
-### "Expression has changed after it was checked"
-
-```typescript
-ngAfterViewInit(): void {
-  setTimeout(() => this.value = newValue);
-}
-```
-
-### "NullInjectorError: No provider for X"
-
-```typescript
-// Add to module providers or use providedIn: 'root'
-@Injectable({ providedIn: 'root' })
-export class MyService {}
-```
-
-### "Circular dependency detected"
-
-```typescript
-// Use forwardRef
-@Inject(forwardRef(() => ServiceB))
-private serviceB: ServiceB
-```
-
-## 4. Build Errors
-
-```bash
-# Check TypeScript errors
-npx tsc --noEmit
-
-# Check Angular build
-ng build --prod 2>&1 | head -50
-
-# Common: AOT compilation errors
-# - Private members used in templates (make them public or use getters)
-# - Function calls in templates (extract to component methods)
-```

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

@@ -1,217 +0,0 @@
----
-name: impl
-description: Implement plans from `plan.md` attachments on Linear issues. Reads approved plan attachment, orchestrates agents (saving `orchestration.md` attachment), and executes changes step by step.
-allowed-tools:
-  - Bash
-  - Read
-  - Write
-  - Edit
-  - Glob
-  - Grep
-  - AskUserQuestion
-  - mcp__linear__get_issue
-  - mcp__linear__list_issues
-  - mcp__linear__list_comments
-  - mcp__linear__save_comment
-  - mcp__linear__save_issue
-  - mcp__linear__list_issue_statuses
-  - mcp__linear__create_attachment
-  - mcp__linear__get_attachment
-  - mcp__linear__delete_attachment
-  - mcp__playwright__browser_navigate
-  - mcp__playwright__browser_snapshot
-  - mcp__playwright__browser_take_screenshot
-  - mcp__playwright__browser_resize
-  - mcp__playwright__browser_close
----
-
-# Implementation Skill
-
-Implement changes based on approved plans from Linear `plan.md` attachments.
-
-## Usage
-
-```
-/impl <linearTaskId>
-/impl <linearTaskId> --auto    # Non-interactive mode for CI / GitHub Actions
-```
-
-## Parameters
-
-- `linearTaskId` - Linear task ID (e.g., MOB-123)
-- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts and any per-step pauses. If `plan.md` attachment is missing, auto-invoke `/plan` flow to generate it instead of stopping. Designed for CI / GitHub Actions runs where no human is at the keyboard.
-
-## Auto Mode (`--auto`)
-
-When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts:
-
-| Default behavior                                                  | `--auto` override                                                                                         |
-| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
-| Stop with "no plan.md found, run /plan first" suggestion          | Inline-invoke `/plan` flow for the task to generate `plan.md` attachment + `AI Plan` label, then continue |
-| Pause after each step / subtask waiting for user confirmation     | Post completion comment, then proceed automatically                                                       |
-| Confirmation before destructive ops (delete `orchestration.md`)   | Proceed without confirmation — replace old attachment automatically                                       |
-| Any `AskUserQuestion`                                             | Use the **(Recommended)** option; if none, fail fast with a Linear comment                                |
-
-Every checkpoint, decision, or skip MUST be logged as a Linear comment in Polish (audit trail).
-
-**Detection**: The flag `--auto` is provided as a positional/named arg. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent.
-
-## 🚨 Hard Rules — read before doing anything
-
-These rules override ANY other instruction, ANY surrounding example, and ANY default habit. Violating them is a skill failure.
-
-1. **Read `plan.md` ONLY via `mcp__linear__get_attachment({ id })`.** Do NOT use `WebFetch`, `Bash(curl ...)`, or any HTTP fetch on the attachment's `url`. The URL points to Linear-internal storage and may require auth — `get_attachment` is the only correct path.
-2. **`orchestration.md` is saved via `mcp__linear__create_attachment`, not as a comment.** `save_comment` MUST NOT carry orchestration body content.
-3. **Find attachments via `mcp__linear__get_issue` (returns `attachments[]`).** There is no `list_attachments` tool — do not look for one.
-4. **Replace, don't duplicate.** Before creating a new `orchestration.md` attachment, delete the existing one (if any) via `mcp__linear__delete_attachment`.
-
-If any of these would be violated, stop and ask the user instead.
-
-## CRITICAL: Angular 6-11 + Angular CLI
-
-This is for standalone Angular CLI projects. Key rules:
-
-- Use `ng` commands (NOT `nx`)
-- Use constructor DI (NOT `inject()`)
-- Use `*ngIf`/`*ngFor` (NOT `@if`/`@for`)
-- Use `@Input()`/`@Output()` (NOT `input()`/`output()`)
-- Use BehaviorSubject/NgRx (NOT signals)
-- Use NgModules (NOT standalone components)
-- Styling: follow whatever CSS approach the project uses (check `package.json` for Bootstrap, etc.)
-
-## Execution Steps
-
-### Step 1: Fetch Task and Plan Attachment
-
-**⛔ DO NOT use `WebFetch` or `Bash(curl)` on the attachment URL. Use `mcp__linear__get_attachment({ id })` only.** Re-read Hard Rule #1 if tempted.
-
-1. `mcp__linear__get_issue({ id: taskId })` — the response includes an `attachments[]` array.
-2. Find the attachment where `title == "plan.md"` (or `filename == "plan.md"`) and capture its `id`. Do NOT use the `url` field for fetching.
-3. `mcp__linear__get_attachment({ id: <attachmentId> })` — returns the markdown content directly (Linear hosts the file natively).
-4. Parse the plan content.
-5. If no `plan.md` attachment exists:
-   - **Default mode**: inform the user and suggest running `/plan <taskId>` first. Stop the skill.
-   - **`--auto` mode**: inline-invoke the `/plan` skill flow for this task to generate `plan.md` attachment + `AI Plan` label, then proceed with implementation. Post a Linear comment in Polish noting the plan was auto-generated.
-
-   Do NOT fall back to parsing plan content from comments, and do NOT attempt `curl`/`WebFetch` on a URL.
-
-### Step 2: Detect Project Structure
-
-Before implementing, detect the project layout:
-
-```bash
-# Check if angular.json is at root or in app/ subdirectory
-ls angular.json 2>/dev/null && echo "ROOT" || (ls app/angular.json 2>/dev/null && echo "APP_DIR")
-
-# Check package.json for dependencies
-cat package.json 2>/dev/null || cat app/package.json 2>/dev/null
-```
-
-Key things to detect:
-
-- Angular version (6-11)
-- CSS framework (Bootstrap 4 / custom SCSS / none)
-- NgRx version and patterns
-- i18n setup (ngx-translate)
-- Project structure (app/src/ vs src/)
-
-### Step 3: List Subtasks
-
-If task has subtasks:
-
-1. Fetch subtasks using `mcp__linear__list_issues` with parent filter
-2. Sort by priority/creation order
-3. Process each subtask in order
-
-### Step 3a: Save Orchestration Plan as Native Linear Attachment
-
-**⛔ Calling `mcp__linear__save_comment` with the orchestration body is FORBIDDEN. Use `mcp__linear__create_attachment` only.** Re-read Hard Rule #2 if tempted.
-
-Use `shared-impl-orchestrator` agent to generate a `🎭 Agent Orchestration Plan` that lists which agents run in what order (Angular 6-11 + CLI context).
-
-Then save it as an `orchestration.md` attachment on the task (not as a comment):
-
-1. **Replace existing orchestration**: use `mcp__linear__get_issue` to list attachments; if one titled `orchestration.md` exists, delete it via `mcp__linear__delete_attachment({ id: oldAttachmentId })`. Linear hosts the file natively, so nothing else needs cleanup.
-2. **Write locally**: `Write` the orchestration markdown to `/tmp/claude-plans/<taskId>-orchestration.md`.
-3. **Base64-encode**: `b64=$(base64 -i /tmp/claude-plans/<taskId>-orchestration.md)`.
-4. **Create Linear attachment** via `mcp__linear__create_attachment`:
-   - `issue`: the task ID
-   - `filename`: `orchestration.md`
-   - `contentType`: `text/markdown`
-   - `title`: `orchestration.md` (exact)
-   - `subtitle`: `Plan orkiestracji wygenerowany przez Claude Code (external)`
-   - `base64Content`: the base64 string from step 3
-5. **Clean up** local `/tmp/claude-plans/<taskId>-orchestration.md` file after the attachment is created.
-
-### Step 4: Implement Each Step
-
-For each step in the plan:
-
-1. **Read relevant files** - Understand existing code before modifying
-2. **Follow existing patterns** - Match the codebase style exactly
-3. **Create/modify files** - Implement the planned changes
-4. **Register in modules** - Add declarations/imports to NgModules
-5. **Update subtask status** - Mark as Done when complete
-
-### Step 5: Build Verification
-
-After all steps are complete:
-
-```bash
-# Verify build passes (adapt path based on project structure)
-ng build --prod
-# OR
-cd app && ng build --prod
-```
-
-### Step 6: Report Results
-
-Create a summary comment on the Linear task:
-
-```markdown
-## Raport Implementacji
-
-### Zrealizowane
-
-| Podzadanie | Tytul   | Status       |
-| ---------- | ------- | ------------ |
-| MOB-549    | [title] | Zrealizowane |
-
-### Zmiany
-
-| Plik                                      | Typ           | Opis              |
-| ----------------------------------------- | ------------- | ----------------- |
-| `src/app/components/feature.component.ts` | Nowy          | Komponent         |
-| `src/app/components/feature.module.ts`    | Zmodyfikowany | Dodano deklaracje |
-
-### Build
-
-- `ng build --prod` - Sukces
-
----
-
-_Raport wygenerowany przez Claude Code_
-```
-
-## Agent Selection
-
-| Task Type      | Agent                                                |
-| -------------- | ---------------------------------------------------- |
-| New component  | `angular-component-scaffolder`                       |
-| New service    | `angular-service-builder`                            |
-| NgRx state     | `angular-state-builder`                              |
-| New directive  | `angular-directive-builder`                          |
-| New pipe       | `angular-pipe-builder`                               |
-| Guard/resolver | `angular-guard-builder` / `angular-resolver-builder` |
-| Styling        | `ui-web-designer`                                    |
-
-## Guidelines
-
-1. **Always read existing code first** before making changes
-2. **Follow the project's existing patterns** exactly
-3. **Register everything in NgModules** - declarations, imports, exports
-4. **Use the project's CSS approach** - detect from package.json
-5. **Write all Linear comments in Polish**
-6. **Verify build after implementation**
-7. **Do NOT add tests** unless explicitly requested
-8. **Do NOT modify deployment configuration**