Before you start
- A wrapper around the content you want to constrain.
- The existing padding and width rules.
- For direct mode: a global stylesheet and Node.js.
How to do it
- Identify the article or content wrapper rather than changing every element on the page.
- Use a reading-oriented width, such as 70ch, in the direct customizer.
- Keep horizontal padding so text does not touch the phone screen edge.
- Check long headings, code blocks, and tables for overflow.
Before & after
.article-body { max-width: 70ch; margin-inline: auto; }The reading column stays centered and comfortable on desktop while still fitting a small screen.
Use with an AI coding tool
1 Describe your change
Use your own words. You do not need a file name. The prompt asks the AI to preserve unrelated work.
We remember this choice on this device. Choosing a tool does not connect it to this website.
2 Copy your prompt
Read the complete prompt below, then copy it.
3 Paste into your AI coding tool
Open your website or app project in your AI coding tool. Paste this into its AI chat box and send it. The tool needs access to your project files to make changes.
A website address alone does not give an AI permission or access to edit it. This prompt goes into an AI chat, not a regular terminal window.
4 Check the result
Check desktop line length, centered layout, and small-screen overflow.
Open your project preview and try the change. Review what changed before publishing. If it is wrong, use your tool’s undo or restore your saved project version.
If the result is not what you expected
The page still overflows
A child with a fixed width can escape the wrapper. Inspect that child separately.
Everything became too narrow
Use an article-specific selector instead of the overall app shell.
Undo the change
Restore the previous max-width and margin rules, or remove the direct override.
References & testing
The examples above explain the expected behavior; they are not a claim that this prompt has been tested in every framework or AI model. The direct tool uses our shared local-edit engine; native Windows execution remains unverified.