f8-features-storage-workflow
Use when implementing, documenting, or troubleshooting Storage workflows in F8Framework, including local persistence, user-scoped keys, AES encryption, Gzip compression, generic collections, and common Unity value types.
Use when implementing, documenting, or troubleshooting Storage workflows in F8Framework, including local persistence, user-scoped keys, AES encryption, Gzip compression, generic collections, and common Unity value types.
Use when implementing or troubleshooting Input feature workflows — multi-platform input, virtual buttons, device switching, and key/axis listening in F8Framework.
Use when working with StreamingAssets Loader tools — sync reading of StreamingAssets files, especially on Android in F8Framework.
Add or update a TPU kernel using jax.experimental.pallas. Use when asked to implement, modify, benchmark, or autotune a Pallas TPU/GPU kernel.
Assist with merging updates and synchronizing functionality from the upstream WinUAE repository (Windows) to Amiberry (Linux/macOS/Android/Windows). Includes a guide for porting Win32 GUI dialogs to Dear ImGui, mapping Windows controls to ImGui equivalents, analyzing platform-specific code, and preserving upstream-sync safety when Amiberry needs local divergences in WinUAE-tracked files. Use this for analyzing upstream commits, identifying Windows-specific code, adapting GUI panels, handling `#ifdef AMIBERRY` splits, and verifying feature parity.
Reference workflow for Amiberry packaging, install-layout, and runtime-path fixes. Use for distro packaging changes, `BUNDLE_SDL`, RPATH and shared-library bundling work, DEB or RPM dependency adjustments, CI matrix packaging toggles, Windows portable install detection, and executable-directory vs current-working-directory path bugs in files such as `cmake/linux/install.cmake`, `packaging/CMakeLists.txt`, `.github/workflows/c-cpp.yml`, and `src/osdep/amiberry.cpp`.
Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says "rebuttal", "reply to reviewers", "ICML rebuttal", "OpenReview response", or wants to answer external reviews safely.
Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Supports push-only (webhook) and interactive (bidirectional) modes. Use when user says "发飞书", "notify feishu", or other skills need to send status updates.
Basics of developing with Turbo Laravel. Activates when starting a new Turbo Laravel project; using dom_id, dom_class, turbo_stream(), or turbo_stream_view() helpers; working with Blade components like x-turbo::frame, x-turbo::stream, x-turbo::stream-from, or x-turbo::refreshes-with; using @domid, @domclass, @channel, or @turbonative directives; checking wantsTurboStream(), wasFromTurboFrame(), or wasFromHotwireNative() request macros; or when the user mentions Hotwire, Turbo, HTML over the wire, or partial page updates.
Develops with Turbo Drive for SPA-like navigation. Activates when configuring page morphing with x-turbo::refreshes-with; working with data-turbo, data-turbo-track, data-turbo-permanent, or data-turbo-preload attributes; managing cache control with x-turbo::exempts-page-from-cache, x-turbo::exempts-page-from-preview, or x-turbo::page-requires-reload; enabling view transitions with x-turbo::page-view-transition; handling form redirects with TurboMiddleware; customizing the progress bar; or when the user mentions Turbo Drive, navigation, page morphing, prefetching, or asset tracking.
Develops with Turbo Frames for scoped navigation and lazy loading. Activates when using the x-turbo::frame Blade component or turbo-frame HTML element; working with data-turbo-frame targeting, frame lazy loading via src attribute, or data-turbo-action for URL updates; detecting frame requests with wasFromTurboFrame(); using frame morphing with refresh="morph"; or when the user mentions Turbo Frame, turbo frame, scoped navigation, inline editing, lazy loading frames, or breaking out of a frame with _top.
Develops with Turbo Streams for partial page updates and real-time broadcasting. Activates when using turbo_stream() or turbo_stream_view() helpers; working with stream actions like append, prepend, replace, update, remove, before, after, or refresh; using the Broadcasts trait, broadcastAppend, broadcastPrepend, broadcastReplace, broadcastRemove, or broadcastRefresh methods; listening with x-turbo::stream-from; using the TurboStream facade for handmade broadcasts; combining multiple streams; or when the user mentions Turbo Stream, broadcasting, real-time updates, WebSocket streams, or partial page changes.
Vue 3 TypeScript, vue-tsc, Volar, Vite, component props, testing, composition API.
提供标准化的 useTable, useRequest 等 Hooks,用于简化列表页和异步请求的逻辑复用。
帮助配置和启动本地开发服务器。当用户提到启动开发服务器、dev server、pnpm dev 时使用。
详细记录了大型 Vue 项目从 Webpack 迁移到 Vite 的完整步骤,包括别名配置、环境变量处理和 CommonJS 兼容性问题的解决。
帮助开发者上手 @blueking/chat-x 组件库开发。当用户需要了解 chat-x、开发新组件时使用。
Scaffold and integrate custom Stac widgets and actions with parsers and registration checks. Use when users ask to build new StacParser or StacActionParser implementations, generate custom model classes, or verify parser registration inside Stac.initialize.
Build Stac DSL screens and themes from product requirements with safe defaults and reusable templates. Use when users ask to create or refactor StacScreen files, map UI requirements to Stac widgets/actions/styles, or scaffold new screen/theme files.
Help initialize and validate a Stac-enabled Flutter project and ship a first server-driven screen. Use when users ask to set up Stac CLI, run stac init/build/deploy, verify project prerequisites, or troubleshoot first-run setup and missing configuration files.