blun-king-cli 9.1.62 → 9.1.63

package/standard-skills/screenshot-lesen/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: screenshot-lesen
+description: "Bilder und Screenshots inhaltlich auslesen (OCR und UI-Struktur), obwohl das Modell selbst keine Bilder sieht. Mandatory triggers: eine Telegram-Nachricht enthaelt image_path oder attachment mit Bild, 'was steht auf dem Bild', 'lies den Screenshot', 'schau dir das Bild an', 'analysiere das Foto'. Der Skill liefert das Kommando-Rezept: EasyOCR zuerst (installiert), Tesseract als Fallback, OmniParser fuer UI-Element-Struktur."
+---
+
+# Screenshot lesen
+
+Du kannst Bilder NICHT direkt sehen — aber du kannst sie mit lokalen
+Werkzeugen in Text verwandeln und dann inhaltlich beantworten. Behaupte nie,
+ein Bild gelesen zu haben, ohne eines dieser Werkzeuge wirklich ausgefuehrt
+zu haben.
+
+## Weg 1 (Standard): EasyOCR — liest allen Text im Bild
+
+```bash
+python -c "import easyocr; r = easyocr.Reader(['de','en'], verbose=False); print('\n'.join(x[1] for x in r.readtext(r'BILDPFAD')))"
+```
+
+- BILDPFAD = der `image_path` aus der Telegram-Nachricht (oder der Pfad einer
+  per download_attachment geholten Datei).
+- Erster Lauf laedt Modelle (dauert kurz), danach schnell.
+- Ergebnis: der Text im Bild, Zeile fuer Zeile. Fasse ihn sinnvoll zusammen,
+  zitiere die relevanten Stellen.
+
+## Weg 2 (Fallback): Tesseract
+
+Wenn EasyOCR fehlt oder haengt:
+
+```bash
+"C:\Program Files\Tesseract-OCR\tesseract.exe" BILDPFAD stdout -l eng
+```
+
+Fuer Deutsch: `deu.traineddata` von
+https://github.com/tesseract-ocr/tessdata_fast/raw/main/deu.traineddata in
+einen eigenen Ordner laden, `TESSDATA_PREFIX` auf dessen ELTERN-Ordner setzen
+(der Ordner selbst muss `tessdata` heissen), dann `-l deu+eng`.
+
+## Weg 3 (UI-Struktur): OmniParser
+
+Wenn nicht nur TEXT gefragt ist, sondern WAS auf einer Oberflaeche ist
+(Buttons, Felder, Layout): OmniParser-Repo (microsoft/OmniParser, lokal
+geklont) nutzen — erkennt UI-Elemente mit Positionen. Schwergewichtig;
+nur verwenden, wenn die Frage wirklich UI-Struktur oder Bedienbarkeit
+betrifft, sonst reicht Weg 1.
+
+## Regeln
+
+- Immer ehrlich sagen, WOMIT du gelesen hast (z.B. "per OCR gelesen").
+- OCR kann sich verlesen — bei kritischen Werten (Zahlen, Codes, Namen)
+  dazusagen, dass es OCR ist und Unsicherheit moeglich ist.
+- Niemals Secrets aus Bildern im Klartext wiedergeben — Fundort und Art
+  nennen, Werte maskieren.

package/standard-skills/stitch-design-taste/DESIGN.md

@@ -0,0 +1,121 @@
+# Design System: Taste Standard
+**Skill:** stitch-design-taste
+
+---
+
+## Configuration — Set Your Style
+Adjust these dials before using this design system. They control how creative, dense, and animated the output should be. Pick the level that fits your project.
+
+| Dial | Level | Description |
+|------|-------|-------------|
+| **Creativity** | `8` | `1` = Ultra-minimal, Swiss, silent, monochrome. `5` = Balanced, clean but with personality. `10` = Expressive, editorial, bold typography experiments, inline images in headlines, strong asymmetry. Default: `8` |
+| **Density** | `4` | `1` = Gallery-airy, massive whitespace. `5` = Balanced sections. `10` = Cockpit-dense, data-heavy. Default: `4` |
+| **Variance** | `8` | `1` = Predictable, symmetric grids. `5` = Subtle offsets. `10` = Artsy chaotic, no two sections alike. Default: `8` |
+| **Motion Intent** | `6` | `1` = Static, no animation noted. `5` = Subtle hover/entrance cues. `10` = Cinematic orchestration noted in every component. Default: `6` |
+
+> **How to use:** Change the numbers above to match your project's vibe. At **Creativity 1–3**, the system produces clean, quiet, Notion-like interfaces. At **Creativity 7–10**, expect inline image typography, dramatic scale contrast, and strong editorial layouts. The rest of the rules below adapt to your chosen levels.
+
+---
+
+## 1. Visual Theme & Atmosphere
+A restrained, gallery-airy interface with confident asymmetric layouts and fluid spring-physics motion. The atmosphere is clinical yet warm — like a well-lit architecture studio where every element earns its place through function. Density is balanced (Level 4), variance runs high (Level 8) to prevent symmetrical boredom, and motion is fluid but never theatrical (Level 6). The overall impression: expensive, intentional, alive.
+
+## 2. Color Palette & Roles
+- **Canvas White** (#F9FAFB) — Primary background surface. Warm-neutral, never clinical blue-white
+- **Pure Surface** (#FFFFFF) — Card and container fill. Used with whisper shadow for elevation
+- **Charcoal Ink** (#18181B) — Primary text. Zinc-950 depth — never pure black
+- **Steel Secondary** (#71717A) — Body text, descriptions, metadata. Zinc-500 warmth
+- **Muted Slate** (#94A3B8) — Tertiary text, timestamps, disabled states
+- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, structural 1px lines. Semi-transparent for depth
+- **Diffused Shadow** (rgba(0,0,0,0.05)) — Card elevation. Wide-spreading, 40px blur, -15px offset. Never harsh
+
+### Accent Selection (Pick ONE per project)
+- **Emerald Signal** (#10B981) — For growth, success, positive data dashboards
+- **Electric Blue** (#3B82F6) — For productivity, SaaS, developer tools
+- **Deep Rose** (#E11D48) — For creative, editorial, fashion-adjacent projects
+- **Amber Warmth** (#F59E0B) — For community, social, warm-toned products
+
+### Banned Colors
+- Purple/Violet neon gradients — the "AI Purple" aesthetic
+- Pure Black (#000000) — always Off-Black or Zinc-950
+- Oversaturated accents above 80% saturation
+- Mixed warm/cool gray systems within one project
+
+## 3. Typography Rules
+- **Display:** `Geist`, `Satoshi`, `Cabinet Grotesk`, or `Outfit` — Track-tight (`-0.025em`), controlled fluid scale, weight-driven hierarchy (700–900). Not screaming. Leading compressed (`1.1`). Alternatives forced — `Inter` is BANNED for premium contexts
+- **Body:** Same family at weight 400 — Relaxed leading (`1.65`), 65ch max-width, Steel Secondary color (#71717A)
+- **Mono:** `Geist Mono` or `JetBrains Mono` — For code blocks, metadata, timestamps. When density exceeds Level 7, all numbers switch to monospace
+- **Scale:** Display at `clamp(2.25rem, 5vw, 3.75rem)`. Body at `1rem/1.125rem`. Mono metadata at `0.8125rem`
+
+### Banned Fonts
+- `Inter` — banned everywhere in premium/creative contexts
+- Generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`, `Palatino`) — BANNED. If serif is needed for editorial/creative, use only distinctive modern serifs like `Fraunces`, `Gambarino`, `Editorial New`, or `Instrument Serif`. Never use default browser serif stacks. Serif is always BANNED in dashboards or software UIs regardless
+
+## 4. Component Stylings
+* **Buttons:** Flat surface, no outer glow. Primary: accent fill with white text. Secondary: ghost/outline. Active state: `-1px translateY` or `scale(0.98)` for tactile push. Hover: subtle background shift, never glow
+* **Cards/Containers:** Generously rounded corners (`2.5rem`). Pure white fill. Whisper border (`1px`, semi-transparent). Diffused shadow (`0 20px 40px -15px rgba(0,0,0,0.05)`). Internal padding `2rem–2.5rem`. Used ONLY when elevation communicates hierarchy — high-density layouts replace cards with `border-top` dividers or negative space
+* **Inputs/Forms:** Label positioned above input. Helper text optional. Error text below in Deep Rose. Focus ring in accent color, `2px` offset. No floating labels. Standard `0.5rem` gap between label-input-error stack
+* **Navigation:** Sleek, sticky. Icons scale on hover (Dock Magnification optional). No hamburger on desktop. Clean horizontal with generous spacing
+* **Loaders:** Skeletal shimmer matching exact layout dimensions and rounded corners. Shifting light reflection across placeholder shapes. Never circular spinners
+* **Empty States:** Composed illustration or icon composition with guidance text. Never just "No data found"
+* **Error States:** Inline, contextual. Red accent underline or border. Clear recovery action
+
+## 5. Hero Section
+The Hero is the first impression — it must be striking, creative, and never generic.
+- **Inline Image Typography:** Embed small, contextual photos or visuals directly between words or letters in the headline. Example: "We build [photo of hands typing] digital [photo of screen] products" — images sit inline at type-height, rounded, acting as visual punctuation between words. This is the signature creative technique
+- **No Overlapping Elements:** Text must never overlap images or other text. Every element has its own clear spatial zone. No z-index stacking of content layers, no absolute-positioned headlines over images. Clean separation always
+- **No Filler Text:** "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons, and any instructional UI chrome are BANNED. The user knows how to scroll. Let the content pull them in naturally
+- **Asymmetric Structure:** Centered Hero layouts are BANNED at this variance level. Use Split Screen (50/50), Left-Aligned text / Right visual, or Asymmetric Whitespace with large empty zones
+- **CTA Restraint:** Maximum one primary CTA button. No secondary "Learn more" links. No redundant micro-copy below the headline
+
+## 6. Layout Principles
+- **Grid-First:** CSS Grid for all structural layouts. Never flexbox percentage math (`calc(33% - 1rem)` is BANNED)
+- **No Overlapping:** Elements must never overlap each other. No absolute-positioned layers stacking content on content. Every element occupies its own grid cell or flow position. Clean, separated spatial zones
+- **Feature Sections:** The "3 equal cards in a row" pattern is BANNED. Use 2-column Zig-Zag, asymmetric Bento grids (2fr 1fr 1fr), or horizontal scroll galleries
+- **Containment:** All content within `max-width: 1400px`, centered. Generous horizontal padding (`1rem` mobile, `2rem` tablet, `4rem` desktop)
+- **Full-Height:** Use `min-height: 100dvh` — never `height: 100vh` (iOS Safari address bar jump)
+- **Bento Architecture:** For feature grids, use Row 1: 3 columns | Row 2: 2 columns (70/30 split). Each tile contains a perpetual micro-animation
+
+## 7. Responsive Rules
+Every screen must work flawlessly across all viewports. **Responsive is not optional — it is a hard requirement. Every single element must be tested at 375px, 768px, and 1440px.**
+- **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to a strict single column. `width: 100%`, `padding: 1rem`, `gap: 1.5rem`. No exceptions
+- **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure. All elements must fit within viewport width. If any element causes horizontal scroll, the design is broken
+- **Typography Scaling:** Headlines scale down gracefully via `clamp()`. Body text stays `1rem` minimum. Never shrink body below `14px`. Headlines must remain readable on 375px screens
+- **Touch Targets:** All interactive elements minimum `44px` tap target. Generous spacing between clickable items. Buttons must be full-width on mobile
+- **Image Behavior:** Hero and inline images scale proportionally. Inline typography images (photos between words) stack below the headline on mobile instead of inline
+- **Navigation:** Desktop horizontal nav collapses to a clean mobile menu (slide-in or full-screen overlay). No tiny hamburger icons without labels
+- **Cards & Grids:** Bento grids and asymmetric layouts revert to stacked single-column cards with full-width. Maintain internal padding (`1rem`)
+- **Spacing Consistency:** Vertical section gaps reduce proportionally on mobile (`clamp(3rem, 8vw, 6rem)`). Never cramped, never excessively airy
+- **Testing Viewports:** Designs must be verified at: `375px` (iPhone SE), `390px` (iPhone 14), `768px` (iPad), `1024px` (small laptop), `1440px` (desktop)
+
+## 8. Motion & Interaction (Code-Phase Intent)
+> **Note:** Stitch generates static screens — it does not animate. This section documents the **intended motion behavior** so that the coding agent (Antigravity, Cursor, etc.) knows exactly how to implement animations when building the exported design into a live product.
+
+- **Physics Engine:** Spring-based exclusively. `stiffness: 100, damping: 20`. No linear easing anywhere. Premium, weighty feel on all interactive elements
+- **Perpetual Micro-Loops:** Every active dashboard component has an infinite-loop state — Pulse on status dots, Typewriter on search bars, Float on feature icons, Shimmer on loading states
+- **Staggered Orchestration:** Lists and grids mount with cascaded delays (`animation-delay: calc(var(--index) * 100ms)`). Waterfall reveals, never instant mount
+- **Layout Transitions:** Smooth re-ordering via shared element IDs. Items swap positions with physics, simulating real-time intelligence
+- **Hardware Rules:** Animate ONLY `transform` and `opacity`. Never `top`, `left`, `width`, `height`. Grain/noise filters on fixed, pointer-events-none pseudo-elements only
+- **Performance:** CPU-heavy perpetual animations isolated in microscopic leaf components. Never trigger parent re-renders. Target 60fps minimum
+
+## 9. Anti-Patterns (Banned)
+- No emojis — anywhere in UI, code, or alt text
+- No `Inter` font — use `Geist`, `Outfit`, `Cabinet Grotesk`, `Satoshi`
+- No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — if serif is needed, use distinctive modern serifs only (`Fraunces`, `Instrument Serif`)
+- No pure black (`#000000`) — Off-Black or Zinc-950 only
+- No neon outer glows or default box-shadow glows
+- No oversaturated accent colors above 80%
+- No excessive gradient text on large headers
+- No custom mouse cursors
+- No overlapping elements — text never overlaps images or other content. Clean spatial separation always
+- No 3-column equal card layouts for features
+- No centered Hero sections (at this variance level)
+- No filler UI text: "Scroll to explore", "Swipe down", "Discover more below", scroll arrows, bouncing chevrons — all BANNED
+- No generic names: "John Doe", "Sarah Chan", "Acme", "Nexus", "SmartFlow"
+- No fake round numbers: `99.99%`, `50%`, `1234567` — use organic data: `47.2%`, `+1 (312) 847-1928`
+- No AI copywriting clichés: "Elevate", "Seamless", "Unleash", "Next-Gen", "Revolutionize"
+- No broken Unsplash links — use `picsum.photos/seed/{id}/800/600` or SVG UI Avatars
+- No generic `shadcn/ui` defaults — customize radii, colors, shadows to match this system
+- No `z-index` spam — use only for Navbar, Modal, Overlay layer contexts
+- No `h-screen` — always `min-h-[100dvh]`
+- No circular loading spinners — skeletal shimmer only

package/standard-skills/stitch-design-taste/SKILL.md

@@ -0,0 +1,184 @@
+---
+name: stitch-design-taste
+description: Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
+---
+
+# Stitch Design Taste — Semantic Design System Skill
+
+## Overview
+This skill generates `DESIGN.md` files optimized for Google Stitch screen generation. It translates the battle-tested anti-slop frontend engineering directives into Stitch's native semantic design language — descriptive, natural-language rules paired with precise values that Stitch's AI agent can interpret to produce premium, non-generic interfaces.
+
+The generated `DESIGN.md` serves as the **single source of truth** for prompting Stitch to generate new screens that align with a curated, high-agency design language. Stitch interprets design through **"Visual Descriptions"** supported by specific color values, typography specs, and component behaviors.
+
+## Prerequisites
+- Access to Google Stitch via [labs.google/stitch](https://labs.google/stitch)
+- Optionally: Stitch MCP Server for programmatic integration with a compatible CLI
+
+## The Goal
+Generate a `DESIGN.md` file that encodes:
+1. **Visual atmosphere** — the mood, density, and design philosophy
+2. **Color calibration** — neutrals, accents, and banned patterns with hex codes
+3. **Typographic architecture** — font stacks, scale hierarchy, and anti-patterns
+4. **Component behaviors** — buttons, cards, inputs with interaction states
+5. **Layout principles** — grid systems, spacing philosophy, responsive strategy
+6. **Motion philosophy** — animation engine specs, spring physics, perpetual micro-interactions
+7. **Anti-patterns** — explicit list of banned AI design clichés
+
+## Analysis & Synthesis Instructions
+
+### 1. Define the Atmosphere
+Evaluate the target project's intent. Use evocative adjectives from the taste spectrum:
+- **Density:** "Art Gallery Airy" (1–3) → "Daily App Balanced" (4–7) → "Cockpit Dense" (8–10)
+- **Variance:** "Predictable Symmetric" (1–3) → "Offset Asymmetric" (4–7) → "Artsy Chaotic" (8–10)
+- **Motion:** "Static Restrained" (1–3) → "Fluid CSS" (4–7) → "Cinematic Choreography" (8–10)
+
+Default baseline: Variance 8, Motion 6, Density 4. Adapt dynamically based on user's vibe description.
+
+### 2. Map the Color Palette
+For each color provide: **Descriptive Name** + **Hex Code** + **Functional Role**.
+
+**Mandatory constraints:**
+- Maximum 1 accent color. Saturation below 80%
+- The "AI Purple/Blue Neon" aesthetic is strictly BANNED — no purple button glows, no neon gradients
+- Use absolute neutral bases (Zinc/Slate) with high-contrast singular accents
+- Stick to one palette for the entire output — no warm/cool gray fluctuation
+- Never use pure black (`#000000`) — use Off-Black, Zinc-950, or Charcoal
+
+### 3. Establish Typography Rules
+- **Display/Headlines:** Track-tight, controlled scale. Not screaming. Hierarchy through weight and color, not just massive size
+- **Body:** Relaxed leading, max 65 characters per line
+- **Font Selection:** `Inter` is BANNED for premium/creative contexts. Force unique character: `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`
+- **Serif Ban:** Generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`, `Palatino`) are BANNED. If serif is needed for editorial/creative contexts, use only distinctive modern serifs: `Fraunces`, `Gambarino`, `Editorial New`, or `Instrument Serif`. Serif is always BANNED in dashboards or software UIs
+- **Dashboard Constraint:** Use Sans-Serif pairings exclusively (`Geist` + `Geist Mono` or `Satoshi` + `JetBrains Mono`)
+- **High-Density Override:** When density exceeds 7, all numbers must use Monospace
+
+### 4. Define the Hero Section
+The Hero is the first impression and must be creative, striking, and never generic:
+- **Inline Image Typography:** Embed small, contextual photos or visuals directly between words or letters in the headline. Images sit inline at type-height, rounded, acting as visual punctuation. This is the signature creative technique
+- **No Overlapping:** Text must never overlap images or other text. Every element occupies its own clean spatial zone
+- **No Filler Text:** "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons are BANNED. The content should pull users in naturally
+- **Asymmetric Structure:** Centered Hero layouts BANNED when variance exceeds 4
+- **CTA Restraint:** Maximum one primary CTA. No secondary "Learn more" links
+
+### 5. Describe Component Stylings
+For each component type, describe shape, color, shadow depth, and interaction behavior:
+- **Buttons:** Tactile push feedback on active state. No neon outer glows. No custom mouse cursors
+- **Cards:** Use ONLY when elevation communicates hierarchy. Tint shadows to background hue. For high-density layouts, replace cards with border-top dividers or negative space
+- **Inputs/Forms:** Label above input, helper text optional, error text below. Standard gap spacing
+- **Loading States:** Skeletal loaders matching layout dimensions — no generic circular spinners
+- **Empty States:** Composed compositions indicating how to populate data
+- **Error States:** Clear, inline error reporting
+
+### 6. Define Layout Principles
+- No overlapping elements — every element occupies its own clear spatial zone. No absolute-positioned content stacking
+- Centered Hero sections are BANNED when variance exceeds 4 — force Split Screen, Left-Aligned, or Asymmetric Whitespace
+- The generic "3 equal cards horizontally" feature row is BANNED — use 2-column Zig-Zag, asymmetric grid, or horizontal scroll
+- CSS Grid over Flexbox math — never use `calc()` percentage hacks
+- Contain layouts using max-width constraints (e.g., 1400px centered)
+- Full-height sections must use `min-h-[100dvh]` — never `h-screen` (iOS Safari catastrophic jump)
+
+### 7. Define Responsive Rules
+Every design must work across all viewports:
+- **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to single column. No exceptions
+- **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure
+- **Typography Scaling:** Headlines scale via `clamp()`. Body text minimum `1rem`/`14px`
+- **Touch Targets:** All interactive elements minimum `44px` tap target
+- **Image Behavior:** Inline typography images (photos between words) stack below headline on mobile
+- **Navigation:** Desktop horizontal nav collapses to clean mobile menu
+- **Spacing:** Vertical section gaps reduce proportionally (`clamp(3rem, 8vw, 6rem)`)
+
+### 8. Encode Motion Philosophy
+- **Spring Physics default:** `stiffness: 100, damping: 20` — premium, weighty feel. No linear easing
+- **Perpetual Micro-Interactions:** Every active component should have an infinite loop state (Pulse, Typewriter, Float, Shimmer)
+- **Staggered Orchestration:** Never mount lists instantly — use cascade delays for waterfall reveals
+- **Performance:** Animate exclusively via `transform` and `opacity`. Never animate `top`, `left`, `width`, `height`. Grain/noise filters on fixed pseudo-elements only
+
+### 9. List Anti-Patterns (AI Tells)
+Encode these as explicit "NEVER DO" rules in the DESIGN.md:
+- No emojis anywhere
+- No `Inter` font
+- No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — distinctive modern serifs only if needed
+- No pure black (`#000000`)
+- No neon/outer glow shadows
+- No oversaturated accents
+- No excessive gradient text on large headers
+- No custom mouse cursors
+- No overlapping elements — clean spatial separation always
+- No 3-column equal card layouts
+- No generic names ("John Doe", "Acme", "Nexus")
+- No fake round numbers (`99.99%`, `50%`)
+- No AI copywriting clichés ("Elevate", "Seamless", "Unleash", "Next-Gen")
+- No filler UI text: "Scroll to explore", "Swipe down", scroll arrows, bouncing chevrons
+- No broken Unsplash links — use `picsum.photos` or SVG avatars
+- No centered Hero sections (for high-variance projects)
+
+## Output Format (DESIGN.md Structure)
+
+```markdown
+# Design System: [Project Title]
+
+## 1. Visual Theme & Atmosphere
+(Evocative description of the mood, density, variance, and motion intensity.
+Example: "A restrained, gallery-airy interface with confident asymmetric layouts
+and fluid spring-physics motion. The atmosphere is clinical yet warm — like a
+well-lit architecture studio.")
+
+## 2. Color Palette & Roles
+- **Canvas White** (#F9FAFB) — Primary background surface
+- **Pure Surface** (#FFFFFF) — Card and container fill
+- **Charcoal Ink** (#18181B) — Primary text, Zinc-950 depth
+- **Muted Steel** (#71717A) — Secondary text, descriptions, metadata
+- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, 1px structural lines
+- **[Accent Name]** (#XXXXXX) — Single accent for CTAs, active states, focus rings
+(Max 1 accent. Saturation < 80%. No purple/neon.)
+
+## 3. Typography Rules
+- **Display:** [Font Name] — Track-tight, controlled scale, weight-driven hierarchy
+- **Body:** [Font Name] — Relaxed leading, 65ch max-width, neutral secondary color
+- **Mono:** [Font Name] — For code, metadata, timestamps, high-density numbers
+- **Banned:** Inter, generic system fonts for premium contexts. Serif fonts banned in dashboards.
+
+## 4. Component Stylings
+* **Buttons:** Flat, no outer glow. Tactile -1px translate on active. Accent fill for primary, ghost/outline for secondary.
+* **Cards:** Generously rounded corners (2.5rem). Diffused whisper shadow. Used only when elevation serves hierarchy. High-density: replace with border-top dividers.
+* **Inputs:** Label above, error below. Focus ring in accent color. No floating labels.
+* **Loaders:** Skeletal shimmer matching exact layout dimensions. No circular spinners.
+* **Empty States:** Composed, illustrated compositions — not just "No data" text.
+
+## 5. Layout Principles
+(Grid-first responsive architecture. Asymmetric splits for Hero sections.
+Strict single-column collapse below 768px. Max-width containment.
+No flexbox percentage math. Generous internal padding.)
+
+## 6. Motion & Interaction
+(Spring physics for all interactive elements. Staggered cascade reveals.
+Perpetual micro-loops on active dashboard components. Hardware-accelerated
+transforms only. Isolated Client Components for CPU-heavy animations.)
+
+## 7. Anti-Patterns (Banned)
+(Explicit list of forbidden patterns: no emojis, no Inter, no pure black,
+no neon glows, no 3-column equal grids, no AI copywriting clichés,
+no generic placeholder names, no broken image links.)
+```
+
+## Best Practices
+- **Be Descriptive:** "Deep Charcoal Ink (#18181B)" — not just "dark text"
+- **Be Functional:** Explain what each element is used for
+- **Be Consistent:** Same terminology throughout the document
+- **Be Precise:** Include exact hex codes, rem values, pixel values in parentheses
+- **Be Opinionated:** This is not a neutral template — it enforces a specific, premium aesthetic
+
+## Tips for Success
+1. Start with the atmosphere — understand the vibe before detailing tokens
+2. Look for patterns — identify consistent spacing, sizing, and styling
+3. Think semantically — name colors by purpose, not just appearance
+4. Consider hierarchy — document how visual weight communicates importance
+5. Encode the bans — anti-patterns are as important as the rules themselves
+
+## Common Pitfalls to Avoid
+- Using technical jargon without translation ("rounded-xl" instead of "generously rounded corners")
+- Omitting hex codes or using only descriptive names
+- Forgetting functional roles of design elements
+- Being too vague in atmosphere descriptions
+- Ignoring the anti-pattern list — these are what make the output premium
+- Defaulting to generic "safe" designs instead of enforcing the curated aesthetic

package/standard-skills/telegram-channel/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: telegram-channel
+description: Operate and diagnose the bundled Telegram channel through its single managed plugin while preserving user credentials, pairing state, and process ownership.
+---
+
+# Telegram Channel
+
+Use this skill for Telegram pairing, inbound and outbound message diagnosis, access rules, and channel verification.
+
+## Workflow
+
+1. Read [references/runtime.md](references/runtime.md) before changing channel configuration.
+2. Inspect the managed plugin and its current process state before proposing a restart or repair.
+3. Keep bot credentials and pairing data in the product's private configuration. Never include them in skills, package manifests, logs, or test fixtures.
+4. Use exactly one bridge and one Telegram MCP owner. Do not create a parallel global MCP entry.
+5. Verify recovery end to end: one process lease, advancing heartbeat, inbound delivery, session handoff, and outbound response.
+
+Do not start, stop, pair, or reconfigure the channel without explicit user authorization.

package/standard-skills/telegram-channel/references/runtime.md

@@ -0,0 +1,7 @@
+# Telegram Runtime Contract
+
+- Telegram is delivered by the bundled managed plugin, not by a seeded user MCP entry.
+- The managed plugin is the sole owner of its bridge and MCP process.
+- Bot credentials and access policy are supplied by the user after installation and never ship in the package.
+- Existing pairing and access configuration wins. Do not replace it during package seeding or updates.
+- A configured file is not runtime proof; verify the live lease and an inbound-to-outbound round trip.

package/standard-skills/translate-native/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Maykbiletti
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/standard-skills/translate-native/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: translate-native
+description: Translate, localize, rewrite, and review user-visible language with native orthography, structural fidelity, and a fail-closed BLUN release gate.
+---
+
+# Translate Native
+
+Use this skill for every translation, localization, translated rewrite, translation review, or user-visible internationalization edit.
+
+This bundled adaptation is based on translate-native 6.41.1. Read [references/native-translation-standard.md](references/native-translation-standard.md) and [references/evaluation-protocol.md](references/evaluation-protocol.md) for the full quality contract. For structured data, also read [references/structured-content.md](references/structured-content.md).
+
+## Seven-pass review
+
+Treat every proposed target as an untrusted draft. Review it in seven distinct passes:
+
+1. Meaning and omissions: preserve every claim, condition, negation, number, and relationship.
+2. Native idiom: remove source-language syntax and translationese without changing meaning.
+3. Register and audience: match locale, tone, formality, and product context.
+4. Terminology and consistency: preserve protected names, commands, paths, placeholders, and repeated terms.
+5. Orthography: use native script, diacritics, capitalization, punctuation, and typography.
+6. Structure and integrity: preserve markup, keys, variables, links, code, and required formatting.
+7. Independent release review: reread source and target as complete documents and attest only what was actually checked.
+
+German `ss` is not deterministic evidence of broken native orthography because it may be correct. ASCII substitutions such as `ae`, `oe`, and `ue` require context-sensitive review against native spelling.
+
+## Mandatory release gate
+
+Before releasing target-language text, call the BLUN language guard tool `release_translation` with:
+
+- the complete source and complete target;
+- the exact language tag and content type;
+- truthful attestations for all seven passes;
+- `short_text_reviewed: true` only after an independent native review of a short UI string, title, or metadata field.
+
+Release only when the response says `release_allowed: true`. Confirm its receipt using `verify_release_token` with the exact same source, target, language, content type, review status, version, and expiry. Never fabricate, edit, reuse, expose, request, or log a release token or signing key.
+
+If the gate blocks, revise and run it again. If the enforced service is unavailable, fail closed for publication-grade or structured translation work. For ordinary conversational translation, run the bundled local guards, label the enforced gate unavailable, and keep the response provisional.
+
+For programmatic integrations, return the verified `release_response` unchanged rather than reconstructing it.

package/standard-skills/translate-native/VERSION

@@ -0,0 +1 @@
+6.41.1

package/standard-skills/translate-native/provenance.json

@@ -0,0 +1,7 @@
+{
+  "name": "translate-native",
+  "version": "6.41.1",
+  "sourceCommit": "047aa2b4ba4c6a7b4797be8ed8ea6b7fd60728f0",
+  "sourceRepository": "https://github.com/Maykbiletti/translate-native",
+  "adaptation": "BLUN host policy replaces client-specific deployment text"
+}

package/standard-skills/translate-native/references/evaluation-protocol.md

@@ -0,0 +1,95 @@
+# Native Translation Evaluation Protocol
+
+## Release rule
+
+Release a translation only when it has zero blocking defects and reads naturally for the specified community, audience, register, and medium. Fluency cannot compensate for changed meaning. Fidelity cannot compensate for obvious translationese.
+
+## Classify defects
+
+| Severity | Definition | Examples | Action |
+| --- | --- | --- | --- |
+| Blocking | Meaning, safety, structure, or identity is damaged | Reversed negation, missing caveat, wrong number, broken placeholder, invented claim, wrong script | Fix before delivery |
+| Major | A native editor would rewrite it or the locale/register is materially wrong | Calque, unnatural syntax, grammatical-but-non-native collocation, broken parallelism, unnecessary borrowing, generic AI filler, wrong honorific, inconsistent terminology, regional mismatch | Fix before delivery |
+| Minor | Meaning and nativeness survive but polish is imperfect | Slight repetition, optional punctuation refinement | Fix when feasible |
+
+Do not average blocking defects into a numeric score. One blocking defect fails the translation.
+
+Grammar is not a release category. A target with zero grammar errors still fails when it contains a major nativeness defect. Use [translationese-review.md](translationese-review.md) for the target-only procedure and worked regression case.
+
+## Run a target-only native review
+
+Temporarily hide the source and judge the target as original writing. Inspect:
+
+- syntax and information order;
+- collocations and idiomatic word choice;
+- paragraph flow, cohesion, rhythm, and repetition;
+- politeness, honorifics, directness, and social relationship;
+- locale, script, punctuation, typography, and medium conventions;
+- whether a native writer would choose the same headline, button, instruction, or transition.
+
+Also inspect whether coordinated items belong to the same grammatical and semantic category, whether source-language technical vocabulary displaced an established native term, and whether polished-sounding AI filler hides a vague relationship.
+
+Rewrite any passage that is merely understandable but not naturally chosen. Preserve protected tokens while moving them to the grammatically natural position.
+
+## Run a source-aware fidelity review
+
+Compare propositions rather than matching words. Account for every source fact, negation, quantity, entity, relationship, condition, exception, uncertainty marker, time reference, and call to action. Flag:
+
+- omissions, additions, duplication, or unjustified explanation;
+- stronger or weaker certainty, obligation, praise, warning, or promise;
+- changed causal relationships, scope, chronology, or ambiguity;
+- terminology drift and inconsistent names;
+- cultural adaptation that changes factual content.
+
+Use back-translation only to reveal possible loss or addition. Never use it as proof of native quality.
+
+## Use independent review when stakes justify it
+
+When another agent or qualified reviewer is available, provide only:
+
+1. the complete source;
+2. the candidate target;
+3. target language, locale, script, audience, register, and medium;
+4. required glossary and protected tokens;
+5. this defect rubric.
+
+Ask for a structured defect list with severity, target excerpt, reason, and minimal correction direction. Do not ask the reviewer to replace the whole translation, reveal an expected answer, or praise the draft. Revise centrally so terminology and voice remain coherent.
+
+Use this release decision contract:
+
+```text
+status: PASS | FAIL
+blocking_defects:
+  - excerpt: exact target fragment
+    class: meaning | completeness | precision | integrity | orthography
+    reason: concise evidence
+major_defects:
+  - excerpt: exact target fragment
+    class: nativeness | locale | register | terminology | parallelism
+    reason: concise evidence
+```
+
+Return `PASS` only when both defect lists are empty. Any blocking or major defect requires revision followed by a complete new native, fidelity, integrity, and orthography review. Never average defects into a passing numeric score.
+
+For legal, medical, safety-critical, contractual, or public high-impact content, an AI reviewer is an additional check, not a substitute for a qualified native professional.
+
+## Route by confidence
+
+- **High:** Language variety and domain are well supported; all gates pass. Deliver normally.
+- **Medium:** One or more usage, locale, or domain choices are uncertain. Verify them with authoritative native sources and rerun the review.
+- **Low:** Reliable evidence is unavailable or varieties may be mixed. Do not present the result as assuredly native. State the limitation or request native review.
+
+Confidence describes evidence, not how fluent the prose appears.
+
+## Evaluate long documents
+
+Create a translation brief before drafting. Record locale, script, audience, address form, voice, tense policy, glossary, names, units, and formatting. Maintain it across sections. After assembly, review the whole document for:
+
+- terminology and capitalization drift;
+- pronoun/reference continuity;
+- headings, captions, lists, and cross-references;
+- consistent voice, politeness, tense, and narrative distance;
+- duplicated or missing content at section boundaries;
+- global rhythm and repeated sentence patterns caused by chunking.
+
+Do not declare a long document finished from section-level checks alone.

package/standard-skills/translate-native/references/native-orthography.md

@@ -0,0 +1,79 @@
+# Native Orthography Gate
+
+## Release rule
+
+Write every target in its native orthography. Correct spelling, language-specific letters, diacritics, alphabet, script, punctuation, casing, spacing, and Unicode normalization are mandatory parts of translation quality, not optional typography.
+
+Do not rely on a separate skill to perform this review. Do not release a translation while a confirmed orthographic defect remains.
+
+## Mandatory review
+
+1. Identify the exact target language, locale, script, and regional standard.
+2. Review every natural-language segment, including headings, buttons, labels, metadata, accessibility text, and mixed-language passages.
+3. Replace ASCII transliterations only when they stand in for native spelling: `schön`, not `schoen`; `förstår`, not `forstar`; `español`, not `espanol`; `čeština`, not `cestina`.
+4. Use the native writing system by default. Do not romanize Greek, Cyrillic, Arabic, Hebrew, Indic, Southeast Asian, or East Asian text unless requested.
+5. Apply locale-specific punctuation and typography, such as Spanish `¿…?` and `¡…!`, French spacing conventions, or Chinese and Japanese punctuation.
+6. Preserve the canonical spelling of names, brands, quotations, and established technical terms. Verify uncertainty instead of inventing a mark.
+7. Normalize newly written UTF-8 content to Unicode NFC. Preserve a different normalization only when a technical format explicitly requires it.
+8. Re-run the full language and fidelity review after any orthographic correction that could change meaning.
+
+## Coverage map
+
+| Language or writing system | Preserve |
+| --- | --- |
+| German | `ä ö ü Ä Ö Ü ß`; use Swiss `ss` where required |
+| Swedish | `å ä ö Å Ä Ö` as separate letters |
+| Danish and Norwegian | `æ ø å Æ Ø Å` |
+| Icelandic and Faroese | accents and letters such as `ð þ æ ö ø` |
+| Spanish | `á é í ó ú ü ñ ¿ ¡` |
+| French | accents, diaeresis, cedilla, and conventional ligatures |
+| Portuguese | acute and circumflex accents, tildes, grave accents, and cedilla |
+| Catalan, Galician, and Basque | native accents, diaeresis, cedilla, middle dot, and `ñ` where applicable |
+| Czech and Slovak | every caron, acute, ring, circumflex, diaeresis, and language-specific consonant |
+| Polish, Hungarian, Romanian | complete native diacritics; Romanian comma-below `ș ț`, not cedilla variants |
+| Turkish and Azerbaijani | dotted and undotted `i`, `ç ğ ö ş ü`, and Azerbaijani `ə` |
+| South Slavic Latin scripts | `č ć đ š ž` and the exact requested regional standard |
+| Baltic languages | macrons, carons, dots, cedillas, and ogoneks |
+| Vietnamese | complete tone and vowel marks, including stacked marks |
+| Greek | Greek alphabet with correct tonos and dialytika; no Greeklish by default |
+| Cyrillic languages | the exact language alphabet, including letters absent from Russian |
+| Arabic-script languages | the correct language-specific letters and punctuation; optional vowel marks only when conventional |
+| Hebrew | Hebrew script; preserve or add niqqud only when the task requires it |
+| Indic scripts | native letters, vowel signs, conjuncts, nukta, virama, and punctuation |
+| Thai, Lao, Khmer, and Myanmar | tone marks, vowel placement, combining marks, and native spacing conventions |
+| Chinese | requested Simplified or Traditional characters and locale-appropriate punctuation |
+| Japanese | appropriate kanji, kana, prolonged-sound and iteration marks, spacing, and punctuation |
+| Korean | Hangul and correct Korean spacing; preserve hanja only when intended |
+| Armenian, Georgian, Ethiopic, and other scripts | native alphabet, canonical spelling, and punctuation |
+
+This map is illustrative, never exhaustive. Apply the same native-orthography rule to every human language and writing system.
+
+## Technical exceptions
+
+Keep exact ASCII or source spelling when modification could break behavior or fidelity:
+
+- code identifiers, commands, environment variables, API fields, JSON keys, database columns, slugs, URLs, email addresses, paths, hashes, tokens, regular expressions, and protocol values;
+- exact quotations, imported data, trademarks, and personal names whose canonical spelling is known;
+- systems with a documented encoding limitation;
+- explicit requests for transliteration, ASCII folding, search keys, or URL-safe text.
+
+Technical exceptions never justify ASCII-only prose around protected values.
+
+## Limits of automated checks
+
+The bundled translation guard verifies UTF-8, Unicode NFC, protected tokens, and structure. The bundled diacritics linter flags frequent ASCII substitutions in many Latin-script languages while ignoring common technical spans. Neither can prove that a word contains the correct diacritic, that the requested script was chosen, or that spelling is native. Use deterministic checks as evidence, then complete the language-aware review manually or with a qualified native reviewer.
+
+## Verification hierarchy
+
+When usage, spelling, script, or locale conventions are uncertain, verify in this order:
+
+1. the requested language community's academy, language council, government style guide, or other recognized normative body;
+2. the [Unicode Standard](https://unicode.org/reports/tr15/) for normalization and character behavior;
+3. [Unicode CLDR](https://cldr.unicode.org/) for locale identifiers, exemplar characters, punctuation sets, plural rules, number and date conventions, and script variants;
+4. the [W3C Language Enablement Index](https://www.w3.org/International/typography/gap-analysis/language-matrix.html) for writing-system layout and typography;
+5. the [IANA Language Subtag Registry](https://www.iana.org/assignments/language-subtag-registry) for language, region, and script tags;
+6. contemporary native-edited dictionaries and monolingual corpora for usage and collocations.
+
+Examples of authoritative language sources include Sweden's [Institutet för språk och folkminnen](https://www.isof.se/svenska-spraket/frageladan), the [Real Academia Española](https://www.rae.es/), the Czech Academy's [Czech Language Institute](https://ujc.cas.cz/), the [Institut d'Estudis Catalans](https://www.iec.cat/), and [Euskaltzaindia](https://www.euskaltzaindia.eus/).
+
+Do not treat a translation engine, parallel corpus, search-result count, ASCII spell-checker, or another model's confidence as a normative source. Use them only to locate questions that still require native evidence.