UIKit Horizontal-First Layouting

Generate ASCII previews before writing UIKit layout code.

1|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/arimunandar/claude-code-ios-plugin --skill uikit-horizontal-first-layouting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: UIKit Horizontal-First Layouting
Source: https://github.com/arimunandar/claude-code-ios-plugin/tree/main/skills/uikit-layouting
Command: npx skills add https://github.com/arimunandar/claude-code-ios-plugin --skill uikit-horizontal-first-layouting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill introduces a disciplined, ASCII-driven approach to UIKit layout design, ensuring visual planning precedes code and reducing subsequent rewrites.

Core Features & Use Cases

  • ASCII-first preview: Always generate an ASCII visualization of the screen layout before implementing constraints and views.
  • Horizontal slicing: Break screens into horizontal rows to simplify constraints and improve maintainability.
  • Stepwise implementation: Build each row top-to-bottom, with user confirmation before code generation.
  • Use Case: Designers and developers collaborating on a login or settings screen align on structure before writing UIKit code.

Quick Start

Draw the full ASCII preview of the target screen, detail each row's content and height, then confirm before generating UIKit code.

Frequently Asked Questions about UIKit Horizontal-First Layouting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan UIKit layouts before writing constraints?

Plan UIKit layouts by generating an ASCII preview of the screen before coding. This enforces visual planning, applies horizontal slicing to break screens into rows, and requires user confirmation prior to code generation to reduce rewrites.

What is horizontal slicing in iOS screen design?

Horizontal slicing is a layout design pattern that breaks iOS screens into top-to-bottom rows. It simplifies constraint configuration and improves maintainability for row-based UIKit views like login, settings, and detail screens.

How do I use ASCII previews for UIKit login and settings screens?

Draw the full ASCII visualization of the target screen, detail each row's content and height, and confirm the structure before generating UIKit code. This stepwise implementation builds each row top-to-bottom for clear alignment.

Does this ASCII layout approach work for complex iOS detail views?

Yes, the ASCII-first layout approach works for iOS detail views by enforcing a visual preview and horizontal slicing. It improves clarity for row-based layouts and requires explicit confirmation before generating the final UIKit constraints.

Why should I use ASCII visualization before coding UIKit constraints?

Use ASCII visualization before coding UIKit constraints to ensure visual planning precedes implementation. This disciplined design pattern reduces subsequent rewrites by aligning structure and row heights before any code is generated.

Can I generate UIKit code without confirming the ASCII layout first?

No, the layouting process requires explicit user confirmation of the ASCII preview before generating UIKit code. This stepwise implementation ensures the horizontal row structure and content heights are validated prior to coding.