halt-review-en

Review HALT architecture compliance across routing, Templ↔HTMX, Atomic Design, Lit, and Go layers.

Updated May 3, 2026
One-click install
npx skills add https://github.com/ousiass/dotfiles --skill halt-review-en
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: halt-review-en
Source: https://github.com/ousiass/dotfiles/tree/main/.claude/skills/halt-review-en
Command: npx skills add https://github.com/ousiass/dotfiles --skill halt-review-en

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

HALT architecture reviews are hard to do consistently because they require cross-checking routing, template/component structure, build outputs, and security assumptions across multiple layers. This Skill helps you catch critical mismatches (like HTMX calling missing routes or Templ↔Lit attribute/API inconsistencies) before they reach production.

Core Features & Use Cases

  • HALT-focused project structure analysis: Locates Go backend layers, Templ component layers (atoms/molecules/organisms/pages/layout), Lit components, routing/handlers, and build config, then plans targeted checks.
  • Sequential HALT compliance review with severity: Runs dedicated checks for routing consistency, Templ↔HTMX connections, cross-layer consistency, HATEOAS rules, Atomic Design structure, Lit Web Components expectations, Go layered architecture, security, and build configuration.
  • Actionable report output: Generates a HALT review report using a shared template and outputs it to GitHub Issue (recommended), a local Markdown file, or directly to the console, including file paths and line numbers.

Quick Start

Run this skill in the target project directory to review the entire HALT codebase and produce a HALT architecture report.

Frequently Asked Questions about halt-review-en

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

FAQPage Schema
How do I verify HTMX and Templ integration consistency in my Go project?

Verify HTMX and Templ integration by running an architecture compliance review that cross-checks routing, template structure, and component APIs to catch mismatches like missing routes or attribute inconsistencies. It generates a report with file paths and line numbers.

How do I check Atomic Design component structure in a Lit and HTMX codebase?

Check Atomic Design structure by reviewing component layers such as atoms, molecules, organisms, pages, and layout to ensure correct hierarchy and cross-layer consistency. The review applies deterministic code-verified findings to validate component organization.

What is a HALT architecture compliance review?

A HALT architecture compliance review systematically verifies routing, Templ↔HTMX integration, Atomic Design components, Lit Web Components, Go layered architecture, security, and build outputs. It ensures correctness and maintainability across these interconnected layers.

Can I output architecture review results directly to GitHub Issues?

Yes, you can output architecture review results to GitHub Issues, a local Markdown file, or the console. The recommended approach generates actionable reports including specific file paths and line numbers for easy tracking.

How do I find security and HATEOAS rule violations in a Huma and Templ project?

Find security and HATEOAS violations by running sequential compliance checks that inspect Go layered architecture and routing rules. The review produces deterministic, code-verified findings to catch critical mismatches before production.

Does this work for projects using HTMX with Lit Web Components and Go?

Yes, this applies specifically to projects using HTMX with Atomic Design, Lit, and the Templ/Huma ecosystem. It requires a target project directory to analyze the entire codebase and produce a comprehensive architecture report.