원클릭으로 Manus에서 모든 스킬 실행

cross-platform-care

스타89

포크8

업데이트2026년 7월 7일 13:11

Write scripts and file handling that survive the machine they didn't develop on — path separators, shell dialects, line endings, case-sensitivity, missing tools. Use when writing shell scripts, CI steps, path manipulation, file I/O, or install/setup instructions others will run.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

adamentwistle

adamentwistle/fable-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

cross-platform-care

"Works on my machine" is an environment assumption you didn't notice making (see environment-first — this is its prevention side).

Build paths with the path library, never string concatenation with / or \: os.path.join/pathlib, path.join, filepath.Join. Same for home (~ doesn't expand everywhere), temp dirs (use the platform API — or the session's designated scratchpad), and current-dir assumptions (prefer absolute paths derived from a known root).
Know which shell your script actually targets. Bashisms ([[, arrays, set -o pipefail) fail in POSIX sh; zsh and bash differ on word splitting and globs; CI images may have dash as /bin/sh. Declare the shebang you mean and test with that shell.
Quote every variable expansion in shell ("$var", "$@"): unquoted expansion breaks on the first path with a space — which is every macOS user directory. Filenames can contain spaces, quotes, unicode, and leading dashes; -- before positional args guards the last one.
Case-sensitivity is a filesystem property: macOS is usually case-insensitive (so import utils finds Utils.py locally and dies on Linux CI); imports, includes, and asset references must match the file's real casing exactly.
Line endings and encodings: CRLF from Windows checkouts breaks shebangs and string comparisons; declare encoding explicitly when reading text (utf-8), don't inherit the platform default.
Don't assume tools exist or match: GNU vs BSD flags differ (sed -i, date -d vs -v, grep -P); check availability or use the portable subset. Version-check anything whose behavior you depend on.
Timezones on servers are UTC; laptops aren't. Code that depends on local time behaves differently in CI/production — be explicit about which zone every timestamp is in (see edge-case-sweep).

Test: "would this run on a fresh Linux CI container and on a macOS laptop with a space in the username?" Both, or state which one it targets.

이 저장소의 다른 Skills

같은 저장소

ambiguity-commit

adamentwistle/fable-skills

Resolve ambiguous requests by investigating, choosing the best-supported reading, and stating the interpretation — instead of guessing silently or blocking on questions. Use whenever a request has multiple plausible readings or an unstated parameter (which file, which env, how thorough, what format).

2026-07-0789

api-surface-care

adamentwistle/fable-skills

Treat any change to a public or shared interface — exported functions, HTTP endpoints, CLI flags, config formats, event/message schemas, DB schemas — as a contract change with consumers you can't see. Use before modifying anything other code depends on.

2026-07-0789

calibrated-recommendation

adamentwistle/fable-skills

When recommending between options, match the strength of the claim to the strength of the evidence — commit when evidence is clear, say it's a coin flip when it is. Use whenever the user asks "which should I use", "what's the best way", "A or B?", or you're proposing a design choice.

2026-07-0789

codebase-orientation

adamentwistle/fable-skills

Fast recon before changing unfamiliar code — instructions → manifest → tree → trace one flow end-to-end → git archaeology → imitate the newest precedent. Use when starting in a repo or module you haven't touched this session, or before designing against an existing architecture.

2026-07-0789

concurrency-reasoning

adamentwistle/fable-skills

Async/concurrent/streaming discipline — five questions (overlapping runs, check-then-act, mutation across await, response ordering, cancellation), idempotent retries, shared-state audit, race amplification. Use for async fan-out, streams/SSE, jobs, caches, or flaky timing-smell bugs.

2026-07-0789

context-checkpoint

adamentwistle/fable-skills

Externalize working state to files so long tasks survive context compaction and interruption. Use at the start of any task likely to exceed ~30 minutes or span many files, and again whenever a major phase completes or the plan changes.

2026-07-0789

name	cross-platform-care
description	Write scripts and file handling that survive the machine they didn't develop on — path separators, shell dialects, line endings, case-sensitivity, missing tools. Use when writing shell scripts, CI steps, path manipulation, file I/O, or install/setup instructions others will run.

cross-platform-care

"Works on my machine" is an environment assumption you didn't notice making (see environment-first — this is its prevention side).

Build paths with the path library, never string concatenation with / or \: os.path.join/pathlib, path.join, filepath.Join. Same for home (~ doesn't expand everywhere), temp dirs (use the platform API — or the session's designated scratchpad), and current-dir assumptions (prefer absolute paths derived from a known root).
Know which shell your script actually targets. Bashisms ([[, arrays, set -o pipefail) fail in POSIX sh; zsh and bash differ on word splitting and globs; CI images may have dash as /bin/sh. Declare the shebang you mean and test with that shell.
Quote every variable expansion in shell ("$var", "$@"): unquoted expansion breaks on the first path with a space — which is every macOS user directory. Filenames can contain spaces, quotes, unicode, and leading dashes; -- before positional args guards the last one.
Case-sensitivity is a filesystem property: macOS is usually case-insensitive (so import utils finds Utils.py locally and dies on Linux CI); imports, includes, and asset references must match the file's real casing exactly.
Line endings and encodings: CRLF from Windows checkouts breaks shebangs and string comparisons; declare encoding explicitly when reading text (utf-8), don't inherit the platform default.
Don't assume tools exist or match: GNU vs BSD flags differ (sed -i, date -d vs -v, grep -P); check availability or use the portable subset. Version-check anything whose behavior you depend on.
Timezones on servers are UTC; laptops aren't. Code that depends on local time behaves differently in CI/production — be explicit about which zone every timestamp is in (see edge-case-sweep).

Test: "would this run on a fresh Linux CI container and on a macOS laptop with a space in the username?" Both, or state which one it targets.