Elysia Tools
Navigation
Workflow Playbook
Convert identifier-like text to a target naming convention, wrap it to a chosen line width, then align or pad the finished lines for readable plain-text output.
Hubs
This workflow is useful when rough identifiers or short text lines must become a consistent block for code, documentation, logs, or a plain-text table. Keep the original input, name the destination, and record the target case, line width, and whether whitespace may change. A clear contract prevents a formatting pass from silently changing the meaning of prose.
Use text-case-converter for identifier-like text. Choose camelCase, PascalCase, snake_case, kebab-case, or another supported mode according to the surrounding project. Do not use a case conversion as a general rewrite for prose. Review acronyms, numbers, punctuation, and mixed input after conversion, because a consistent mechanical result can still be wrong for one important name.
Run text-wrap after the naming pass. Preserve paragraph breaks when the output is meant to be read as prose, and use a hard word break only when the destination really has a strict width. Once the line boundaries are stable, choose text-left-aligner for labels, text-right-aligner for values that should share a right edge, or text-justifier when stretched spaces are acceptable in a multiword text block.
Choose text-pad when the requirement is not just an edge but an exact width or a deliberate fill character. Spaces are usually the least distracting choice for columns; dots, dashes, or zeros can be useful for separators or fixed-format values, but they should be part of the destination specification. Lines already at or beyond the target cannot be made shorter by padding.
Compare the final text with the original, check a short line, a long line, an acronym, a number, and a blank paragraph, then inspect the result in a monospaced view. The workflow is ready to hand off when the naming rule, line width, alignment edge, and padding behavior are all visible in the output and no unexpected content has been removed.
Workflow playbook
Separate identifier-like lines from prose, select the required target case, and run text-case-converter only on the part governed by that naming rule. Keep the original beside the converted result so an acronym or number that was normalized unexpectedly can be restored.
Pass the converted text to text-wrap and choose a line width that fits its destination. Preserve paragraph breaks for prose or lists; enable word breaking only when an overlong token must fit a hard limit, because breaking it changes how the text is read.
Use text-left-aligner for labels and prose, text-right-aligner for numeric values or suffixes that should share a right edge, and text-justifier for multiword lines where expanded spaces are acceptable. Keep the same target length across lines that belong to one column.
Use text-case-converter when the text represents identifiers or labels that must follow a naming contract. Skip it for prose whose capitalization carries meaning, and keep the original as the comparison point.
Use text-wrap to establish line boundaries for paragraphs and lists. For prose where stretching spaces is acceptable, choose text-justifier; for labels or values that must meet an edge, choose a left or right aligner instead.
Choose text-pad when every line needs an explicit target width, a selected fill character, or a center/justify mode. Use the side-specific aligners for a quick left or right placement when extra padding rules are simple.
Use text-pad when the output needs an explicit width or a fill character such as a space, dot, dash, or zero. Check lines that are already longer than the target, inspect whitespace at both edges, and compare the finished block with a representative original before delivery.