1,202 件 ・ 関連度順
概要と使いどころ
Publish and update a game on itch.io: create the project page and upload builds with the butler CLI (butler push) to named channels. Use for itch.io publishing, butler push, channel naming for Windows/macOS/Linux/HTML5, versioning uploads, or shipping a jam or release build to itch.io.
日本語の概要は準備中です。原文の説明を表示しています。
Build and ship Unity 6.3 LTS players: build settings and scenes, player/quality settings, the IL2CPP vs Mono scripting backend, managed code stripping, scripted BuildPipeline.BuildPlayer, and CI/headless builds. Use when configuring or automating a build, choosing a scripting backend, shrinking build size, or when the user mentions Unity build, player settings, IL2CPP, code stripping, or Addressables.
日本語の概要は準備中です。原文の説明を表示しています。
Package and ship an Unreal Engine 5 project: the Platforms menu Package Project flow, build configurations (Development vs Shipping), cooking content, packaging settings and the Game Default Map, and command-line builds with RunUAT BuildCookRun. Use when packaging a build, making a shipping build, cooking content, configuring packaging settings, or when the user mentions package Unreal, cook content, shipping build, or BuildCookRun.
日本語の概要は準備中です。原文の説明を表示しています。
Publish or update a game on Steam with Steamworks and SteamPipe: configure depots and packages, upload builds with steamcmd, set a build live on a branch, and run the release checklists. Use for Steam publishing, app_build.vdf/steamcmd uploads, depots, beta branches, or a store page release.
日本語の概要は準備中です。原文の説明を表示しています。
Run /scope to turn a product idea into a living, coarse scope in docs/scope/ and keep it current: plan a new product, plan the next slice, enroll one named feature, or run with no argument to reconcile after shipping and queue what is next. Seeds WHAT to build; /architect designs, /develop builds.
日本語の概要は準備中です。原文の説明を表示しています。
Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and ships iOS/macOS apps with XcodeGen, SwiftUI and SPM: Xcode build fixes, device deployment, Apple Developer signing/notarization, CI/CD pipelines. Use for XcodeGen project.yml setup, "Library not loaded @rpath" crashes, code-signing errors (Error -25294, adhoc fallback), or Electron notarization failures. Not for TCC permission dialogs (use macos-permissions) or disk cleanup (use macos-cleaner).
日本語の概要は準備中です。原文の説明を表示しています。
Builds and maintains Claude Code plugin marketplaces: converts a skills repo to spec-valid marketplace.json, adds/updates plugin entries, and migrates skills into or between suites. Use for marketplace.json, plugin distribution, one-click install, or "put these skills in a suite". Not for repo health audits (use marketplace-health-check) or cache reconciliation (use skill-governance).
日本語の概要は準備中です。原文の説明を表示しています。
Fixes broken line wrapping in Claude Code exported .txt conversation files — rebuilds tables, paragraphs, paths and tool calls hard-wrapped at a fixed width. Use for an export (YYYY-MM-DD-HHMMSS-*.txt) with broken tables, split paths, or mangled tool output, or "fix export" / "make export readable". Not for a live web conversation (use read-claude-web-conversation) or session history (use read-claude-code-history).
日本語の概要は準備中です。原文の説明を表示しています。
Build a beginner running plan from wherever you are to a real goal — first nonstop mile, 5K, or 10K — that builds up slowly enough to avoid injury. Use when asked for a couch to 5k plan, help me start running, train for a [distance], or a running plan for beginners. Produces a week-by-week walk/run progression to the goal, session detail, pacing and form basics, rest and cross-training, and an injury-prevention note — with a 'check with a doctor if you have health conditions' flag.
日本語の概要は準備中です。原文の説明を表示しています。
Wrap up a client project the right way — a clean handoff, a strong final impression, and the moves that turn a finished project into referrals and repeat work. Use when asked to wrap up a client project, offboard a client, end a client relationship well, or project handoff. Produces a closeout checklist (deliverables, access, final invoice, documentation), a handoff/wrap-up message, the referral/testimonial/repeat-work asks to make at the peak moment, a graceful process for ending an ongoing relationship, and how to leave the door open — so the ending builds your business instead of just stopping.
日本語の概要は準備中です。原文の説明を表示しています。
Design, improve, and review interfaces for websites, apps, dashboards, and components: explore distinct design directions, compare styles side by side, and refine visual hierarchy against real screenshots. Delivers comparison pages, design notes, mockups, or working interfaces. Use for new interface design, style comparison, visual polish, screenshot recreation, or interface review. Not for business logic, APIs, builds, or code cleanup without visible UI changes. If oil-ui-pro is installed, use oil-ui-pro instead. 设计、改进和评审网站、App、后台与组件的界面，完成设计方向探索、多风格同屏比较、视觉层级和基于实际画面的迭代；按请求交付对比页、设计说明、设计稿或可运行界面。当用户需要新界面设计、比较不同设计风格、视觉精修、截图还原或界面评审时使用。只负责设计判断，组件归属、数据流、状态正确性和测试等代码实现质量不在范围内。不用于纯业务逻辑、接口、构建部署、无界面行为变化的代码整理、单独绘制普通插画或操作现有网站。已安装 oil-ui-pro 时交给 oil-ui-pro。
日本語の概要は準備中です。原文の説明を表示しています。
Beginner-friendly end-to-end video creator for HyperFrames. Use when the user says "make a video", "create a video", "new video", "build a video", "video from scratch", "I want to make a video", "help me create a video", or when someone who's never used HyperFrames before arrives with a concept, script, or rough idea and wants a finished MP4. Interviews the user in one pass, then builds the full video with mandatory preview and visual-verification gates.
日本語の概要は準備中です。原文の説明を表示しています。
Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system. Output is live-ready — no review pass, no placeholder content, no prototype styling. Implements hub pages, section listings, article pages, and cross-linking for Blog, Guides, Learn, and Comparisons sections.
日本語の概要は準備中です。原文の説明を表示しています。
Mobile/web build pipeline: fastlane-first local builds, store submission, pre-submission checklists. Triggers: app, mobile, store submission, deploy app, fastlane, expo, react native, flutter.
日本語の概要は準備中です。原文の説明を表示しています。
Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to xcode-build-fixer, and re-benchmarking after changes. Use when a developer wants an end-to-end build optimization workflow, asks to speed up Xcode builds, wants a full build audit, or needs a recommend-first optimization pass covering compilation, project settings, and packages.
日本語の概要は準備中です。原文の説明を表示しています。
Use when positioning an American Educational Research Journal (AERJ) manuscript in the literature. AERJ readers span the whole field, so the paper must engage the literatures a general education-research audience expects and speak past its own subfield. Builds the positioning argument; it does not write the literature review for you.
日本語の概要は準備中です。原文の説明を表示しています。
Use when assembling the data and code deposit for an American Economic Review: Insights (AER: Insights) short-format manuscript to pass the AEA Data and Code Availability Policy and the AEA Data Editor's pre-publication reproducibility check. Builds the package and README; it does not run the analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the model setup, equilibrium concept, or proof architecture is the bottleneck for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript — the central skill for a theory-first paper. Builds the model to the AEJ: Micro bar (clean, general, well-motivated result); it does not check whether your theorem is correct.
日本語の概要は準備中です。原文の説明を表示しています。
Use when presenting results for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript — propositions, numerical examples, schematic theory figures, and empirical/experimental tables. Builds exhibits to AEA house norms; it does not derive the results (see aejmic-theory-model).
日本語の概要は準備中です。原文の説明を表示しています。
Use when an American Economic Journal: Applied Economics (AEJ: Applied) manuscript's headline estimate must be shown to survive specification, sample, and inference choices before submission or in an R&R. Builds the robustness suite a sophisticated referee expects; it does not establish the primary identification (aeja-identification) or format the exhibits (aeja-tables-figures).
日本語の概要は準備中です。原文の説明を表示しています。
Use when assembling the data and code replication package for an American Economic Journal: Applied Economics (AEJ: Applied) manuscript to pass the AEA Data and Code Availability Policy and the AEA Data Editor's pre-publication reproducibility check. Builds the openICPSR deposit and README; it does not run the analysis or write the paper.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the headline result of an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript must be shown stable across specification, sample, identification, and tuning choices. Builds the robustness program a macro referee will demand; it does not establish the primary identification or model (use aejmac-identification / aejmac-theory-model first).
日本語の概要は準備中です。原文の説明を表示しています。