القائمة
Create a 1-2 page cheat sheet / quick reference for a tool, language, or framework.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | cheat-sheet |
| description | Create a 1-2 page cheat sheet / quick reference for a tool, language, or framework. |
| argument-hint | <topic> [--pdf] [--output <path>] |
| allowed-tools | Read, Write, WebSearch, WebFetch, Task, AskUserQuestion, Skill |
| disable-model-invocation | true |
Create concise, high-quality cheat sheets for any tool, technology, language, framework, or concept. Output a practical 1-2 page reference document focusing on the most commonly used commands, features, and key information users look up repeatedly.
$ARGUMENTSExtract from the arguments:
--pdf flag or user requests PDF)--output specified), otherwise save to the current working directoryIf the topic is ambiguous or too broad, use AskUserQuestion to clarify scope. For example, "Git" could mean basic commands, advanced workflows, or configuration — ask which aspect to focus on.
Conduct focused research to identify the most practical, commonly-referenced information.
Prioritize sources that reveal the most commonly used features, typical workflows, and critical gotchas.
Before writing, distill the research into a concrete plan:
Follow the formatting guidelines in references/formatting-guide.md for structure templates, entry formatting rules, length targets, content priorities, and exclusion rules.
Key principles:
Save the cheat sheet as a markdown file:
<topic>-cheat-sheet.md (kebab-case)--output specifiedWhen the user requests PDF output (via --pdf flag or explicit request):
latex skill to create the cheat sheet as a .tex filereferences/formatting-guide.md (compact margins, small font, two-column layout, reduced spacing)references/formatting-guide.md — Detailed formatting rules, section templates, and examples of well-structured cheat sheet entriesAdd terms, context, or instructions to Shama voice-to-text files for clipboard mode (Ctrl+Opt+Space) or shell-command mode (Ctrl+Opt+S), at project or global level.
Initialize Shama voice-to-text config for the project — create voice.json, voice-vocabulary.md, voice-context.md, and register the project in Shama's registry.toml.
Reflect on codebase navigation effectiveness at end of conversation. Surfaces dead ends, inefficiencies, missing context. Does not write files — pair with /kiro:steering-custom to persist.
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.