菜单
Use when shell scripts (bash/PowerShell) print non-ASCII glyphs like checkmarks, X marks, or box-drawing rules that render as mojibake under Git Bash / Windows cp1252 terminals — replace runtime output with ASCII equivalents while leaving comments and remote heredocs untouched.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Use when implementing multiple related enhancements, or a large feature that must be split across risk boundaries, and you need to decide branch/PR structure. Covers accumulating related work on one shared branch with atomic commits per enhancement, splitting risky multi-PR features along risk seams, and safely handling a branch that has both committed and dirty (uncommitted) work when shipping.
Use when a rebase or merge reports conflicts on a file where both branches only appended or inserted new content (append-only logs, registries, holding-pen documents) rather than editing the same lines. Recognizes the conflict as a false signal and resolves it as a union-keep-both operation instead of a real semantic merge.
Use when reskinning an app with a real brand's visual identity — extract the actual palette from a live site's raw CSS (not markdown), recreate logo/icon assets programmatically with documented extraction rationale, and codify everything as versioned, named design tokens rather than one-off hardcoded values.
Use when building a skill, doc, or knowledge base for an existing internal service or codebase, or when asked to audit past sessions for recurring failures and gaps — mine prior Claude conversation transcripts instead of reverse-engineering from logs or current code alone.
基于 SOC 职业分类
| name | fleet-cp1252-mojibake-fix |
| description | Use when shell scripts (bash/PowerShell) print non-ASCII glyphs like checkmarks, X marks, or box-drawing rules that render as mojibake under Git Bash / Windows cp1252 terminals — replace runtime output with ASCII equivalents while leaving comments and remote heredocs untouched. |
| status | active |
| version | "2026-07-05T00:00:00.000Z" |
A fleet of scripts (bash .sh, PowerShell .ps1) emits Unicode symbols — ✓ ✗ ══ ── and similar — in runtime output (echo/printf/Write-Host statements, helper function bodies). Under Git Bash or any terminal defaulting to the Windows cp1252 code page, these bytes render as mojibake (garbled multi-byte sequences) instead of the intended glyph. Use this skill when auditing or migrating a script fleet's console output for cross-terminal safety, or when a pre-commit hook needs to enforce ASCII-only output going forward.
cat -A <file> to reveal non-printing/high-bit bytes inline, or perl -ne 'print if /[^\x00-\x7F]/' <file> to list only lines containing non-ASCII. Grep for the specific glyphs (✓, ✗, ═, ─) to find helper function definitions that emit them.✓ (success) → *✗ (fail) → x!══ (heavy rule) → ==── (light rule) → --awk line-range deletion when consolidating or replacing helper function definitions — this is content-agnostic (deletes by line number, not by pattern match) so it won't accidentally strip adjacent comments or unrelated code.cat -A / perl -ne non-ASCII scan across the whole file (or diff) and confirm every remaining non-ASCII byte is one of the three acceptable categories from step 1 — not new output that slipped through..ps1 files that blocks non-ASCII runtime output (PowerShell scripts are the easiest to lint automatically for this)..sh fleet code, fix manually during refactoring passes — no reliable static enforcement point was established, so treat every helper-consolidation touch as an opportunity to sweep for mojibake.awk line-range deletion is preferred over pattern-based deletion for removing whole helper blocks because it doesn't risk leaving orphaned braces/parens if the glyph pattern doesn't match every line of the block.cmd.exe); the same script may look fine when tested from a UTF-8 Linux terminal, which is why manual .sh reviews are necessary rather than relying on "it looked right when I tested it."✓ but missing ══ in the same helper) is a common miss caught only by the residual-byte scan.