readable-text-formatting
This skill should be used whenever generating markdown tables, ASCII art, text-based diagrams, box-drawing layouts, or any formatted text intended for raw monospace reading. Applies automatically — no user trigger needed. Ensures column alignment, border consistency, and proper padding.
What this skill does
# Readable Text Formatting Ensure all generated formatted text is human-readable in raw monospace form. This applies to markdown tables, ASCII diagrams, and any text with visual structure. ## Core Principles 1. **Alignment is for human readers** — raw `.md` files should be scannable in a text editor 2. **Consistent column width** — each column padded to the longest content in that column 3. **Border alignment** — all vertical and horizontal boundaries align perfectly ## Markdown Tables ### The Problem ```markdown | Name | Age | Occupation | |---|---|---| | Alice | 30 | Software Engineer | | Christopher | 45 | Product Manager | ``` ### The Solution ```markdown | Name | Age | Occupation | |-------------|-----|-------------------| | Alice | 30 | Software Engineer | | Christopher | 45 | Product Manager | ``` ### How to Create Aligned Tables **Step 1: Determine column widths** — for each column, find `max(header_length, max(all_data_lengths))`. **Step 2: Pad all cells** — add trailing spaces to reach the column width. **Step 3: Create separator** — fill with dashes matching the column width exactly. ## ASCII Diagrams ### The Problem ``` ┌─────────────┐ │ Title Here │ │ Some content that is longer │ └─────────────┘ ``` ### The Solution All borders must align vertically: ``` ┌──────────────────────────────┐ │ Title Here │ │ Some content that is longer │ └──────────────────────────────┘ ``` ### How to Create Aligned Diagrams **Step 1: Find maximum content width** — the longest line inside the box. **Step 2: Calculate border width** — `content_width + 2 (padding) + 2 (border chars)`. **Step 3: Build each line**: - Top: `┌` + dashes + `┐` - Content: `│` + text + padding + `│` - Bottom: `└` + dashes + `┘` ## Self-Check Before Output Before finalizing any formatted text, verify: 1. **Visual alignment** — all vertical lines align, all horizontal lines are continuous 2. **Width consistency** — every row/line has the same total width 3. **Border integrity** — top and bottom borders match width, left and right borders align on every line ## Best Practices - **Monospace mental model**: assume output is viewed in a monospace font - **Measure first**: calculate all widths before generating text - **Default to ASCII-safe**: if Unicode box-drawing might cause issues, use `+`, `-`, `|` - **Test with longest content**: dimensions based on the widest content ## References - **ASCII patterns, character sets, common mistakes, advanced examples**: `references/patterns-and-examples.md`
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.