mcpbeat Sign in

Dart Multiline Strings Agent Skill

|- Guidelines and best practices for refactoring consecutive prints, single-line string concatenations, and complex output blocks into triple-quoted multi-line string literals (''' or """) in Dart.

996 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
139
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kevmoo/dash_skills --skill dart-multiline-strings

The instruction itself

12 sections, as written by the author

Dart Multi-line Strings

1. When to use this skill

Use this skill when:

  • Refactoring consecutive print() or stdout.writeln() statements into a

single, cohesive output block.

  • Simplifying string literals that span multiple lines, contain embedded

newlines (\n), or use nested indentations.

  • Formatting large user-facing text output (like CLI help menus, reports, or

templated messages) to be readable, maintainable, and performant.

Discovery

To find candidate code blocks for multi-line string refactoring:

  • Look for multiple back-to-back print() or stdout.writeln() calls inside

a function, especially inside loops, console views, or CLI controllers.

  • Look for single-line strings heavily loaded with \n escape sequences.
  • Look for multiple string concatenations using the + operator or adjacent

string literal splits that are meant to represent multi-line outputs.

2. Guidelines

Combine Consecutive Outputs

Instead of calling print() repeatedly for a multi-line output, group the

contents into a single triple-quoted string literal: print('''...''').

Explicit and Clean Alignment

In a triple-quoted literal, the exact spacing and formatting inside the quotes

are preserved. Use this to specify indentation levels visually instead of using

manually padded space prefixes (e.g., ' ').

Remove Empty Print Calls

If there are empty print() or print('') statements serving as vertical

separators between output segments, replace them by letting the trailing

newline of a multi-line string block handle the separation naturally.

Handling the First Newline

If the opening triple-quote is immediately followed by a newline, the compiler

discards it.

  • If you do not want a leading blank line, start the string content on a

fresh line in the source code for clean layout.

  • If you do want a leading blank line in the output, leave an extra empty

line inside the triple-quoted block, or use \n explicitly at the

beginning:

    print('''

    This starts with one blank line above it.''');

80-Character Line Limit Exemption

The lines_longer_than_80_chars lint rule automatically ignores lines inside

multiline string literals. You can write long lines inside triple-quotes without

triggering linter warnings or being forced to break them up.

Dynamic Switch Expressions inside Interpolation

Leverage Dart 3 switch expressions directly inside string interpolations to

dynamically select and inject optional lines, conditional labels, or helper

instructions. This avoids cluttering the surrounding code with imperatively

constructed strings or multiple if statements:

print('''
Status: ${status.isSuccess ? 'PASS' : 'FAIL'}
${switch (status) {
  Status.failed => 'Error details: $errorMessage',
  _ => '',
}}''');

3. Examples

Refactoring Consecutive Prints with Indentation

Avoid:

void printGerritView(String branch, String desc, bool hasConflicts) {
  print('Branch Details:');
  print('    Name:        ' + branch);
  print('    Description: ' + desc);
  print('');
  if (hasConflicts) {
    print('    WARNING: This branch has conflicts.');
    print('    Run `git merge origin/main` to resolve.');
  }
}

Prefer:

void printGerritView(String branch, String desc, bool hasConflicts) {
  print('''
Branch Details:
    Name:        $branch
    Description: $desc
${hasConflicts ? '''
    WARNING: This branch has conflicts.
    Run `git merge origin/main` to resolve.''' : ''}''');
}

Other skills for the same job

different authors, same section of the catalogue
Receiving Code Review
by ZhanlinCui
×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens
Requesting Code Review
by ZhanlinCui
×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

2k tokens
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Karpathy Guidelines
by hyyhf
×3

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

629 tokens
Code Reviewer
by google-gemini
vendor ×2

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

795 tokens
Agent MD Refactor
by softaworks
×2

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

4k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take kevmoo/dart-multiline-strings from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.