LineCitrine supports AI-assisted work on plain-text layout algorithms in your project folder. Compare proposed break choices with explicit costs and keep Unicode code-point width separate from visual rendering.
def wrap_words(words, width):
words = tuple(words)
if type(width) is not int or not 1 <= width <= 80 or len(words) > 100:
raise ValueError("wrap.limit")
if any(type(w) is not str or not w or len(w) > width or any(c.isspace() for c in w) for w in words):
raise ValueError("wrap.word")
n = len(words)
costs, ends = [0] * (n+1), [0] * n
for i in range(n-1, -1, -1):
used, best = 0, None
for j in range(i, n):
used += len(words[j]) + (j > i)
if used > width:
break
cost = 0 if j == n-1 else (width-used)**2 + costs[j+1]
if best is None or cost < best:
best, ends[i] = cost, j+1
costs[i] = best
lines, i = [], 0
while i < n:
lines.append(" ".join(words[i:ends[i]]))
i = ends[i]
return lines| Review before applying | Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes. |
|---|---|
| Connection | Base URL, credentials and a reachable server. |
| Project | Test empty input and competing breaks, rejecting empty or oversized words without claiming terminal display width. |
def wrap_words(words, width):
words = tuple(words)
if type(width) is not int or not 1 <= width <= 80 or len(words) > 100:
raise ValueError("wrap.limit")
if any(type(w) is not str or not w or len(w) > width or any(c.isspace() for c in w) for w in words):
raise ValueError("wrap.word")
n = len(words)
costs, ends = [0] * (n+1), [0] * n
for i in range(n-1, -1, -1):
used, best = 0, None
for j in range(i, n):
used += len(words[j]) + (j > i)
if used > width:
break
cost = 0 if j == n-1 else (width-used)**2 + costs[j+1]
if best is None or cost < best:
best, ends[i] = cost, j+1
costs[i] = best
lines, i = [], 0
while i < n:
lines.append(" ".join(words[i:ends[i]]))
i = ends[i]
return linesLineCitrine offers a Windows coding workspace for developers working through output-formatting decisions with a connected AI model. A layout request becomes easier to review when it states what counts as a better result. Open the project folder and bring the formatter, its consumer and a representative input into the conversation before requesting a change.
One example asks for plain-text line breaks that minimize squared unused space while treating the last line separately. Define the allowed words, width limit and cost rule explicitly. Ask the model to compare candidate breaks against that objective. Keep code-point length distinct from displayed column width so the proposal does not quietly promise behavior beyond the chosen representation.
Review the suggested edit with competing layouts, an empty input and a word that exceeds the accepted width. Run the project's checks and calculate expected costs for the small examples you choose. The result should preserve words and meet the stated objective, not merely look balanced in one font. Include the consuming format if it imposes additional requirements.
A supported OpenAI-compatible or Anthropic endpoint supplies LineCitrine's model connection. Where unrestricted AI models are offered, you can select one using the required credentials. The model and server determine restrictions, context limits and tool support; the layout objective remains a requirement you define and verify.
State whether its unused space contributes to the cost. The illustrative objective excludes it, which can change the preferred breaks. Include a small example where that choice matters and compare the proposed output against the cost rule you actually intend.
Not generally. Combining marks and wide characters can display differently from their code-point count. Keep the measurement in your contract explicit. If terminal columns matter, define that separate requirement and review the necessary handling in your real rendering environment.
Use small inputs with a few competing break choices and compute their expected costs independently. Check that the proposal selects an allowed minimum under the stated rule. Then run broader project fixtures to look for changed behavior beyond those examples.
Specify whether the formatter rejects it, splits it or permits overflow. The example rejects words beyond the accepted width. Review that path and its caller so a layout edit does not silently introduce a different content transformation or error policy.
LineCitrine · Updated 2026-10-25