261 assets · page 8 of 11
Use when a screen, an entity editor or a journey should be seen and critiqued as a running mockup, or when the user says 'prototype this screen', 'build the storybook', 'click-dummy', 'try the editor for this entity'. Grows one Vue Storybook package layer by layer: floorplans, screens, entity editors, the whole app, journeys, and a generated page per feature.
Extract VBA source code (.bas / .cls modules, forms, reports) from a Microsoft Access database (.accdb / .mdb) WITHOUT MS Access installed. Use when asked to extract, dump, recover, or read VBA / macros / module code from an Access database, or when olevba fails with 'not a supported file type' on an .accdb. Handles modern ACE12 'Standard ACE DB' files that olevba and mdbtools cannot decompress.
Team notifications and messaging for skaile-dev. Supports free-form Mattermost messages plus structured templates for plans, breaking changes, releases, and devlog summaries.
Use when _concept/ needs a health check, its cross-references have drifted, or you want to know whether every feature is actually built and shipped. Produces the review verdict and a build-coverage matrix read from the trace, each finding naming the skill that fixes it. Triggers on 'audit the concept', 'check for issues', 'fix the links', 'is every feature done', 'what code belongs to no feature'.
[skaile-development] Use when creating, building, modifying, or extending a PostXL-generated app — including scaffolding a brand-new one into an empty repo with `pxl create-project`. Activates when you see `postxl-schema.json`, `postxl-lock.json`, `generate.ts`, `skaile.preview.json`, or `// @custom-start` markers; when the user mentions PostXL, PXL, `pxl`, regenerate, eject, custom block, or schema drift; when a user asks to build a new full-stack TypeScript app on the PostXL stack (NestJS + Prisma + tRPC + React 19 + Vite); or when a regeneration produced a confusing diff or merge conflict. Also covers the skaile-dev projects `platform/backend`, `platform/frontend`, and `store/backend`.
Use when an agent needs to author, modify, review, render, or export PowerPoint (.pptx / .pptm) decks — create/open/close documents, add/duplicate/delete/reorder slides, edit text (with run/paragraph/shape scope + styling), insert images with picture effects, add/edit tables (incl. merge + per-cell borders), draw shapes (solid/gradient/pattern fills), update chart data in existing charts, render slides to PNG/JPG/SVG at low or high fidelity, and export to PPTX/PDF/HTML/PNG-batch/JPG-batch/SVG-batch/outline-text. Stateful Apache POI 5.5.x + LibreOffice engine over stdio, 52 tools.
Use when you need to analyze a user request and find the appropriate prog-expert-* skill from the programming-* directories (e.g. programming-js, programming-python), or when you need to store new implementation knowledge and need to know which expert should learn it.
Use when you need to set up, develop, or integrate Directus into your project, especially with Docker and Nuxt 3. Triggers include "setup directus with docker", "configure directus local development", "generate directus types", "integrate directus with nuxt", or "authenticate with directus sdk".
Use when you need to create, configure, or manage GitAgent-compatible agent definitions (agent.yaml, SOUL.md, RULES.md, SKILL.md). Expert-level programming and pattern management for the GitAgent open standard (spec v0.1.0).
Use when you need to create, edit, or debug Marimo reactive Python notebooks, including cell structure, reactivity rules, output display, and the Lint-Export-Assert test protocol. Expert-level programming and pattern management.
Use when you need to expert-level nuxt development. Expert-level programming and pattern management.
Use when you need to work with omp (pi-coding-agent), including RPC mode integration, skill authoring, extension development, agent embedding, and CLI configuration. Expert-level programming and pattern management.
Use when you need to use when you need to implement advanced primevue 4 features in nuxt 3, including design tokens, forms, and custom theming.. Expert-level programming and pattern management.
Use when you need to implement pydantic-ai Agent API patterns including structured outputs with result_type, message history, OpenAI/Gemini model backends, async streaming with run_stream(), and multi-provider integration. Expert-level programming and pattern management.
Use when you need to implement Python 3.12+ patterns, uv workspace monorepo management, async Python, decorator patterns, pytest/mock testing, ruff/mypy configuration, Rich CLI output, pydantic-settings config, and Protocol-based interface design. Expert-level programming and pattern management.
Use when you need to implement shadcn-vue (shadcn-nuxt) in Nuxt 3/4 — component registry via components.json, Tailwind CSS v4 with @tailwindcss/vite, class-variance-authority, tailwind-merge, and auto-imported shadcn components.
Use when you need to use when you need to implement advanced tiptap editors in nuxt 3, including collaboration, custom node views, and context menus.. Expert-level programming and pattern management.
Use when you need to implement TTS (text-to-speech) or STT (speech-to-text) integrations in Nuxt 3/Nitro applications, including Deepgram streaming STT via WebSocket, ElevenLabs TTS, browser MediaRecorder, and audio settings management. Expert-level programming and pattern management.
Use when you need to implement a typst template from an image or pdf reference iteratively. Expert-level programming and pattern management.
Use when you need to implement UnaUI (@una-ui/nuxt) in Nuxt 3/4 — N* component usage, color tokens, slot patterns, UnoCSS-driven theming, and UnaUI module configuration.
Use when you need to implement or configure UnoCSS in Nuxt 3/4 projects — presets (wind4, icons, attributify, typography), uno.config.ts theming, dark mode, safelist, layers, and UnoCSS module integration.
Use when you need to implement VueUse composables in Nuxt 3, including auto-import configuration, composable selection, conflict handling with Nuxt built-ins, and reactive browser/state/DOM utilities. Expert-level programming and pattern management.
Create, review, or update a design spec / proposal for new features, architectural changes, or cross-package work in the skaile-dev monorepo. Use when work is too complex to jump straight into code — the spec captures the problem, design, alternatives, and approval status before implementation begins.
Use when an app is built or adopted and you suspect its design, not its conformance, is what hurts users — scans the code against the rulebook, the glossary and APP-DESIGN.md for shallow screens, overloaded concepts, hidden modes, undeclared representations and tier violations, reports evidenced candidates, then grills the one you pick. Triggers on 'what is wrong with this design', 'find design problems', 'which screens should merge', 'improve the UX of this app', 'design review of the code'.