build
- Repo stars 357
- License GPL-2.0
- Author updated Live
- Author repo woocommerce-ios
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @woocommerce · GPL-2.0
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: build
description: Build the WooCommerce iOS project Run the build command: bundle exec fastlane buildfortesting 2>…
category: engineering
runtime: no special runtime
---
# build output preview
## PART A: Task fit
- Use case: Build the WooCommerce iOS project Run the build command: bundle exec fastlane buildfortesting 2>&1 | tail -50 If the build fails: If the build succeeds, report success. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Build the WooCommerce iOS project Run the build command: bundle exec fastlane buildfortesting 2>&1 | tail -50 If the build fails: If the build succeeds, report success. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/simulator`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: build
description: Build the WooCommerce iOS project Run the build command: bundle exec fastlane buildfortesting 2>…
category: engineering
source: woocommerce/woocommerce-ios
---
# build
## When to use
- Build the WooCommerce iOS project Run the build command: bundle exec fastlane buildfortesting 2>&1 | tail -50 If the b…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "build" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Build the WooCommerce iOS project.
Run the build command:
bundle exec fastlane build_for_testing 2>&1 | tail -50If the build fails:
- Analyze the error output — look for compilation errors, identify file and line
- Check if it is a missing import, type mismatch, syntax error, or stale generated code
- If stale codegen, run:
bundle exec rake generate - If
Unable to find a device matching— use the/simulatorskill to discover an available simulator, then retry - Suggest or apply the fix
If the build succeeds, report success.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review