agentleFS
Sign inStart free
mocchaleramocchalera/mockup-to-code-skill/skills/design-copy-structure/SKILL.md

design-copy-structure

Skill0 starsChanged 4 months agoISCView on GitHub

Build copy hierarchy so words drive layout and rhythm. Use when writing or restructuring headlines, subheads, and microcopy for web pages.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write one decisive headline that frames the page.

    line 14
  2. Distinctive:

    Use it as the primary layout anchor.

    line 15
  3. Distinctive:

    Create short subheads that split the story into chapters.

    line 18
  4. Distinctive:

    Keep body copy minimal; use proof and visuals for detail.

    line 19
  5. Distinctive:

    Place breaks at semantic pivots to control breathing.

    line 22
  6. Distinctive:

    Use short final lines to leave an aftertaste.

    line 23
  7. Distinctive:

    Avoid vague or hedged language.

    line 27
  8. Distinctive:

    Keep line length and cadence intentional.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Copy Structure

Overview

Make copy the skeleton of the layout, not an afterthought.

Workflow

1) Define the core line

  • Write one decisive headline that frames the page.
  • Use it as the primary layout anchor.

2) Shape the hierarchy

  • Create short subheads that split the story into chapters.
  • Keep body copy minimal; use proof and visuals for detail.

3) Design Japanese line breaks and flow

  • Place breaks at semantic pivots to control breathing.
  • Use short final lines to leave an aftertaste.

4) Add contrast in tone

  • Mix bold statements with quiet supporting lines.
  • Avoid vague or hedged language.

Output expectations

  • Provide a copy hierarchy that maps to sections.
  • Keep line length and cadence intentional.

Resources

references/

  • references/copy-as-structure.md for templates and editorial rules.
  • references/jp-copy-flow.md for Japanese line-break prompts and cadence rules.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free