web

Enforce Phoenix LiveView and HEEx development conventions for maintainable web applications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ityonemo/pepper --skill web-ityonemo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web
Source: https://github.com/ityonemo/pepper/tree/main/.claude/skills/web
Command: npx skills add https://github.com/ityonemo/pepper --skill web-ityonemo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces best practices for Phoenix LiveView and HEEx development, ensuring cleaner, more maintainable, and performant web applications.

Core Features & Use Cases

  • Template Externalization: Mandates separate .html.heex files for all templates, improving code organization and editor support.
  • Modern HEEx Syntax: Promotes the use of :for and :if attributes over legacy பகுதிகளில் syntax for conciseness and performance.
  • Component Organization: Guides the structuring of reusable UI components with clear namespaces and design rules.
  • LiveView Routing Patterns: Advocates for parameter-based mode switching within single LiveView modules.
  • Form Handling: Enforces the use of Ecto changesets for robust and framework-aligned form management.
  • LiveComponent Patterns: Defines when and how to use LiveComponents for stateful UI sections, including communication strategies.
  • JavaScript Hooks Organization: Standardizes the organization of LiveView JavaScript hooks by domain for better maintainability.
  • Visual Debugging: Integrates headless Chrome for taking screenshots to debug visual and JavaScript-related issues.

Quick Start

Use the web skill to ensure all new LiveView code adheres to the documented conventions.

Frequently Asked Questions about web

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

FAQPage Schema
What are the best practices for organizing Phoenix LiveView components and templates?

Organize Phoenix LiveView components by externalizing templates into separate `.html.heex` files and structuring reusable UI components with clear namespaces and established design rules for maintainability.

How do I handle forms and changesets in Phoenix LiveView?

Handle forms in Phoenix LiveView by enforcing the use of Ecto changesets for robust, framework-aligned form management. This ensures data validation and state management remain consistent with established Elixir conventions.

When should I use LiveComponents instead of standard LiveViews in Phoenix?

Use LiveComponents in Phoenix for stateful UI sections that require isolated state management. Standard LiveViews are better for parameter-based mode switching within a single module, while LiveComponents define specific communication strategies.

Does Phoenix HEEx syntax support control flow attributes like if and for?

Phoenix HEEx syntax supports modern control flow through `:if` and `:for` attributes. These should be used over legacy syntax for better conciseness and rendering performance in web applications.

What is the best way to organize JavaScript hooks in a Phoenix LiveView application?

The best way to organize JavaScript hooks in a Phoenix LiveView application is by grouping them by domain. This standardization improves maintainability and keeps client-side logic aligned with server-side state.

How do I visually debug Phoenix LiveView JavaScript and rendering issues?

Visually debug Phoenix LiveView issues by integrating headless Chrome to take screenshots. This approach helps identify and resolve visual layout problems and JavaScript-related hook execution errors.