skills.rest
TbK0ng
TbK0ngCOMMUNITY
Explore all skills by this author →
GitHub

check-frontend

Identify frontend code violating Trellis frontend guidelines in modified files.

Updated Feb 23, 2026
Search Tags:#automation#ui#frontend#quality#guidelines#code-review#browser-testing
One-click install
npx skills add https://github.com/TbK0ng/mytrellis --skill check-frontend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-frontend
Source: https://github.com/TbK0ng/mytrellis/tree/main/.agents/skills/check-frontend
Command: npx skills add https://github.com/TbK0ng/mytrellis --skill check-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend code often drifts away from the team's enforced guidelines, causing inconsistent UIs and higher maintenance costs.

Core Features & Use Cases

  • Read and compare modified frontend files against the repository's guidelines at .trellis/spec/frontend/index.md.
  • Review relevant guideline files for components, hooks, state management, types, and overall quality guidelines, and report violations.
  • If UI behavior changes, perform a browser verification pass and surface follow-up items.

Quick Start

Run the frontend check on your latest changes to ensure they follow Trellis frontend guidelines.

Frequently Asked Questions about check-frontend

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

FAQPage Schema
How do I check if my frontend code follows project guidelines?▼

To check frontend code against guidelines, this process reads modified files and compares them against repository documentation at .trellis/spec/frontend/index.md. It then reports violations related to components, hooks, state management, and types.

What is automated frontend code review for UI changes?▼

Automated frontend code review for UI changes is the process of enforcing pre-checks, reading guideline docs, reporting style violations, and requiring browser verification when UI behavior changes. It ensures modified frontend files maintain consistent quality.

Do I need browser testing when modifying frontend components?▼

Yes, browser testing is required when modifying frontend components if the UI behavior changes. This process surfaces follow-up items and mandates a browser verification pass to ensure style enforcement and UI changes function correctly.

How do I verify modified frontend hooks and state management?▼

You verify modified frontend hooks and state management by applying this check to modified frontend files. It reviews relevant guideline files for these specific scenarios and reports any code that violates Trellis frontend guidelines.

Can I enforce quality guidelines for frontend types automatically?▼

Yes, you can enforce quality guidelines for frontend types automatically. This check identifies frontend code that violates guidelines, covering components, hooks, state management, and types by reading and comparing modified files against repository docs.

Related Skills

Explore More Software Engineering Skills→
Lin117-shygoLin117-shygo

check-frontend

Verify frontend code changes against repository guidelines and report violations.

Community
Basic
LuisUrrutiaLuisUrrutia

web-design-guidelines

Audit HTML/CSS/JS UI code against Web Interface Guidelines for accessibility and design consistency.

Community
Intermediate
Sir-chawakornSir-chawakorn
33

preview-mode

Preview code changes locally with browser automation and visual diff comparisons.

Community
Intermediate
sunLeeesunLeee

check-python-style

Validate Python code style, type hints, and Google-style docstrings.

Community
Intermediate