pos-frontend

Audit frontend interfaces for accessibility, consistency, and UX gaps.

8|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill pos-frontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pos-frontend
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/pos-frontend
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill pos-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend teams struggle with inconsistent UI, outdated design tokens, and fragmented UX analysis across projects. pos-frontend consolidates UI audits, design-system upgrades, and UX analysis with persistent design-token memory to unify quality.

Core Features & Use Cases

  • Frontend audit: accessibility, responsiveness, interactions, and performance checks.
  • Design system upgrade: token alignment, components, patterns for consistency.
  • UX analysis: user flows, journeys, and mockups with memory of past learnings.

Quick Start

Run an end-to-end frontend health check by auditing a target UI, upgrading the design tokens, and performing a UX analysis for a new feature.

Frequently Asked Questions about pos-frontend

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

FAQPage Schema
How do I perform a frontend audit for accessibility and UI consistency?

A frontend audit checks target interfaces for accessibility, responsiveness, interactions, and performance gaps to identify UI health issues. This process flags inconsistencies and fragmented UX patterns across the codebase for remediation.

How do I upgrade my design system tokens and component patterns?

Design system upgrades align outdated design tokens, components, and interaction patterns to unify visual consistency. This process relies on persistent token memory to track and apply standardized design changes across the project.

What is the best way to analyze user flows and retain UX memory across projects?

Analyzing user flows and journeys requires retaining domain memory of past UX learnings to prevent fragmented analysis. This approach stores historical UX data to inform and validate new feature mockups and interactions.

Can I audit frontend performance and interactions without external dependencies?

Yes, frontend audits evaluate interactions and performance natively without requiring external dependencies. The tooling operates independently to assess UI health, accessibility gaps, and responsiveness directly within your environment.

When do I need a design token inventory for a UI health check?

A design token inventory is needed when a UI health check reveals inconsistent styling or outdated components across a codebase. It establishes persistent memory of token states to guide design system upgrades and enforce guardrails.

Why does my UX analysis lose context across different frontend projects?

UX analysis loses context when past learnings and user flow histories are not persisted across projects. Implementing domain memory handling and audit histories ensures that previous UX insights inform current evaluations.