@smartsoft001/pro-claude-plugins 0.2.0

package/plugins/flow/skills/karpathy-guidelines/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: karpathy-guidelines
+description: Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
+license: MIT
+---
+
+# Karpathy Guidelines
+
+Behavioral guidelines to reduce common LLM coding mistakes, derived from [Andrej Karpathy's observations](https://x.com/karpathy/status/2015883857489522876) on LLM coding pitfalls.
+
+**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
+
+## 1. Think Before Coding
+
+**Don't assume. Don't hide confusion. Surface tradeoffs.**
+
+Before implementing:
+
+- State your assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them - don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
+
+## 2. Simplicity First
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+## 3. Surgical Changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+When editing existing code:
+
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it - don't delete it.
+
+When your changes create orphans:
+
+- Remove imports/variables/functions that YOUR changes made unused.
+- Don't remove pre-existing dead code unless asked.
+
+The test: Every changed line should trace directly to the user's request.
+
+## 4. Goal-Driven Execution
+
+**Define success criteria. Loop until verified.**
+
+Transform tasks into verifiable goals:
+
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step tasks, state a brief plan:
+
+```
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+```
+
+Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

package/plugins/flow/skills/linear-suggestion/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: linear-suggestion
+description: Create a Linear issue in the "Framework 2.0" project with a suggestion for agent or skill improvements.
+allowed-tools: mcp__linear__save_issue
+---
+
+# Linear Suggestion
+
+Create a Linear issue in the **Framework 2.0** project containing a suggestion for improving agent definitions or skills. Used by automated analysis agents to propose changes without blocking the workflow.
+
+## When to Use
+
+- When an automated agent (e.g., `shared-parallelization-analyzer`) identifies a recurring pattern that could improve an agent or skill
+- When proposing orchestrator rule changes based on parallelization analysis
+- When any non-interactive process needs to suggest framework improvements
+
+## Input Parameters
+
+The invoking agent must provide:
+
+| Parameter     | Required | Description                                                                   |
+| ------------- | -------- | ----------------------------------------------------------------------------- |
+| `title`       | YES      | Short summary of the suggestion (max 100 chars)                               |
+| `description` | YES      | Full markdown description with rationale and proposed changes                 |
+| `source`      | YES      | Agent that generated the suggestion (e.g., `shared-parallelization-analyzer`) |
+| `targetFile`  | NO       | Path to the file to be modified (e.g., `agents/shared-impl-orchestrator.md`)  |
+| `category`    | NO       | One of: `OPTIMIZATION`, `NEW_RULE`, `PATTERN_UPDATE`, `BUG_FIX`               |
+
+## Issue Format
+
+### Title
+
+```
+[Agent Suggestion] {title}
+```
+
+### Description
+
+```markdown
+## Agent Improvement Suggestion
+
+**Source agent**: `{source}`
+**Category**: {category}
+**Target file**: `{targetFile}`
+
+---
+
+{description}
+
+---
+
+_This issue was automatically created by `{source}` via the `linear-suggestion` skill._
+_Review and apply manually if the suggestion is valid._
+```
+
+## Process
+
+1. **Format the issue title** with `[Agent Suggestion]` prefix
+2. **Build the description** using the template above, inserting all provided parameters
+3. **Create the issue** using MCP Linear server:
+
+   ```
+   Create issue in project "Framework 2.0":
+   - Title: [Agent Suggestion] {title}
+   - Description: {formatted description}
+   - Label: agent-evolution
+   ```
+
+4. **Return the issue ID and URL** to the invoking agent
+
+## Output Format
+
+After successful creation, return:
+
+```
+Linear issue created:
+- ID: {issueId}
+- Title: [Agent Suggestion] {title}
+- URL: {issueUrl}
+```
+
+## Error Handling
+
+If issue creation fails (e.g., MCP Linear server unavailable):
+
+- Log the error silently
+- Do NOT block the parent workflow
+- Return a failure notice without throwing
+
+```
+Linear suggestion skipped: {error reason}
+```
+
+## Example
+
+**Input from `shared-parallelization-analyzer`:**
+
+```
+title: Add parallel scaffolding rule to orchestrator
+description: |
+  ### Observation
+
+  In 3 out of 5 recent tasks, scaffolding agents for independent files
+  (e.g., `angular-component-scaffolder` + `angular-service-builder`) were
+  marked as SEQ despite having no shared output files.
+
+  ### Proposed Change
+
+  Add to `shared-impl-orchestrator.md` → Execution Patterns → Parallel vs Sequential:
+
+  | Scenario                                | Pattern  | Reason                          |
+  | --------------------------------------- | -------- | ------------------------------- |
+  | Multiple scaffolding for independent files | PARALLEL | No shared output files between scaffolders |
+
+  ### Evidence
+
+  - FRA-700: scaffold-component + scaffold-service (independent)
+  - FRA-705: scaffold-directive + scaffold-service (independent)
+  - FRA-710: scaffold-component + scaffold-pipe (independent)
+source: shared-parallelization-analyzer
+targetFile: packages/shared/claude-plugins/src/plugins/flow/agents/shared-impl-orchestrator.md
+category: OPTIMIZATION
+```
+
+**Created issue:**
+
+```
+Linear issue created:
+- ID: FRA-100
+- Title: [Agent Suggestion] Add parallel scaffolding rule to orchestrator
+- URL: https://linear.app/smartflow001/issue/FRA-100
+```

package/plugins/flow/skills/maia-files-delete/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: maia-files-delete
+description: Delete a file from Maia API temporary storage.
+allowed-tools: Bash
+---
+
+# Maia Files Delete
+
+Delete a file from Maia AI API temporary storage to free up space.
+
+## API Endpoint
+
+```
+DELETE https://maia-ai-api.smartsoft.biz.pl/files/{id}
+```
+
+## Usage
+
+When given a file ID or URL, delete it:
+
+```bash
+curl -s -X DELETE https://maia-ai-api.smartsoft.biz.pl/files/{id}
+```
+
+## Process
+
+1. Extract ID from input (can be full URL or just ID)
+2. Send DELETE request
+3. Confirm deletion
+
+## Input Formats
+
+Accept either:
+
+- Full URL: `https://maia-ai-api.smartsoft.biz.pl/files/abc123`
+- Just ID: `abc123`
+
+## Output Format
+
+After successful deletion:
+
+```
+Deleted: {id}
+```
+
+## Batch Deletion
+
+When given multiple IDs, delete them all:
+
+```bash
+for id in id1 id2 id3; do
+  curl -s -X DELETE "https://maia-ai-api.smartsoft.biz.pl/files/$id"
+  echo "Deleted: $id"
+done
+```
+
+## Error Handling
+
+If deletion fails, report the error but continue with remaining files.

package/plugins/flow/skills/maia-files-upload/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: maia-files-upload
+description: Upload a file to Maia API temporary storage.
+allowed-tools: Bash
+---
+
+# Maia Files Upload
+
+Upload a file to the Maia AI API temporary storage and get a URL for use in Linear comments or markdown.
+
+## API Endpoint
+
+```
+POST https://maia-ai-api.smartsoft.biz.pl/files
+```
+
+## Usage
+
+When given a file path, upload it:
+
+```bash
+curl -s -X POST https://maia-ai-api.smartsoft.biz.pl/files \
+  -F "file=@/path/to/file.png"
+```
+
+## Response
+
+```json
+{ "id": "abc123def456" }
+```
+
+## Result URL
+
+```
+https://maia-ai-api.smartsoft.biz.pl/files/{id}
+```
+
+## Process
+
+1. Validate file exists: `test -f "/path/to/file" && echo "OK"`
+2. Upload file using curl
+3. Extract ID from JSON response
+4. Return ID and full URL
+
+## Output Format
+
+After successful upload, return:
+
+```
+Uploaded: {filename}
+ID: {id}
+URL: https://maia-ai-api.smartsoft.biz.pl/files/{id}
+```
+
+## Error Handling
+
+If file doesn't exist or upload fails, report the error clearly.

package/plugins/flow/skills/nx-conventions/SKILL.md

@@ -0,0 +1,326 @@
+---
+name: nx-conventions
+description: Nx monorepo patterns, workspace organization, and build conventions
+---
+
+# Nx Conventions
+
+This skill provides guidance on Nx monorepo patterns for this project.
+
+## 1. Workspace Structure
+
+```
+/
+├── apps/
+│   ├── web/              # Main Angular SSR application
+│   └── web-e2e/          # Cypress E2E tests
+├── libs/
+│   └── shared/
+│       └── angular/      # Shared Angular library
+├── tools/
+│   ├── specs/            # Project specifications
+│   └── mockups/          # Design mockups
+├── nx.json               # Nx workspace configuration
+├── tsconfig.base.json    # Base TypeScript config
+└── package.json
+```
+
+## 2. Project Naming
+
+| Type                | Pattern                  | Example                        |
+| ------------------- | ------------------------ | ------------------------------ |
+| Apps                | `{name}`                 | `web`, `api`                   |
+| E2E                 | `{app}-e2e`              | `web-e2e`                      |
+| Domain libs         | `{domain}-domain`        | `museum-objects-domain`        |
+| Angular libs        | `{domain}-shell-angular` | `museum-objects-shell-angular` |
+| Shared angular libs | `shared-angular`         | `shared-angular`               |
+
+## 3. Common Nx Commands
+
+### Development
+
+```bash
+# Serve application
+nx serve web
+
+# Serve with specific configuration
+nx serve web --configuration=development
+
+# Build application
+nx build web
+
+# Build for production
+nx build web --configuration=production
+```
+
+### Testing
+
+```bash
+# Run unit tests
+nx test web
+nx test shared-angular
+
+# Run tests with coverage
+nx test web --coverage
+
+# Run tests in watch mode
+nx test web --watch
+
+# Run E2E tests
+nx e2e web-e2e
+
+# Open Cypress
+nx open-cypress web-e2e
+```
+
+### Linting
+
+```bash
+# Lint project
+nx lint web
+nx lint shared-angular
+
+# Lint all affected projects
+nx affected --target=lint
+```
+
+### Building
+
+```bash
+# Build single project
+nx build web
+
+# Build affected projects
+nx affected --target=build
+
+# Show dependency graph
+nx graph
+```
+
+## 4. Affected Commands
+
+Run tasks only on changed projects:
+
+```bash
+# Test affected
+nx affected --target=test
+
+# Lint affected
+nx affected --target=lint
+
+# Build affected
+nx affected --target=build
+
+# Specify base branch
+nx affected --target=test --base=main
+```
+
+## 5. Project Configuration
+
+### project.json
+
+```json
+{
+  "name": "web",
+  "$schema": "../../node_modules/nx/schemas/project-schema.json",
+  "projectType": "application",
+  "sourceRoot": "apps/web/src",
+  "prefix": "app",
+  "targets": {
+    "build": {
+      "executor": "@angular-devkit/build-angular:application",
+      "options": {
+        "outputPath": "dist/apps/web",
+        "index": "apps/web/src/index.html",
+        "browser": "apps/web/src/main.ts",
+        "polyfills": ["zone.js"],
+        "tsConfig": "apps/web/tsconfig.app.json"
+      },
+      "configurations": {
+        "production": {
+          "budgets": [
+            {
+              "type": "initial",
+              "maximumWarning": "2MB",
+              "maximumError": "4MB"
+            }
+          ],
+          "outputHashing": "all"
+        },
+        "development": {
+          "optimization": false,
+          "sourceMap": true
+        }
+      },
+      "defaultConfiguration": "development"
+    },
+    "serve": {
+      "executor": "@angular-devkit/build-angular:dev-server",
+      "options": {
+        "port": 4210
+      }
+    },
+    "test": {
+      "executor": "@nx/jest:jest",
+      "options": {
+        "jestConfig": "apps/web/jest.config.ts",
+        "passWithNoTests": true
+      },
+      "configurations": {
+        "ci": {
+          "codeCoverage": true
+        }
+      }
+    }
+  }
+}
+```
+
+## 6. Path Mappings
+
+In `tsconfig.base.json`:
+
+```json
+{
+  "compilerOptions": {
+    "paths": {
+      "@shared/angular": ["libs/shared/angular/src/index.ts"],
+      "@shared/angular/*": ["libs/shared/angular/src/lib/*"]
+    }
+  }
+}
+```
+
+Usage:
+
+```typescript
+import { SharedModule } from '@shared/angular';
+import { MyService } from '@shared/angular/services';
+```
+
+## 7. Library Types
+
+### Feature Library
+
+Contains smart components, routes, and business logic.
+
+```typescript
+// libs/museum/feature-objects/src/index.ts
+export * from './lib/objects.routes';
+export * from './lib/containers';
+```
+
+### UI Library
+
+Contains presentational (dumb) components only.
+
+```typescript
+// libs/shared/ui/src/index.ts
+export * from './lib/button/button.component';
+export * from './lib/card/card.component';
+```
+
+### Data Access Library
+
+Contains services, state management, and API calls.
+
+```typescript
+// libs/museum/data-access/src/index.ts
+export * from './lib/services/objects.service';
+export * from './lib/+state/objects.facade';
+```
+
+### Utility Library
+
+Contains pure functions, helpers, and utilities.
+
+```typescript
+// libs/shared/util-forms/src/index.ts
+export * from './lib/validators';
+export * from './lib/form-helpers';
+```
+
+## 8. Caching
+
+Nx caches task results. Configure in `nx.json`:
+
+```json
+{
+  "targetDefaults": {
+    "build": {
+      "cache": true,
+      "dependsOn": ["^build"]
+    },
+    "test": {
+      "cache": true
+    },
+    "lint": {
+      "cache": true
+    }
+  }
+}
+```
+
+## 9. Task Dependencies
+
+Define task execution order:
+
+```json
+{
+  "targetDefaults": {
+    "build": {
+      "dependsOn": ["^build"]
+    },
+    "test": {
+      "dependsOn": ["build"]
+    }
+  }
+}
+```
+
+- `^build` means build dependencies first
+- `build` means build this project first
+
+## 10. Generators
+
+Create new code with generators:
+
+```bash
+# Generate Angular component
+nx g @nx/angular:component my-component --project=shared-angular
+
+# Generate Angular service
+nx g @nx/angular:service my-service --project=shared-angular
+
+# Generate library
+nx g @nx/angular:library my-lib --directory=shared
+
+# Dry run (preview changes)
+nx g @nx/angular:component my-component --dry-run
+```
+
+## 11. CI/CD Integration
+
+```yaml
+# Example GitHub Actions
+- name: Install dependencies
+  run: npm ci
+
+- name: Run affected lint
+  run: npx nx affected --target=lint --base=origin/main
+
+- name: Run affected test
+  run: npx nx affected --target=test --base=origin/main --configuration=ci
+
+- name: Run affected build
+  run: npx nx affected --target=build --base=origin/main --configuration=production
+```
+
+## 12. Best Practices
+
+1. **Keep apps thin** - Business logic in libraries
+2. **Use affected** - Only build/test what changed
+3. **Leverage caching** - Let Nx cache task results
+4. **Consistent naming** - Follow naming conventions
+5. **Define boundaries** - Use tags and constraints
+6. **Path aliases** - Use `@scope/lib` imports