메뉴
Guides Rust binary size reduction for ccusage. Use when changing the rust/Cargo.toml release profile, dependency features, native packaging size, or investigating executable bloat with cargo bloat.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/TuYv/ccpm --skill rust-binary-size명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分
Use when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix — message-matched to the destination landing page. Not for scoring an ad account — use ad-account-auditor; not for the post-click page — use landing-optimizer; not for organic articles — use content-writer. 广告创意/广告文案/RSA标题
Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试
SOC 직업 분류 기준
SKILL.md 표시 중
| name | rust-binary-size |
| description | Guides Rust binary size reduction for ccusage. Use when changing the rust/Cargo.toml release profile, dependency features, native packaging size, or investigating executable bloat with cargo bloat. |
| paths | ["rust/Cargo.toml","rust/**/*.rs","rust/**/*.toml","apps/ccusage/scripts/**"] |
| globs | rust/**/*.rs,rust/**/*.toml,apps/ccusage/scripts/** |
https://github.com/johnthagen/min-sized-rust
[profile.release] in rust/Cargo.toml already applies the min-sized-rust
settings, including a separate opt-level for dependencies. Read it before adding
anything, and change it only when a measurement argues for it.
What ends up in a published platform package is the single bin/ccusage staged by
the Nushell scripts in apps/ccusage/scripts/, so packaged size tracks the binary
almost exactly. The development skill covers that packaging seam.
Measure before editing code or dependencies:
direnv exec . cargo build --manifest-path rust/Cargo.toml --release --bin ccusage
ls -lh rust/target/release/ccusage
When the release profile does not explain a regression, look at feature flags
(cargo tree -e features -p ccusage) and large symbols (cargo bloat --release --bin ccusage --crates), both against the same manifest. cargo bloat is not in
the dev shell; the missing-tools skill covers running it without a flake change.
Low-risk first: drop unnecessary dependency default features once tests show they are unused, narrow optional features rather than swapping a well-fitting crate, and remove dead release-only code paths or assets. CLI behavior, JSON output, table output, and packaging semantics stay unchanged unless the user asks otherwise.
These are opt-in experiments, appropriate only when the user asks for an aggressive
minimum-size push: nightly-only flags (-Zlocation-detail, -Zfmt-debug,
panic=immediate-abort, build-std), #![no_std]/#![no_main] with manual stdio,
binary packers such as UPX, and prefer-dynamic linking.
For release-profile or packaging changes, rebuild the native CLI, compare against
the earlier measurement, and record the command and result in the PR body or review
reply. Repo-wide format and test recipes are in the development skill.