Loading...
Loading...
Found 1,386 Skills
Export auto-editor's edit or microphone recording to a video editor (Premiere, DaVinci Resolve, Final Cut Pro, ShotCut, Kdenlive), to individual clips, or to auto-editor timeline files (.v1/.v2/.v3); and import timeline/XML files to render them. Use when someone wants an editor-ready project, a preserved microphone source, split clips, or timeline files instead of a finished video.
Enforces Flutter widget composition — extract named const Widget classes never `Widget _buildX()` methods, lean build() (no I/O/formatting/domain math, precompute in the ViewModel), dumb Views that watch one Notifier and route intents via ref.read, StatelessWidget by default with every controller disposed, lazy `.builder` lists, cheapest-widget choices (SizedBox/ColoredBox/Align over Container), a strict key policy (ValueKey for reorderable lists, never GlobalKey), gesture→visible-focusable-fallback wiring, plus structural layout — full-bleed background vs SafeArea content, computed cell sizing, the GridView cross/main-axis spacing trap, EdgeInsetsDirectional, and resizeToAvoidBottomInset/IME handling. Use when building or refactoring any screen or widget, splitting a large build() into components, writing GridView/ListView/LayoutBuilder/SafeArea/Scaffold, wiring onTap/onLongPress/Draggable, choosing a key or data class, or reviewing widget code in a diff.
Stands up one navigable feature the same way every time — a fixed lib/features/<feature>/presentation/ folder (dumb View + one 1:1 Notifier/AsyncNotifier ViewModel + widgets/ + scoped <feature>_providers.dart), downward-only dependencies with no cross-feature imports, reactive reads as scoped StreamProviders over a repository .watch(), every mutation through one repository single-write-path method, typed Result/Failure surfaced as AsyncValue, a typed go_router route carrying identity in path params, ARB parity across locales, family+autoDispose keying, and EdgeInsetsDirectional-only geometry. Use when adding a screen, tab, or feature folder; wiring a feature Notifier/ViewModel or a scoped stream provider; registering a route; adding ARB keys for a new screen; splitting an over-grown feature; or adding a persisted record its View reads.
Create, edit, and review MaaFramework interface.json (Project Interface V2), covering task entry declaration, controller/resource configuration, GUI option wiring (pipeline_override and override order), preset configuration, pretask pre-launch tasks, agent child process configuration, import splitting and structure troubleshooting. Use when creating, editing, or reviewing an interface.json for a MaaFW project, adding user-facing options or presets, wiring pipeline_override, configuring pretask or agent child processes, splitting interface files via import, or diagnosing interface structure errors.
Create deterministic editorial-style cover images with a warm paper-gray background, oversized black slab-serif/Chinese display typography, generous whitespace, and a dotted vector analysis icon. Use when the user asks for a “点阵编辑风封面”, “暖灰杂志风封面”, “Codex + Hyperframes 同款封面”, or wants to reproduce/adapt the specific minimal left-text/right-icon banner style. Produce editable SVG and a rendered PNG; do not use this skill for generic covers without this visual direction.
Use when someone asks for a Specimen icon, runs /specimen, or wants a 3D product icon — a glossy object on a soft tile, lit like a piece in a display case, looping, in a dark and a light theme — for a feature grid, a landing page, a changelog or an empty state, shipped as video or as a live element with nothing to install.
Modularizes existing Angular components and projects following official angular.dev best practices, SOLID principles, and the Smart/Presentational pattern. Use when the user asks to "modularize", "refactor component", "split component", "extract component", "decompose component", "organize Angular project", "apply Angular best practices", "split into feature modules", "restructure project", or "improve project structure".
Unified entry for Feishu instant messaging, covering sending, replying, forwarding, merged forwarding, urgent messaging and resource downloading, reading chat history, Reaction, Pin and group member management, constructing V2 interactive cards, and WebSocket event subscription. This Skill must be used when users request to send messages or notifications, view or export group chats, manage group members, create Feishu cards for alerts/approvals/reports/dashboards/marketing promotions/festival greetings/brand displays/hand-drawn or dark-themed creatives/cards with buttons or charts, listen to real-time message or approval events, or process message attachments. This Skill must be triggered as long as the target carrier is Feishu chat or group messages, or the request contains terms like msg/chat/card/event, post/interactive, oc_/om_, Reaction, Pin, urgent messaging or local images in messages, even if the user doesn't explicitly mention CLI. Do not use it for email reading/replying/drafting, nor for meeting recording, Minutes or verbatim transcripts; use feishu-cli-mail and feishu-cli-meetings for those respectively. Use feishu-cli-platform for global message search.
Build and maintain the standing risk register for a technical event - risks named by category, scored on a likelihood x impact matrix adapted to a dated one-shot deliverable, split into prevention, contingency or insurance, the insurance stack including the communicable-disease buy-back, internal go/no-go decision dates set against the venue's escalating cancellation-fee curve, and the on-site emergency plan. Use whenever the user mentions event insurance, cancelling or postponing an event, a go/no-go call, an emergency or evacuation plan, weather or speaker-dropout contingency, or a risk register - even if they never say "risk". Not legal or insurance advice. Do NOT use for day-of live incident handling - use samber/dev-event-organizer-skills@event-run-of-show instead.
Review or design an iOS interface for iPhone Duo's poses — closed, open, book-folded, tabletop and tent — covering side-mounted controls, asymmetric layouts, fold avoidance, sheets, and how to use the inner display well. Use for design critique, mockup review, or deciding what a screen should look like on a foldable iPhone rather than how to code it.
Make a 30-45 second product launch video in code with Claude Code, the kind SaaS companies post on launch day. One sentence split across scenes, real product screens with slow camera moves, a typed prompt, a proof beat and a clear call to action. Use when someone says "launch video", "promo video for my product", "announce my course/cohort/offer", "make a launch reel" or "trailer for my product".
The Suno craft skill — generate full songs, brand music, and audio (vocals, lyrics, stems) with the right tier, honest rights, and structure control. Use when someone wants to make music with Suno/AI, create a brand sound/theme/jingle/podcast intro, control song structure (meta-tags), build a consistent sonic identity (Personas, Voices), split stems, distribute AI music to Spotify/YouTube, or asks whether they own their Suno songs. Uses the TRACK framework. Reads ai-music-and-sound (the router) + brand-profile + the content skill the music serves first. The agent writes briefs/lyrics and can drive the API where connected; the HUMAN's ears judge every track; WoopSocial publishes the content it scores. Rights: paid plan from the first note, commercial rights not ownership, no indemnification while litigation runs, AI-disclosure at distribution; never clone a real artist's voice. Distinct from ai-music-and-sound, ai-voiceover/elevenlabs (spoken TTS), capcut, and podcast-and-audiograms.