amw-text-visual-cheatsheets

Generates validated ASCII CLI cheat-sheet panels with cross-platform command columns.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-webdesign --skill amw-text-visual-cheatsheets-emasoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amw-text-visual-cheatsheets
Source: https://github.com/Emasoft/ai-maestro-webdesign/tree/main/skills/amw-text-visual-cheatsheets
Command: npx skills add https://github.com/Emasoft/ai-maestro-webdesign --skill amw-text-visual-cheatsheets-emasoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams waste time hunting through docs for the right CLI command for their platform, and README command tables quickly become stale, misaligned, or missing Windows variants. This Skill produces portable, fixed-width ASCII cheat-sheet panels for tools like gh, git, kubectl, and deploy scripts that embed cleanly in READMEs, PR descriptions, and terminal help output. ## Core Features & Use Cases - Cross-platform command grids: One row per action with side-by-side macOS/Linux (bash/zsh) and Windows (PowerShell/CMD) columns, left-aligned and fixed-width. - Safety and structure conventions: Destructive commands are starred with footnote caveats, placeholders use <...> brackets with a legend, and multi-workflow command sets are split into per-category sections. - Mandatory validation gate: Every panel must pass amw-validate-ascii.py before delivery, enforcing the 100-column README / 80-column terminal width ceilings and exact column alignment. - Use Case: Ask for an ASCII cheat sheet for your team's gh workflow, and receive validated panels split into Setup, Daily Workflow, and Deploy sections with a last-tested footer, ready to paste into your README. ## Quick Start Ask the assistant to create an ASCII cheat sheet for the gh CLI covering setup, daily workflow, and deploy commands with macOS and Windows variants.

Frequently Asked Questions about amw-text-visual-cheatsheets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an ASCII cheat sheet for CLI commands?▼

Provide your command categories, the commands per platform, and any notes on flags or prerequisites. The skill drafts fixed-width panels grouped by workflow stage, then validates each one with amw-validate-ascii.py before presenting it in a fenced code block.

How do I document commands for both macOS and Windows in a README?▼

Use a side-by-side platform table with one row per action and separate columns for macOS/Linux bash and Windows PowerShell. Columns are sized to the longest cell plus two spaces of padding, and identical commands still appear in both columns for parity.

What is the maximum width for an ASCII table in a GitHub README?▼

The width ceiling is 100 columns for GitHub READMEs and 80 columns for terminal --help output. If a long command blows past the limit, define a shell variable at the top of the panel and reference it in each cell.

Can this skill generate HTML or SVG cheat sheets?▼

No, output is strictly ASCII text panels with no HTML or SVG. If you need a styled web page, the skill routes you to shadcn/ui, Tailwind, or ascii-to-html skills, treating the ASCII panel as the source of truth.

How are destructive commands marked in a CLI cheat sheet?▼

Destructive commands get a `*` prefix on the action name plus a footnote below the table explaining the risk and guardrail, such as recommending --force-with-lease for force pushes. Dry-run flags are included when the tool supports them.

Why does the ASCII panel validation fail?▼

Validation fails on misaligned columns, tabs, emoji, variable-width glyphs, or exceeding the width ceiling. Apply each FIX hint from amw-validate-ascii.py and re-run until it passes; the table mode of amw-ascii-render.py guarantees alignment for large panels.