skills.rest
CaltexBevo
CaltexBevoCOMMUNITY
Explore all skills by this author →
GitHub

ihe-frontend

Enforces frontend governance rules and WCAG 2.1 AA compliance for Innovating Higher Ed website changes.

Updated Feb 5, 2026
Search Tags:#branding#accessibility#frontend#compliance#governance#wcag#design-system
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill ihe-frontend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ihe-frontend
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/ihe-frontend
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill ihe-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The frontend governance rules ensure every modification to pages, components, layouts, themes, navigation, footers, and accessibility features adheres to the official standards for Innovating Higher Ed (ihe-pulse).

Core Features & Use Cases

  • Central source of truth for frontend rules governing branding, structure, and accessibility.
  • Enforces consistent navigation, footer structure, and theming across the site, reducing drift.
  • Ensures WCAG 2.1 AA accessibility compliance and semantic markup for all pages and components.
  • Provides guardrails for critical pages (About, founder bios) and tool/order constraints, with extensibility via optional scripts/references/assets.

Quick Start

Consult ihe-frontend before implementing any frontend changes to ensure compliance with all governance rules.

Frequently Asked Questions about ihe-frontend

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

FAQPage Schema
How do I ensure WCAG 2.1 AA accessibility compliance for frontend components?▼

Frontend governance rules enforce consistent navigation, footer structure, and theming across the site to reduce drift. They act as a central source of truth for branding, structure, and accessibility before implementing any frontend changes.

What's the best way to govern branding and design-system compliance for website layouts?▼

Frontend governance rules enforce consistent navigation, footer structure, and theming across the site to reduce drift. They act as a central source of truth for branding, structure, and accessibility before implementing any frontend changes.

Does frontend governance apply to changes spanning themes, nav, and footer structures?▼

Frontend governance requires a SKILL.md entry and YAML frontmatter with name and description before implementing changes. Optional scripts, references, and assets can be specified to provide extensibility for critical pages and tool constraints.

When do I need to consult frontend governance rules for accessibility features?▼

Frontend governance validates WCAG compliance checks and semantic markup for critical pages like About and founder bios. It provides guardrails for tool and order constraints while ensuring accessibility features adhere to official standards.

What are the limitations of frontend governance for critical pages and tool constraints?▼

Frontend governance provides guardrails for critical pages like About and founder bios, with tool and order constraints limiting freeform modifications. Governance mandates specific requirements for YAML frontmatter and SKILL.md entries before sprint work proceeds.

Related Skills

Explore More Education & Research Skills→
sigitpoerwosigitpoerwo

template-skill

Define a reusable Claude skill entry with YAML frontmatter in SKILL.md.

Community
Basic
peopleforresterpeopleforrester
3

accessibility-checker

Audit web content for WCAG 2.1 AA accessibility issues and output a prioritized remediation report.

Community
Basic
roderikroderik
2

rams

Analyze UI components for WCAG accessibility and visual design issues.

Community
Basic
angelgarciasolorzanoangelgarciasolorzano

shadcn

Generate design system guidelines for Shadcn UI components with WCAG 2.2 AA compliance.

Community
Advanced