Keep comparison answers readable in a terminal about 100 columns wide. Limits Markdown tables to four columns with short phrases, and switches to lists or per-item headings when the content needs longer explanations.
Keep a Markdown table readable in a narrow terminal of about 100 display columns - a wide table or one carrying prose in its cells wraps into unreadable ragged rows. Always call read_skill for bundled:table-fit before emitting a Markdown table in a final answer, and load it as soon as the answer starts forming as a comparison, a mapping, a feature matrix, a pros-and-cons, an options rundown, or a per-item summary across several dimensions. Do not load it for a table already inside a file being edited, for code, data, or test fixtures that merely look tabular, for tables the user pasted for you to read, or for an answer with no table and no tabular shape forming.
Review the instructions the agent will receive before you install.
The answer is read in a terminal about 100 display columns wide. A table wider than that wraps every row, and wrapped rows lose the column alignment that made the table worth using. So a table only pays for itself when it stays narrow.
Two budgets, both hard:
If the content fits both, use the table. If it does not, do not shrink the font of the problem by abbreviating into unreadable shorthand, and do not let the table run wide. Switch shape instead.
Use one of these instead of a table. Neither is a lesser answer; for prose-heavy content they are the better one.
A list — when each item needs a sentence or two:
- **tokio** — the default. Widest ecosystem, work-stealing scheduler, heaviest
dependency tree. Pick it unless you have a specific reason not to.
- **smol** — small and readable. Fewer integrations, so you write more glue.
Short per-item headings — when each item needs several dimensions covered in prose:
### tokio
Maturity: production-default across the ecosystem.
Tradeoff: large dependency graph and a heavier compile.
### smol
Maturity: stable, much smaller surface.
Tradeoff: fewer ready-made integrations.
Count the dimensions the answer actually needs, then look at the longest value any cell would hold.
A mapping with short values on both sides — a key to its meaning, a type to its size, a flag to its effect — is the case tables are for. Keep those as tables.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a 3D object with three.js, inspect it from every angle in an interactive viewer, and download it as OBJ + MTL or GLB for use in other 3D applications.
Maintain a private task list with deadlines, next steps, waiting parties, and blockers. Update progress and dependencies, merge duplicate items, and archive closed tasks so ongoing commitments stay clear and easy to follow.
Coordinate a task from a verifiable goal through completion. Handle work directly or split independent tasks across separate agent sessions, track progress, verify results, and arrange pull request merging when included in the goal.
Create animated HTML pages with smooth scene transitions and playback controls. An editable timeline lets users adjust scene lengths and speeds, with fixed landscape or portrait layouts prepared for video export.
Review synced Apple Health records, including steps, heart rate, sleep, and workouts. Retrieve daily summaries or detailed samples for a chosen period, and check sync status and missing data before interpreting the results.
Create and edit Word documents and templates, reorganize text, replace images, and work with tracked changes or comments. Apply proper headings and lists, then render every page to check its appearance before delivery.