dk-frontend-skills 1.0.0

package/.claude/skills/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/.claude/skills/frontend-design/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
+license: Complete terms in LICENSE.txt
+---
+
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
+
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
+
+**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
+
+Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

package/.claude/skills/moai-framework-electron/SKILL.md

@@ -0,0 +1,328 @@
+---
+name: moai-framework-electron
+description: >
+  Electron 33+ desktop app development specialist covering Main/Renderer
+  process architecture, IPC communication, auto-update, and packaging with
+  Electron Forge. Use when building cross-platform desktop applications.
+license: Apache-2.0
+compatibility: Designed for Claude Code
+allowed-tools: Read, Grep, Glob, mcp__context7__resolve-library-id, mcp__context7__get-library-docs
+user-invocable: false
+metadata:
+  version: "2.0.0"
+  category: "framework"
+  status: "active"
+  updated: "2026-01-10"
+  modularized: "false"
+  tags: "electron, desktop, cross-platform, nodejs, chromium, ipc, auto-update, electron-builder, electron-forge"
+  context7-libraries: "/electron/electron, /electron/forge, /electron-userland/electron-builder"
+  related-skills: "moai-lang-typescript, moai-domain-frontend, moai-lang-javascript"
+---
+
+# Electron 33+ Desktop Development
+
+## Quick Reference
+
+Electron 33+ Desktop App Development Specialist enables building cross-platform desktop applications with web technologies.
+
+Auto-Triggers: Electron projects detected via electron.vite.config.ts or electron-builder.yml files, desktop app development requests, IPC communication pattern implementation
+
+### Core Capabilities
+
+Electron 33 Platform:
+
+- Chromium 130 rendering engine for modern web features
+- Node.js 20.18 runtime for native system access
+- Native ESM support in main process
+- WebGPU API support for GPU-accelerated graphics
+
+Process Architecture:
+
+- Main process runs as single instance per application with full Node.js access
+- Renderer processes display web content in sandboxed environments
+- Preload scripts bridge main and renderer with controlled API exposure
+- Utility processes handle background tasks without blocking UI
+
+IPC Communication:
+
+- Type-safe invoke/handle patterns for request-response communication
+- contextBridge API for secure renderer access to main process functionality
+- Event-based messaging for push notifications from main to renderer
+
+Auto-Update Support:
+
+- electron-updater integration with GitHub and S3 publishing
+- Differential updates for smaller download sizes
+- Update notification and installation management
+
+Packaging Options:
+
+- Electron Forge for integrated build tooling and plugin ecosystem
+- electron-builder for flexible multi-platform distribution
+
+Security Features:
+
+- contextIsolation for preventing prototype pollution
+- Sandbox enforcement for renderer process isolation
+- Content Security Policy configuration
+- Input validation patterns for IPC handlers
+
+### Project Initialization
+
+Creating a new Electron application requires running the create-electron-app command with the vite-typescript template. Install electron-builder as a development dependency for packaging. Add electron-updater as a runtime dependency for auto-update functionality.
+
+For detailed commands and configuration, see reference.md Quick Commands section.
+
+---
+
+## Implementation Guide
+
+### Project Structure
+
+Recommended Directory Layout:
+
+The source directory should contain four main subdirectories:
+
+Main Directory: Contains the main process entry point, IPC handler definitions organized by domain, business logic services, and window management modules
+
+Preload Directory: Contains the preload script entry point and exposed API definitions that bridge main and renderer
+
+Renderer Directory: Contains the web application built with React, Vue, or Svelte, including the HTML entry point and Vite configuration
+
+Shared Directory: Contains TypeScript types and constants shared between main and renderer processes
+
+The project root should include the electron.vite.config.ts for build configuration, electron-builder.yml for packaging options, and resources directory for app icons and assets.
+
+### Main Process Setup
+
+Application Lifecycle Management:
+
+The main process initialization follows a specific sequence. First, enable sandbox globally using app.enableSandbox() to ensure all renderer processes run in isolated environments. Then request single instance lock to prevent multiple app instances from running simultaneously.
+
+Window creation should occur after the app ready event fires. Configure BrowserWindow with security-focused webPreferences including contextIsolation enabled, nodeIntegration disabled, sandbox enabled, and webSecurity enabled. Set the preload script path to expose safe APIs to the renderer.
+
+Handle platform-specific behaviors: on macOS, re-create windows when the dock icon is clicked if no windows exist. On other platforms, quit the application when all windows close.
+
+For implementation examples, see examples.md Main Process Entry Point section.
+
+### Type-Safe IPC Communication
+
+IPC Type Definition Pattern:
+
+Define an interface that maps channel names to their payload types. Group channels by domain such as file operations, window operations, and storage operations. This enables type checking for both main process handlers and renderer invocations.
+
+Main Process Handler Registration:
+
+Register IPC handlers in a dedicated module that imports from the shared types. Each handler should validate input using a schema validation library such as Zod before processing. Use ipcMain.handle for request-response patterns and return structured results.
+
+Preload Script Implementation:
+
+Create an API object that wraps ipcRenderer.invoke calls for each channel. Use contextBridge.exposeInMainWorld to make this API available in the renderer as window.electronAPI. Include cleanup functions for event listeners to prevent memory leaks.
+
+For complete IPC implementation patterns, see examples.md Type-Safe IPC Implementation section.
+
+### Security Best Practices
+
+Mandatory Security Settings:
+
+Every BrowserWindow must have webPreferences configured with four critical settings. contextIsolation must always be enabled to prevent renderer code from accessing Electron internals. nodeIntegration must always be disabled in renderer processes. sandbox must always be enabled for process-level isolation. webSecurity must never be disabled to maintain same-origin policy enforcement.
+
+Content Security Policy:
+
+Configure session-level CSP headers using webRequest.onHeadersReceived. Restrict default-src to self, script-src to self without unsafe-inline, and connect-src to allowed API domains. This prevents XSS attacks and unauthorized resource loading.
+
+Input Validation:
+
+Every IPC handler must validate inputs before processing. Prevent path traversal attacks by rejecting paths containing parent directory references. Validate file names against reserved characters. Use allowlists for permitted directories when implementing file access.
+
+For security implementation details, see reference.md Security Best Practices section.
+
+### Auto-Update Implementation
+
+Update Service Architecture:
+
+Create an UpdateService class that manages the electron-updater lifecycle. Initialize with the main window reference to enable UI notifications. Configure autoDownload as false to give users control over bandwidth usage.
+
+Event Handling:
+
+Handle update-available events by notifying the renderer and prompting the user for download confirmation. Track download-progress events to display progress indicators. Handle update-downloaded events by prompting for restart.
+
+User Notification Pattern:
+
+Use system dialogs to prompt users when updates are available and when downloads complete. Send events to the renderer for in-app notification display. Support both immediate and deferred installation.
+
+For complete update service implementation, see examples.md Auto-Update Integration section.
+
+### App Packaging
+
+Electron Builder Configuration:
+
+Configure the appId with reverse-domain notation for platform registration. Specify productName for display in system UI. Set up platform-specific targets for macOS, Windows, and Linux.
+
+macOS Configuration:
+
+Set category for App Store classification. Enable hardenedRuntime and configure entitlements for notarization. Configure universal builds targeting both x64 and arm64 architectures.
+
+Windows Configuration:
+
+Specify icon path for executable and installer. Configure NSIS installer options including installation directory selection. Set up code signing with appropriate hash algorithms.
+
+Linux Configuration:
+
+Configure category for desktop environment integration. Set up multiple targets including AppImage for universal distribution and deb/rpm for package manager installation.
+
+For complete configuration examples, see reference.md Configuration section.
+
+---
+
+## Advanced Patterns
+
+For comprehensive documentation on advanced topics, see reference.md and examples.md:
+
+Window State Persistence:
+
+- Saving and restoring window position and size across sessions
+- Handling multiple displays and display changes
+- Managing maximized and fullscreen states
+
+Multi-Window Management:
+
+- Creating secondary windows with proper parent-child relationships
+- Sharing state between multiple windows
+- Coordinating window lifecycle events
+
+System Tray and Native Menus:
+
+- Creating and updating system tray icons with context menus
+- Building application menus with keyboard shortcuts
+- Platform-specific menu patterns for macOS and Windows
+
+Utility Processes:
+
+- Spawning utility processes for CPU-intensive background tasks
+- Communicating with utility processes via MessageChannel
+- Managing utility process lifecycle and error handling
+
+Native Module Integration:
+
+- Rebuilding native modules for Electron Node.js version
+- Using better-sqlite3 for local database storage
+- Integrating keytar for secure credential storage
+
+Protocol Handlers and Deep Linking:
+
+- Registering custom URL protocols for app launching
+- Handling deep links on different platforms
+- OAuth callback handling via custom protocols
+
+Performance Optimization:
+
+- Lazy loading windows and heavy modules
+- Optimizing startup time with deferred initialization
+- Memory management for long-running applications
+
+---
+
+## Works Well With
+
+- moai-lang-typescript - TypeScript patterns for type-safe Electron development
+- moai-domain-frontend - React, Vue, or Svelte renderer development
+- moai-lang-javascript - Node.js patterns for main process
+- moai-domain-backend - Backend API integration
+- moai-workflow-testing - Testing strategies for desktop apps
+
+---
+
+## Troubleshooting
+
+Common Issues and Solutions:
+
+White Screen on Launch:
+
+Verify the preload script path is correctly configured relative to the built output directory. Check that loadFile or loadURL paths point to existing files. Enable devTools to inspect console errors. Review CSP settings that may block script execution.
+
+IPC Not Working:
+
+Confirm channel names match exactly between main handlers and renderer invocations. Ensure handlers are registered before windows load content. Verify contextBridge usage follows the correct pattern with exposeInMainWorld.
+
+Native Modules Fail:
+
+Run electron-rebuild after npm install to recompile native modules. Match the Node.js version embedded in Electron. Add a postinstall script to automate rebuilding.
+
+Auto-Update Not Working:
+
+Verify the application is code-signed as updates require signing. Check publish configuration in electron-builder.yml. Enable electron-updater logging to diagnose connection issues. Review firewall settings that may block update checks.
+
+Debug Commands:
+
+Rebuild native modules with npx electron-rebuild. Check Electron version with npx electron --version. Enable verbose update logging with DEBUG=electron-updater environment variable.
+
+---
+
+## Resources
+
+For complete code examples and configuration templates, see:
+
+- reference.md - Detailed API documentation, version matrix, Context7 library mappings
+- examples.md - Production-ready code examples for all patterns
+
+For latest documentation, use Context7 to query:
+
+- /electron/electron for core Electron APIs
+- /electron/forge for Electron Forge tooling
+- /electron-userland/electron-builder for packaging configuration
+
+---
+
+Version: 2.0.0
+Last Updated: 2026-01-10
+Changes: Restructured to comply with CLAUDE.md Documentation Standards - removed all code examples, converted to narrative text format
+
+<!-- moai:evolvable-start id="rationalizations" -->
+## Common Rationalizations
+
+| Rationalization | Reality |
+|---|---|
+| "I can use Node.js APIs directly in the renderer process" | Renderer process runs untrusted content. Direct Node.js access is a remote code execution vector. Use IPC through the preload bridge. |
+| "contextIsolation is unnecessary since I trust my own code" | Context isolation prevents prototype pollution from web content reaching Node.js. It is not about trusting your code, it is about isolating contexts. |
+| "Auto-update can be configured after release" | Shipping without auto-update means users stay on vulnerable versions. Configure it before the first release. |
+| "I will package the app later, development builds are enough for testing" | Development builds have different file paths, permissions, and code signing. Only production-packaged builds reveal real distribution issues. |
+| "IPC is slow, I will share state through global variables" | IPC overhead is microseconds. Global variables bypass process isolation, which exists for security. |
+
+<!-- moai:evolvable-end -->
+
+<!-- moai:evolvable-start id="red-flags" -->
+## Red Flags
+
+- nodeIntegration set to true in BrowserWindow options
+- contextIsolation set to false without documented security justification
+- Renderer process imports directly from electron or node modules (bypass preload)
+- No auto-update mechanism configured
+- IPC handler does not validate or sanitize arguments from renderer
+
+<!-- moai:evolvable-end -->
+
+<!-- moai:evolvable-start id="verification" -->
+## Verification
+
+- [ ] nodeIntegration is false and contextIsolation is true in all BrowserWindows
+- [ ] All renderer-to-main communication uses contextBridge and IPC
+- [ ] IPC handlers validate input arguments before processing
+- [ ] Auto-update configured and tested (show update configuration)
+- [ ] Application packages successfully with Electron Forge (show build output)
+- [ ] No direct require('electron') in renderer process code
+
+<!-- moai:evolvable-end -->
+
+## Telemetry Window
+
+**Status**: UNCLEAR (60-day window)
+**R4 audit verdict**: KEEP (monitor)
+**SPEC**: SPEC-V3R2-WF-001 §6.2 (REQ-WF001-013)
+**Window start**: 2026-04-25 (Wave 1.5 commit date)
+**Window end**: 2026-06-24 (60 days)
+**Re-audit trigger**: SessionStart hook activation count for this skill
+**Decision criteria**:
+- If activation count >= 5 during window → retain permanently
+- If activation count = 0 during window → schedule RETIRE in v3.1
+- If 0 < count < 5 → retain with "low-use" tag