@heyai-rules/pilo-masterkit 2.1.0 → 3.1.0

package/.agent/skills/nutrient-document-processing/SKILL.md

@@ -1,167 +1,167 @@
----
-name: nutrient-document-processing
-description: Process, convert, OCR, extract, redact, sign, and fill documents using the Nutrient DWS API. Works with PDFs, DOCX, XLSX, PPTX, HTML, and images.
-origin: ECC
----
-
-# Nutrient Document Processing
-
-> **Note:** This skill integrates with the Nutrient commercial API. Review their terms before use.
-
-Process documents with the [Nutrient DWS Processor API](https://www.nutrient.io/api/). Convert formats, extract text and tables, OCR scanned documents, redact PII, add watermarks, digitally sign, and fill PDF forms.
-
-## Setup
-
-Get a free API key at **[nutrient.io](https://dashboard.nutrient.io/sign_up/?product=processor)**
-
-```bash
-export NUTRIENT_API_KEY="pdf_live_..."
-```
-
-All requests go to `https://api.nutrient.io/build` as multipart POST with an `instructions` JSON field.
-
-## Operations
-
-### Convert Documents
-
-```bash
-# DOCX to PDF
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "document.docx=@document.docx" \
-  -F 'instructions={"parts":[{"file":"document.docx"}]}' \
-  -o output.pdf
-
-# PDF to DOCX
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "document.pdf=@document.pdf" \
-  -F 'instructions={"parts":[{"file":"document.pdf"}],"output":{"type":"docx"}}' \
-  -o output.docx
-
-# HTML to PDF
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "index.html=@index.html" \
-  -F 'instructions={"parts":[{"html":"index.html"}]}' \
-  -o output.pdf
-```
-
-Supported inputs: PDF, DOCX, XLSX, PPTX, DOC, XLS, PPT, PPS, PPSX, ODT, RTF, HTML, JPG, PNG, TIFF, HEIC, GIF, WebP, SVG, TGA, EPS.
-
-### Extract Text and Data
-
-```bash
-# Extract plain text
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "document.pdf=@document.pdf" \
-  -F 'instructions={"parts":[{"file":"document.pdf"}],"output":{"type":"text"}}' \
-  -o output.txt
-
-# Extract tables as Excel
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "document.pdf=@document.pdf" \
-  -F 'instructions={"parts":[{"file":"document.pdf"}],"output":{"type":"xlsx"}}' \
-  -o tables.xlsx
-```
-
-### OCR Scanned Documents
-
-```bash
-# OCR to searchable PDF (supports 100+ languages)
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "scanned.pdf=@scanned.pdf" \
-  -F 'instructions={"parts":[{"file":"scanned.pdf"}],"actions":[{"type":"ocr","language":"english"}]}' \
-  -o searchable.pdf
-```
-
-Languages: Supports 100+ languages via ISO 639-2 codes (e.g., `eng`, `deu`, `fra`, `spa`, `jpn`, `kor`, `chi_sim`, `chi_tra`, `ara`, `hin`, `rus`). Full language names like `english` or `german` also work. See the [complete OCR language table](https://www.nutrient.io/guides/document-engine/ocr/language-support/) for all supported codes.
-
-### Redact Sensitive Information
-
-```bash
-# Pattern-based (SSN, email)
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "document.pdf=@document.pdf" \
-  -F 'instructions={"parts":[{"file":"document.pdf"}],"actions":[{"type":"redaction","strategy":"preset","strategyOptions":{"preset":"social-security-number"}},{"type":"redaction","strategy":"preset","strategyOptions":{"preset":"email-address"}}]}' \
-  -o redacted.pdf
-
-# Regex-based
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "document.pdf=@document.pdf" \
-  -F 'instructions={"parts":[{"file":"document.pdf"}],"actions":[{"type":"redaction","strategy":"regex","strategyOptions":{"regex":"\\b[A-Z]{2}\\d{6}\\b"}}]}' \
-  -o redacted.pdf
-```
-
-Presets: `social-security-number`, `email-address`, `credit-card-number`, `international-phone-number`, `north-american-phone-number`, `date`, `time`, `url`, `ipv4`, `ipv6`, `mac-address`, `us-zip-code`, `vin`.
-
-### Add Watermarks
-
-```bash
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "document.pdf=@document.pdf" \
-  -F 'instructions={"parts":[{"file":"document.pdf"}],"actions":[{"type":"watermark","text":"CONFIDENTIAL","fontSize":72,"opacity":0.3,"rotation":-45}]}' \
-  -o watermarked.pdf
-```
-
-### Digital Signatures
-
-```bash
-# Self-signed CMS signature
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "document.pdf=@document.pdf" \
-  -F 'instructions={"parts":[{"file":"document.pdf"}],"actions":[{"type":"sign","signatureType":"cms"}]}' \
-  -o signed.pdf
-```
-
-### Fill PDF Forms
-
-```bash
-curl -X POST https://api.nutrient.io/build \
-  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
-  -F "form.pdf=@form.pdf" \
-  -F 'instructions={"parts":[{"file":"form.pdf"}],"actions":[{"type":"fillForm","formFields":{"name":"Jane Smith","email":"jane@example.com","date":"2026-02-06"}}]}' \
-  -o filled.pdf
-```
-
-## MCP Server (Alternative)
-
-For native tool integration, use the MCP server instead of curl:
-
-```json
-{
-  "mcpServers": {
-    "nutrient-dws": {
-      "command": "npx",
-      "args": ["-y", "@nutrient-sdk/dws-mcp-server"],
-      "env": {
-        "NUTRIENT_DWS_API_KEY": "YOUR_API_KEY",
-        "SANDBOX_PATH": "/path/to/working/directory"
-      }
-    }
-  }
-}
-```
-
-## When to Use
-
-- Converting documents between formats (PDF, DOCX, XLSX, PPTX, HTML, images)
-- Extracting text, tables, or key-value pairs from PDFs
-- OCR on scanned documents or images
-- Redacting PII before sharing documents
-- Adding watermarks to drafts or confidential documents
-- Digitally signing contracts or agreements
-- Filling PDF forms programmatically
-
-## Links
-
-- [API Playground](https://dashboard.nutrient.io/processor-api/playground/)
-- [Full API Docs](https://www.nutrient.io/guides/dws-processor/)
-- [npm MCP Server](https://www.npmjs.com/package/@nutrient-sdk/dws-mcp-server)
+---
+name: nutrient-document-processing
+description: Process, convert, OCR, extract, redact, sign, and fill documents using the Nutrient DWS API. Works with PDFs, DOCX, XLSX, PPTX, HTML, and images.
+origin: ECC
+---
+
+# Nutrient Document Processing
+
+> **Note:** This skill integrates with the Nutrient commercial API. Review their terms before use.
+
+Process documents with the [Nutrient DWS Processor API](https://www.nutrient.io/api/). Convert formats, extract text and tables, OCR scanned documents, redact PII, add watermarks, digitally sign, and fill PDF forms.
+
+## Setup
+
+Get a free API key at **[nutrient.io](https://dashboard.nutrient.io/sign_up/?product=processor)**
+
+```bash
+export NUTRIENT_API_KEY="pdf_live_..."
+```
+
+All requests go to `https://api.nutrient.io/build` as multipart POST with an `instructions` JSON field.
+
+## Operations
+
+### Convert Documents
+
+```bash
+# DOCX to PDF
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "document.docx=@document.docx" \
+  -F 'instructions={"parts":[{"file":"document.docx"}]}' \
+  -o output.pdf
+
+# PDF to DOCX
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "document.pdf=@document.pdf" \
+  -F 'instructions={"parts":[{"file":"document.pdf"}],"output":{"type":"docx"}}' \
+  -o output.docx
+
+# HTML to PDF
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "index.html=@index.html" \
+  -F 'instructions={"parts":[{"html":"index.html"}]}' \
+  -o output.pdf
+```
+
+Supported inputs: PDF, DOCX, XLSX, PPTX, DOC, XLS, PPT, PPS, PPSX, ODT, RTF, HTML, JPG, PNG, TIFF, HEIC, GIF, WebP, SVG, TGA, EPS.
+
+### Extract Text and Data
+
+```bash
+# Extract plain text
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "document.pdf=@document.pdf" \
+  -F 'instructions={"parts":[{"file":"document.pdf"}],"output":{"type":"text"}}' \
+  -o output.txt
+
+# Extract tables as Excel
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "document.pdf=@document.pdf" \
+  -F 'instructions={"parts":[{"file":"document.pdf"}],"output":{"type":"xlsx"}}' \
+  -o tables.xlsx
+```
+
+### OCR Scanned Documents
+
+```bash
+# OCR to searchable PDF (supports 100+ languages)
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "scanned.pdf=@scanned.pdf" \
+  -F 'instructions={"parts":[{"file":"scanned.pdf"}],"actions":[{"type":"ocr","language":"english"}]}' \
+  -o searchable.pdf
+```
+
+Languages: Supports 100+ languages via ISO 639-2 codes (e.g., `eng`, `deu`, `fra`, `spa`, `jpn`, `kor`, `chi_sim`, `chi_tra`, `ara`, `hin`, `rus`). Full language names like `english` or `german` also work. See the [complete OCR language table](https://www.nutrient.io/guides/document-engine/ocr/language-support/) for all supported codes.
+
+### Redact Sensitive Information
+
+```bash
+# Pattern-based (SSN, email)
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "document.pdf=@document.pdf" \
+  -F 'instructions={"parts":[{"file":"document.pdf"}],"actions":[{"type":"redaction","strategy":"preset","strategyOptions":{"preset":"social-security-number"}},{"type":"redaction","strategy":"preset","strategyOptions":{"preset":"email-address"}}]}' \
+  -o redacted.pdf
+
+# Regex-based
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "document.pdf=@document.pdf" \
+  -F 'instructions={"parts":[{"file":"document.pdf"}],"actions":[{"type":"redaction","strategy":"regex","strategyOptions":{"regex":"\\b[A-Z]{2}\\d{6}\\b"}}]}' \
+  -o redacted.pdf
+```
+
+Presets: `social-security-number`, `email-address`, `credit-card-number`, `international-phone-number`, `north-american-phone-number`, `date`, `time`, `url`, `ipv4`, `ipv6`, `mac-address`, `us-zip-code`, `vin`.
+
+### Add Watermarks
+
+```bash
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "document.pdf=@document.pdf" \
+  -F 'instructions={"parts":[{"file":"document.pdf"}],"actions":[{"type":"watermark","text":"CONFIDENTIAL","fontSize":72,"opacity":0.3,"rotation":-45}]}' \
+  -o watermarked.pdf
+```
+
+### Digital Signatures
+
+```bash
+# Self-signed CMS signature
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "document.pdf=@document.pdf" \
+  -F 'instructions={"parts":[{"file":"document.pdf"}],"actions":[{"type":"sign","signatureType":"cms"}]}' \
+  -o signed.pdf
+```
+
+### Fill PDF Forms
+
+```bash
+curl -X POST https://api.nutrient.io/build \
+  -H "Authorization: Bearer $NUTRIENT_API_KEY" \
+  -F "form.pdf=@form.pdf" \
+  -F 'instructions={"parts":[{"file":"form.pdf"}],"actions":[{"type":"fillForm","formFields":{"name":"Jane Smith","email":"jane@example.com","date":"2026-02-06"}}]}' \
+  -o filled.pdf
+```
+
+## MCP Server (Alternative)
+
+For native tool integration, use the MCP server instead of curl:
+
+```json
+{
+  "mcpServers": {
+    "nutrient-dws": {
+      "command": "npx",
+      "args": ["-y", "@nutrient-sdk/dws-mcp-server"],
+      "env": {
+        "NUTRIENT_DWS_API_KEY": "YOUR_API_KEY",
+        "SANDBOX_PATH": "/path/to/working/directory"
+      }
+    }
+  }
+}
+```
+
+## When to Use
+
+- Converting documents between formats (PDF, DOCX, XLSX, PPTX, HTML, images)
+- Extracting text, tables, or key-value pairs from PDFs
+- OCR on scanned documents or images
+- Redacting PII before sharing documents
+- Adding watermarks to drafts or confidential documents
+- Digitally signing contracts or agreements
+- Filling PDF forms programmatically
+
+## Links
+
+- [API Playground](https://dashboard.nutrient.io/processor-api/playground/)
+- [Full API Docs](https://www.nutrient.io/guides/dws-processor/)
+- [npm MCP Server](https://www.npmjs.com/package/@nutrient-sdk/dws-mcp-server)

package/.agent/skills/nuxt4-patterns/SKILL.md

@@ -1,100 +1,100 @@
----
-name: nuxt4-patterns
-description: Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
-origin: ECC
----
-
-# Nuxt 4 Patterns
-
-Use when building or debugging Nuxt 4 apps with SSR, hybrid rendering, route rules, or page-level data fetching.
-
-## When to Activate
-
-- Hydration mismatches between server HTML and client state
-- Route-level rendering decisions such as prerender, SWR, ISR, or client-only sections
-- Performance work around lazy loading, lazy hydration, or payload size
-- Page or component data fetching with `useFetch`, `useAsyncData`, or `$fetch`
-- Nuxt routing issues tied to route params, middleware, or SSR/client differences
-
-## Hydration Safety
-
-- Keep the first render deterministic. Do not put `Date.now()`, `Math.random()`, browser-only APIs, or storage reads directly into SSR-rendered template state.
-- Move browser-only logic behind `onMounted()`, `import.meta.client`, `ClientOnly`, or a `.client.vue` component when the server cannot produce the same markup.
-- Use Nuxt's `useRoute()` composable, not the one from `vue-router`.
-- Do not use `route.fullPath` to drive SSR-rendered markup. URL fragments are client-only, which can create hydration mismatches.
-- Treat `ssr: false` as an escape hatch for truly browser-only areas, not a default fix for mismatches.
-
-## Data Fetching
-
-- Prefer `await useFetch()` for SSR-safe API reads in pages and components. It forwards server-fetched data into the Nuxt payload and avoids a second fetch on hydration.
-- Use `useAsyncData()` when the fetcher is not a simple `$fetch()` call, when you need a custom key, or when you are composing multiple async sources.
-- Give `useAsyncData()` a stable key for cache reuse and predictable refresh behavior.
-- Keep `useAsyncData()` handlers side-effect free. They can run during SSR and hydration.
-- Use `$fetch()` for user-triggered writes or client-only actions, not top-level page data that should be hydrated from SSR.
-- Use `lazy: true`, `useLazyFetch()`, or `useLazyAsyncData()` for non-critical data that should not block navigation. Handle `status === 'pending'` in the UI.
-- Use `server: false` only for data that is not needed for SEO or the first paint.
-- Trim payload size with `pick` and prefer shallower payloads when deep reactivity is unnecessary.
-
-```ts
-const route = useRoute()
-
-const { data: article, status, error, refresh } = await useAsyncData(
-  () => `article:${route.params.slug}`,
-  () => $fetch(`/api/articles/${route.params.slug}`),
-)
-
-const { data: comments } = await useFetch(`/api/articles/${route.params.slug}/comments`, {
-  lazy: true,
-  server: false,
-})
-```
-
-## Route Rules
-
-Prefer `routeRules` in `nuxt.config.ts` for rendering and caching strategy:
-
-```ts
-export default defineNuxtConfig({
-  routeRules: {
-    '/': { prerender: true },
-    '/products/**': { swr: 3600 },
-    '/blog/**': { isr: true },
-    '/admin/**': { ssr: false },
-    '/api/**': { cache: { maxAge: 60 * 60 } },
-  },
-})
-```
-
-- `prerender`: static HTML at build time
-- `swr`: serve cached content and revalidate in the background
-- `isr`: incremental static regeneration on supported platforms
-- `ssr: false`: client-rendered route
-- `cache` or `redirect`: Nitro-level response behavior
-
-Pick route rules per route group, not globally. Marketing pages, catalogs, dashboards, and APIs usually need different strategies.
-
-## Lazy Loading and Performance
-
-- Nuxt already code-splits pages by route. Keep route boundaries meaningful before micro-optimizing component splits.
-- Use the `Lazy` prefix to dynamically import non-critical components.
-- Conditionally render lazy components with `v-if` so the chunk is not loaded until the UI actually needs it.
-- Use lazy hydration for below-the-fold or non-critical interactive UI.
-
-```vue
-<template>
-  <LazyRecommendations v-if="showRecommendations" />
-  <LazyProductGallery hydrate-on-visible />
-</template>
-```
-
-- For custom strategies, use `defineLazyHydrationComponent()` with a visibility or idle strategy.
-- Nuxt lazy hydration works on single-file components. Passing new props to a lazily hydrated component will trigger hydration immediately.
-- Use `NuxtLink` for internal navigation so Nuxt can prefetch route components and generated payloads.
-
-## Review Checklist
-
-- First SSR render and hydrated client render produce the same markup
-- Page data uses `useFetch` or `useAsyncData`, not top-level `$fetch`
-- Non-critical data is lazy and has explicit loading UI
-- Route rules match the page's SEO and freshness requirements
-- Heavy interactive islands are lazy-loaded or lazily hydrated
+---
+name: nuxt4-patterns
+description: Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
+origin: ECC
+---
+
+# Nuxt 4 Patterns
+
+Use when building or debugging Nuxt 4 apps with SSR, hybrid rendering, route rules, or page-level data fetching.
+
+## When to Activate
+
+- Hydration mismatches between server HTML and client state
+- Route-level rendering decisions such as prerender, SWR, ISR, or client-only sections
+- Performance work around lazy loading, lazy hydration, or payload size
+- Page or component data fetching with `useFetch`, `useAsyncData`, or `$fetch`
+- Nuxt routing issues tied to route params, middleware, or SSR/client differences
+
+## Hydration Safety
+
+- Keep the first render deterministic. Do not put `Date.now()`, `Math.random()`, browser-only APIs, or storage reads directly into SSR-rendered template state.
+- Move browser-only logic behind `onMounted()`, `import.meta.client`, `ClientOnly`, or a `.client.vue` component when the server cannot produce the same markup.
+- Use Nuxt's `useRoute()` composable, not the one from `vue-router`.
+- Do not use `route.fullPath` to drive SSR-rendered markup. URL fragments are client-only, which can create hydration mismatches.
+- Treat `ssr: false` as an escape hatch for truly browser-only areas, not a default fix for mismatches.
+
+## Data Fetching
+
+- Prefer `await useFetch()` for SSR-safe API reads in pages and components. It forwards server-fetched data into the Nuxt payload and avoids a second fetch on hydration.
+- Use `useAsyncData()` when the fetcher is not a simple `$fetch()` call, when you need a custom key, or when you are composing multiple async sources.
+- Give `useAsyncData()` a stable key for cache reuse and predictable refresh behavior.
+- Keep `useAsyncData()` handlers side-effect free. They can run during SSR and hydration.
+- Use `$fetch()` for user-triggered writes or client-only actions, not top-level page data that should be hydrated from SSR.
+- Use `lazy: true`, `useLazyFetch()`, or `useLazyAsyncData()` for non-critical data that should not block navigation. Handle `status === 'pending'` in the UI.
+- Use `server: false` only for data that is not needed for SEO or the first paint.
+- Trim payload size with `pick` and prefer shallower payloads when deep reactivity is unnecessary.
+
+```ts
+const route = useRoute()
+
+const { data: article, status, error, refresh } = await useAsyncData(
+  () => `article:${route.params.slug}`,
+  () => $fetch(`/api/articles/${route.params.slug}`),
+)
+
+const { data: comments } = await useFetch(`/api/articles/${route.params.slug}/comments`, {
+  lazy: true,
+  server: false,
+})
+```
+
+## Route Rules
+
+Prefer `routeRules` in `nuxt.config.ts` for rendering and caching strategy:
+
+```ts
+export default defineNuxtConfig({
+  routeRules: {
+    '/': { prerender: true },
+    '/products/**': { swr: 3600 },
+    '/blog/**': { isr: true },
+    '/admin/**': { ssr: false },
+    '/api/**': { cache: { maxAge: 60 * 60 } },
+  },
+})
+```
+
+- `prerender`: static HTML at build time
+- `swr`: serve cached content and revalidate in the background
+- `isr`: incremental static regeneration on supported platforms
+- `ssr: false`: client-rendered route
+- `cache` or `redirect`: Nitro-level response behavior
+
+Pick route rules per route group, not globally. Marketing pages, catalogs, dashboards, and APIs usually need different strategies.
+
+## Lazy Loading and Performance
+
+- Nuxt already code-splits pages by route. Keep route boundaries meaningful before micro-optimizing component splits.
+- Use the `Lazy` prefix to dynamically import non-critical components.
+- Conditionally render lazy components with `v-if` so the chunk is not loaded until the UI actually needs it.
+- Use lazy hydration for below-the-fold or non-critical interactive UI.
+
+```vue
+<template>
+  <LazyRecommendations v-if="showRecommendations" />
+  <LazyProductGallery hydrate-on-visible />
+</template>
+```
+
+- For custom strategies, use `defineLazyHydrationComponent()` with a visibility or idle strategy.
+- Nuxt lazy hydration works on single-file components. Passing new props to a lazily hydrated component will trigger hydration immediately.
+- Use `NuxtLink` for internal navigation so Nuxt can prefetch route components and generated payloads.
+
+## Review Checklist
+
+- First SSR render and hydrated client render produce the same markup
+- Page data uses `useFetch` or `useAsyncData`, not top-level `$fetch`
+- Non-critical data is lazy and has explicit loading UI
+- Route rules match the page's SEO and freshness requirements
+- Heavy interactive islands are lazy-loaded or lazily hydrated