container-lines
Skill0 starsChanged 5 months agoApache-2.0View on GitHub
Add vertical container-size guide lines with mini corner squares for precise, structured web layouts. Use when asked for container lines, measured layout guides, vertical boundary lines, editorial grid markers, or small corner-square frame details.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- boraoztunc/skillsword for word, first seen Jun 11, 2026
Other versions1 project uses a version of this.
Word for word · 1
- boraoztunc/skills★ 454100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- vercel-react-best-practices/AGENTS.mdAGENTS.md
- adversarial-reviewSkill
- analytics-trackingSkill
- animejsSkill
- apple-designSkill
- app-store-screenshotsSkill
- beam-glow-statesSkill
- beautiful-shadowsSkill
- competitor-alternativesSkill
- conductor-rewrite-performanceSkill
- content-strategySkill
- contribute-catalogSkill
- copy-editingSkill
- copywritingSkill
- corner-diagonalsSkill
- css-animationsSkill
- css-border-gradientSkill
- documentary-brutalist-agencySkill
- editorial-portfolio-chaptersSkill
- emil-design-engSkill
- framed-grid-layoutSkill
- frontend-designSkill
- glass-dark-uiSkill
- gsapSkill
- hyperframes-cliSkill
- hyperframes-mediaSkill
- hyperframes-registrySkill
- hyperframesSkill
- impeccableSkill
- landing-pageSkill
- linear-local-first-architectureSkill
- liquid-metal-borderSkill
- lottieSkill
- make-interfaces-feel-betterSkill
- mesh-gradient-dark-blue-cleanSkill
- minimal-zine-posterSkill
- ogilvy-copywritingSkill
- operational-enterprise-aiSkill
- page-croSkill
- pricing-pageSkill
- product-proof-saasSkill
- programmatic-seoSkill
- progressive-blurSkill
- remotion-to-hyperframesSkill
- reveal-hover-effectSkill
- schema-markupSkill
- seo-auditSkill
- service-booking-flowSkill
- shaders-cursor-ripplesSkill
- skeuomorphic-uiSkill
- staggered-word-revealSkill
- stop-slopSkill
- tailwindSkill
- tailwind-v4Skill
- thinking-orbsSkill
- threeSkill
- typegpuSkill
- vercel-react-best-practicesSkill
- visual-style-presetsSkill
- waapiSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Keep lines thin: 1px with low opacity.
- Distinctive: line 16
Add mini squares at container corners or section intersections.
- Distinctive: line 17
Keep the line system consistent across sections.
- Distinctive: line 18
Place lines behind content but above the page background.
- Distinctive: line 34
Use pseudo-elements on the layout shell.
- Distinctive: line 64
Add four small squares to sections that need a precise measured feel.
- Distinctive: line 98
Use the same container width as the line positions.
- Distinctive: line 108
Use lines as structure, not decoration.
- Distinctive: line 109
Do not add lines to every nested component.
- Distinctive: line 111
Avoid bright accent colors unless the entire visual system is technical or industrial.
- Distinctive: line 112
Keep container max-width and padding shared between content and guide lines.
≈ “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.
Files
Container Lines
Use When
- A page needs subtle vertical guides that reveal the content container width.
- A hero, section, or product page feels too loose and needs structural tension.
- The design calls for mini corner squares, measured edges, or quiet technical framing.
Rules
- Draw lines at the left and right edges of the main content container.
- Keep lines thin:
1pxwith low opacity. - Add mini squares at container corners or section intersections.
- Keep the line system consistent across sections; do not change width per section.
- Place lines behind content but above the page background.
- Disable pointer events so the guides never block UI.
Base Tokens
:root {
--container-max: 1120px;
--container-pad: clamp(20px, 4vw, 48px);
--line-color: rgba(24, 24, 27, 0.14);
--line-strong: rgba(24, 24, 27, 0.28);
--corner-size: 6px;
}Page Container Lines
Use pseudo-elements on the layout shell.
.container-lines {
position: relative;
isolation: isolate;
}
.container-lines::before,
.container-lines::after {
content: "";
position: absolute;
top: 0;
bottom: 0;
z-index: -1;
width: 1px;
background: var(--line-color);
pointer-events: none;
}
.container-lines::before {
left: max(var(--container-pad), calc((100% - var(--container-max)) / 2));
}
.container-lines::after {
right: max(var(--container-pad), calc((100% - var(--container-max)) / 2));
}Corner Squares
Add four small squares to sections that need a precise measured feel.
.corner-squares {
position: relative;
}
.corner-squares > .corner {
position: absolute;
width: var(--corner-size);
height: var(--corner-size);
background: var(--line-strong);
pointer-events: none;
}
.corner.top-left { top: 0; left: 0; transform: translate(-50%, -50%); }
.corner.top-right { top: 0; right: 0; transform: translate(50%, -50%); }
.corner.bottom-left { bottom: 0; left: 0; transform: translate(-50%, 50%); }
.corner.bottom-right { right: 0; bottom: 0; transform: translate(50%, 50%); }<main class="container-lines">
<section class="corner-squares">
<span class="corner top-left"></span>
<span class="corner top-right"></span>
<span class="corner bottom-left"></span>
<span class="corner bottom-right"></span>
...
</section>
</main>Minimal Section Wrapper
Use the same container width as the line positions.
.content-container {
width: min(100% - (var(--container-pad) * 2), var(--container-max));
margin-inline: auto;
}Taste Rules
- Use lines as structure, not decoration. They should organize the page quietly.
- Do not add lines to every nested component; keep them at page or major-section level.
- Mini squares should be small and exact, usually
4pxto8px. - Avoid bright accent colors unless the entire visual system is technical or industrial.
- Keep container max-width and padding shared between content and guide lines.
Quick Checks
- The vertical lines align exactly with the content container edges.
- Corner squares sit on real container or section corners, not arbitrary positions.
- Lines remain subtle on light and dark backgrounds.
- Mobile still has enough padding between the line and content.
- Guides do not intercept clicks, hovers, or text selection.
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
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.

