Formatting Tables & Diagrams

Standardize Markdown tables and Unicode diagrams with enforced formatting rules.

48|18|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/pageel/para-workspace --skill formatting-tables-diagrams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Formatting Tables & Diagrams
Source: https://github.com/pageel/para-workspace/tree/main/templates/common/agents/skills/formatting
Command: npx skills add https://github.com/pageel/para-workspace --skill formatting-tables-diagrams

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill prevents misaligned, hard-to-read tables and diagrams by enforcing consistent formatting rules for AI-generated artifacts.

Core Features & Use Cases

  • Markdown table formatting with strict alignment, padded columns, and URL reference-linking for long values.
  • Unicode box diagrams and hierarchy/flow templates to ensure consistent visual structure across renderers.
  • Tree listings, comparison tables, and status icon conventions to standardize how project artifacts communicate structure and state.
  • Applies to ALL artifacts including plans, backlogs, brainstorms, docs, and session logs.

Quick Start

Use the formatting patterns to produce a tables-and-diagrams section that includes a properly padded comparison table and a Unicode flow diagram in a text code block.

Frequently Asked Questions about Formatting Tables & Diagrams

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

FAQPage Schema
How do I fix misaligned Markdown tables in my documentation?

To fix misaligned Markdown tables in documentation, apply strict formatting rules like equal-width padded columns and bounded cell lengths. This standardization ensures visual structure stays consistent and scannable across different renderers.

What is the best way to format Unicode box diagrams for project planning?

The best way to format Unicode box diagrams for project planning is using Unicode-only characters within text code blocks. This approach prevents renderer inconsistencies and enforces a consistent visual structure for flows and hierarchies.

Why do my Unicode tree diagrams break across different Markdown renderers?

Unicode tree diagrams break across Markdown renderers when non-standard characters or unbounded spacing is used. Enforcing Unicode-only diagram characters and placing them inside text code blocks ensures they render cleanly everywhere.

Does this Markdown table formatting approach work for comparison layouts?

Yes, this Markdown table formatting approach works for comparison layouts by enforcing equal-width padded columns. It standardizes how project artifacts communicate structure and state, keeping comparison tables aligned.

What are the limitations of using Unicode for text-based diagrams?

A limitation of using Unicode for text-based diagrams is that visual structure relies entirely on strict character spacing. You must enforce bounded cell lengths and required code-block placement to prevent misalignment and maintain scannability.