Skip to content

搵技能.../

Agent Skill Search Engine

搜尋

搜尋
分類
職業

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Fl Studio Basics | Skills Pool

技能檔案

Fl Studio Basics

Use when any task is executed in FL Studio; provides universal UI rules (Hint Bar usage, Channel Rack orientation, numeric entry, and anti-loop behavior).

artemgetmann2 星標2026年2月16日

職業
分類: 代碼質素

技能內容

Apply these rules for all FL Studio tasks before domain-specific steps.

Hint Bar policy

Use Hint Bar only when target identity is ambiguous.
Verify once, then act immediately.
If two checks fail, stop checking and use direct visual positioning.
Do not chain hover+zoom+hover loops.

Channel Rack orientation

F6 focuses Channel Rack.
Rows are instruments, steps run left-to-right (1..16).
Confirm row label once (for example "808 Kick"), then execute step clicks.
If row identity or active-step state is unclear, call extract_fl_state instead of repeating zoom loops.

Numeric fields (tempo/values)

Direct entry first: click field, type value, press Enter.
Verify resulting value once.
Do not use repeated scroll loops for numeric fields.

Menu / popup policy

相關技能

快速安裝

Fl Studio Basics

npx skillvault add artemgetmann/artemgetmann-cortex-skills-fl-studio-basics-skill-md

下載 Skill 打開源碼倉庫

作者: artemgetmann
星標: 2
更新時間: 2026年2月16日
職業

本頁內容

01Hint Bar policy

Open menu.
Use at most one zoom on the menu list if needed.
Click target option.
Verify result.

Anti-loop rule

Do not perform more than two consecutive inspection-only actions (zoom/mouse_move) without a decisive action (left_click or key).
When blocked by ambiguity after two inspections, use extract_fl_state and then execute a decisive action immediately.

02

Channel Rack orientation

03Numeric fields (tempo/values)

04Menu / popup policy

05Anti-loop rule

Musicians and Singers

Openclaw Release Maintainer

Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

Verify

Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

Flow

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

自動化工具

Fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

Hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

microsoft184.0k

Add Policy

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

microsoft184.0k

Musicians and Singers