ワンクリックでManusで任意のスキルを実行

grokbuild-dev

スター19

フォーク3

更新日2026年7月6日 11:22

Builds, runs, and tests the GrokBuild macOS SwiftPM app. Use when developing GrokBuild, running make targets, fixing build failures, or working on SwiftUI/AppKit UI in this repo.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

rimusz

rimusz/grok-build-desktop

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

GrokBuild development

Quick start

make run          # build release + launch via open
make test         # swift test
swift build       # debug build
xed .             # open Package.swift in Xcode (optional)

Before UI work

Read ARCHITECTURE.md for file layout.
Prefer make over ad-hoc xcodebuild (no .xcodeproj).
After Swift changes, run swift build or make build.

Definition of done (every code change)

Do not finish a task with code-only diffs. Same session:

make test — must pass; add tests in Tests/GrokBuildTests/ for behavior you changed.
Computer Use — required for every code change, not only SwiftUI view edits. make run to repackage/relaunch (not just make build), then drive the app (snapshot → navigate to affected state → click/type → screenshot when helpful). Default: user-grokbuild-computer-use MCP; fallback: agent-desktop directly or Orca computer-use CLI. Service/persistence changes still need a live check of the user-visible outcome.
ARCHITECTURE.md — update source map, persistence, notifications, or common tasks → files when structure/flow changes.
README.md — update when users would notice the change.
BUILDING.md — update when build/packaging/scripts change.
Skills/rules — update relevant .cursor/skills/ or .cursor/rules/ if workflow changed.

Full checklist: .cursor/rules/docs-and-tests.mdc.

Common tasks

Task	Command
Package .app	`make app` → `dist/GrokBuild.app`
DMG	`make dmg`
Clean	`make clean`
Unit tests	`make test`

grok CLI dependency

App requires grok on PATH or at ~/.grok/bin/grok. User must run grok login. Test CLI: grok --version.

Architecture reminders

Process: GrokProcess + ChatStore
Workspaces: WorkspaceStore + SessionLayoutStore
Menu bar: StatusBarController + AppDelegate
Full map: ARCHITECTURE.md
Do not commit unless the user asks.

このリポジトリの他の Skills

同じリポジトリ

grokbuild-grok-cli

rimusz/grok-build-desktop

Works with grok CLI integration in GrokBuild — auth state, version checks, session resume, permission settings, and bundled browser skill. Use when changing GrokProcess, GrokCLIService, UpdateChecker, or grok-related settings UI.

2026-07-2419

grokbuild-grok-web

rimusz/grok-build-desktop

Drives grok.com web through Browser Control tools — chat, Imagine, skills, and connectors — then continues the task locally. Use when the user asks to use grok.com features that the grok CLI does not expose (Imagine, web-only skills/connectors), or to combine a grok.com web answer with local Computer Use/file work.

2026-06-2919

grokbuild-release

rimusz/grok-build-desktop

Versions, packages, signs, notarizes, and publishes GrokBuild GitHub releases. Use when bumping VERSION, running make release, editing release.yml, or helping with codesigning/notarization.

2026-06-2919

grokbuild-desktop

rimusz/grok-build-desktop

Develops the GrokBuild macOS app in this repository. Use when editing Swift/SwiftUI code, Makefile packaging, release scripts, About/Update panels, or grok CLI integration in grok-build-desktop.

2026-06-2919

grokbuild-computer-use

rimusz/grok-build-desktop

Guides GrokBuild desktop automation through Computer Use MCP tools. Use when the user asks to inspect or control native macOS apps, menus, dialogs, forms, Safari, Finder, or system UI through agent-desktop.

2026-06-2519

grokbuild-browser-control

rimusz/grok-build-desktop

Guides GrokBuild browser automation through agent-browser MCP tools. Use when the user asks to open websites, inspect pages, click/type in a browser, use managed internal Chrome, attach to existing Chrome/Chromium, or debug browser-control setup.

2026-06-2219

GrokBuild development

Quick start

make run # build release + launch via open make test # swift test swift build # debug build xed . # open Package.swift in Xcode (optional)

Before UI work

Read ARCHITECTURE.md for file layout.

Prefer make over ad-hoc xcodebuild (no .xcodeproj).

After Swift changes, run swift build or make build.

Definition of done (every code change)

Do not finish a task with code-only diffs. Same session:

make test — must pass; add tests in Tests/GrokBuildTests/ for behavior you changed.

Computer Use — required for every code change, not only SwiftUI view edits. make run to repackage/relaunch (not just make build), then drive the app (snapshot → navigate to affected state → click/type → screenshot when helpful). Default: user-grokbuild-computer-use MCP; fallback: agent-desktop directly or Orca computer-use CLI. Service/persistence changes still need a live check of the user-visible outcome.

ARCHITECTURE.md — update source map, persistence, notifications, or common tasks → files when structure/flow changes.

README.md — update when users would notice the change.

BUILDING.md — update when build/packaging/scripts change.

Skills/rules — update relevant .cursor/skills/ or .cursor/rules/ if workflow changed.

Full checklist: .cursor/rules/docs-and-tests.mdc.

Common tasks

Task

Command

Package .app

make app → dist/GrokBuild.app

DMG

make dmg

Clean

make clean

Unit tests

make test

grok CLI dependency

App requires grok on PATH or at ~/.grok/bin/grok. User must run grok login. Test CLI: grok --version.

Architecture reminders

Process: GrokProcess + ChatStore

Workspaces: WorkspaceStore + SessionLayoutStore

Menu bar: StatusBarController + AppDelegate

Full map: ARCHITECTURE.md

Do not commit unless the user asks.

name	grokbuild-dev
description	Builds, runs, and tests the GrokBuild macOS SwiftPM app. Use when developing GrokBuild, running make targets, fixing build failures, or working on SwiftUI/AppKit UI in this repo.