tcballard/build-omarchy-plugins

omarchy-qml-patterns

Apply shared hosted-QML patterns to Omarchy 4 Quattro plugin code, including theme tokens, layout, process execution and local state.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/tcballard/build-omarchy-plugins --skill omarchy-qml-patterns

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Write hosted Omarchy QML

Inspect the installed host and closest working component. Use its contract rather than assuming the pinned examples fit every version.

  • Use hosted Item/UI entry points, never a second ShellRoot or Quickshell process. Give late-injected host properties safe defaults rather than required declarations.
  • Use qs.Ui components and semantic tokens. Import qs.Commons as Commons and qualify Commons.Color.*: Qt 6.12 adds a conflicting Color type. Keep the unqualified import too when using Style, Util or Border.
  • Use host motion components; route custom durations through Style.duration(ms) and stop looping animations under Style.reduceMotion. Inspect host support before using these newer tokens.
  • Keep hover/selection/open state per visual instance; share polling and remote state through a service where needed.
  • Set Text.PlainText for external text at every sink, including tooltips and nested delegates. Bound external data before displaying or saving it.
  • Launch commands with argument arrays. If a shell is necessary, quote external values with Util.shellQuote. Keep secrets out of display properties, logs and environment dumps.
  • Keep repeated network/process/storage policy in a narrow adapter with explicit errors and tests for its actual production path.

Load only relevant references: host injection and facades, theme/orientation/monitors, plugin translations, motion and reduced motion, process and state, or external-data review boundaries.

For a theme problem, fix the consumer or shared theme source that owns it. Verify affected behavior with fixtures and required repository checks; report Qt imports and live lifecycle as unrun unless observed on the target host.