split-layout-technical — Claude Code skill
Shapes a technical split-screen interface with framed panels, mono metadata and restrained type. Use it when visual content and supporting information need distinct areas.
npx skills add MengTo/Skills --skill split-layout-technical -a claude-codeWhat split-layout-technical does
This skill guides a full-page interface built around two clear panels. One panel carries the immersive or visual focus, while the other holds explanation, specifications, metadata, supporting content or navigation. Fine rules, inset boundaries, corner markers and measured spacing give each area its own frame.
For larger screens, it calls for flex-row, split columns or a two-panel grid. Smaller screens stack the panels vertically while keeping their roles separate. The default split ratio is 50/50, though a dominant side can take more room.
The type direction pairs quiet editorial headlines with monospaced labels for status text, coordinates and specifications. At least one panel should include a framed media, canvas or image surface. Filling both sides with equal density weakens the hierarchy.
What it helps with
- separate visual content from page specifications
- frame panels with inset rules and thin borders
- format status labels in monospaced text
- build compact specification rows with dividers
- stack a split layout on smaller screens
Example prompts for the agent
- Apply
split-layout-technicalto this page, with media on the left and specifications on the right. - Create a
split-layout-technicallanding page with framed panels and mono metadata. - Rework this screen into two distinct panels that stack on smaller screens.
How to install split-layout-technical
1Skills CLI (Vercel)
npx skills add MengTo/Skills --skill split-layout-technical -a claude-code2Manually: put the files in place
~/.claude/skills/split-layout-technical/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/split-layout-technical/
1Skills CLI (Vercel)
npx skills add MengTo/Skills --skill split-layout-technical -a codex2Manually: put the files in place
.agents/skills/split-layout-technical/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add MengTo/Skills --skill split-layout-technical -a cursor2Manually: put the files in place
.cursor/skills/split-layout-technical/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install MengTo/Skills split-layout-technical2Manually: put the files in place
.github/skills/split-layout-technical/SKILL.md1Skills CLI (Vercel)
npx skills add MengTo/Skills --skill split-layout-technical -a gemini-cli2Platform CLI
gemini skills install https://github.com/MengTo/Skills --path agent-skills/web-design/split-layout-technicalManually: put the files in place
.devin/skills/split-layout-technical/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add MengTo/Skills --skill split-layout-technical -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about split-layout-technical
How do I install split-layout-technical in Claude Code?
Run npx skills add MengTo/Skills --skill split-layout-technical -a claude-code, then run npx skills add MengTo/Skills --skill split-layout-technical -a claude-code again. The skill file is at ~/.claude/skills/split-layout-technical/SKILL.md.
What does split-layout-technical do?
It provides design direction for a technical two-panel page with fine frames, restrained typography, monospaced utility labels and embedded surfaces. It covers panel roles, spacing, framing and responsive behaviour.
How does the skill handle smaller screens?
It uses split columns, a two-panel grid or flex-row on larger screens. On smaller screens, the panels stack vertically and remain separate zones.
Source text
SKILL.md · MIT
--- name: split-layout-technical description: "Create a technical split-screen design system with dual panels, fine frame lines, mono metadata, quiet editorial typography, and premium inset surfaces." --- # Split Layout Technical Skill ## Use When - Create a technical split-screen design system with dual panels, fine frame lines, mono metadata, quiet editorial typography, and premium inset surfaces. ## Workflow ## Scope - Apply this as a full-page layout and design-system direction when the interface should be organized into two clear panels or halves. - Use it for product pages, showcases, portfolios, editorial-tech layouts, or concept presentations that benefit from a disciplined split-screen structure. - This is a layout system first: it should control framing, spacing, typography, metadata treatment, and panel behavior, not just add a vertical divider. ## Visual target - Build the page around a strong split layout, usually two equal or near-equal vertical panels on desktop, with each side carrying a distinct role. - One side should act as the hero or immersive focal panel, while the other side handles explanation, specs, metadata, supporting content, or navigation. - Use thin frame lines, inset boundary rules, tiny corner markers, and precise spacing so each panel feels like a technical display surface. - Pair quiet editorial typography with mono utility labeling so the system feels intelligent, architectural, and controlled. - Keep the palette restrained, with neutral surfaces and one selective accent color derived from the design rather than a hardcoded hue. ## Implementation guidance - Prefer `flex-row`, split columns, or a clear two-panel grid on desktop, then stack the panels vertically on smaller screens without losing the sense of separate zones. - Give each panel its own internal framing: inset vertical rules, edge offsets, corner squares, thin borders, or measured padding that creates a contained shell. - Use mono or utility text for top rails, metadata strips, labels, coordinates, system markers, specs, or status copy. - Main headlines should remain clean and confident rather than loud; support them with controlled tracking, restrained hierarchy, and generous spacing. - Feature one premium embedded surface inside at least one panel, such as a bordered media frame, canvas region, visualization area, or image window. - Let one panel feel denser and more informational while the other feels more visual, spatial, or atmospheric to create useful contrast. ## Recommended patterns - Left/right split hero: immersive artwork or media on one side, explanatory content and structured details on the other. - Technical rails: slim top labels, footer metadata, coordinates, version markers, timestamps, or publisher-style microcopy in mono. - Specification blocks: compact two-column facts, thin dividers, line-separated rows, and restrained tabular presentation. - Framed surfaces: gradient-border wrappers, inset shadows, clipped media windows, or dark technical canvases placed inside a quiet outer shell. - Panel asymmetry: keep the overall split balanced, but allow different content densities and vertical rhythms inside each half. ## Tuning knobs - Split ratio: use 50/50 by default, but shift slightly when one side needs more dominance. - Frame density: increase or reduce the number of inset rules, corner markers, and dividers depending on how technical the system should feel. - Typography mood: steer more editorial with larger serif-like display moments, or more product-technical with cleaner sans and mono emphasis. - Surface depth: tune border gradients, inset shadow strength, and internal panel contrast so embedded surfaces feel premium but not heavy. - Accent restraint: use the accent for active details, system cues, or focal content, not as a blanket color wash. ## Avoid - Generic two-column marketing layouts that lack structural framing and technical detail. - Overcrowding both panels equally so the split loses hierarchy and purpose. - Bright multi-color treatments that break the calm, technical tone. - Rounded playful UI patterns that fight the precise architectural layout. - Treating the split only as decoration instead of giving each half a distinct functional role.
© MengTo · MIT · MengTo/Skills