skills.rest
yusifeng
yusifengCOMMUNITY
Explore all skills by this author →
GitHub

formax-approval-ui-workflow

Standardize approval UI prompts and presenters for Claude Code alignment.

192|7|Updated Dec 30, 2025
Search Tags:#workflow#ui#consistency#claude-code#approval#prompt#presenter
One-click install
npx skills add https://github.com/yusifeng/formax --skill formax-approval-ui-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: formax-approval-ui-workflow
Source: https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-approval-ui-workflow
Command: npx skills add https://github.com/yusifeng/formax --skill formax-approval-ui-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline and standardize the approval UI across all prompts and presenters, ensuring consistency with Claude Code alignment and reliable keyboard navigation.

Core Features & Use Cases

  • Centralizes approval chrome customization for headers, prompts, and previews to maintain a cohesive user experience.
  • Guides per-tool prompts and presenters for Bash, Read, Write, and Edit workflows, preserving clear UX flows and safe defaults.
  • Enables safe, fast previews and guardrails to prevent regressions during UI changes.

Quick Start

Review and implement the approval UI workflow guidelines to align your prompts with Claude Code parity.

Frequently Asked Questions about formax-approval-ui-workflow

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

FAQPage Schema
How do I maintain a consistent approval UI across different developer tools?▼

To maintain a consistent approval UI, you can standardize approval prompts and presenters using centralized guidelines that ensure Claude Code alignment and reliable keyboard navigation across modules.

What are the best practices for standardizing approval prompts in internal workflows?▼

Standardizing approval prompts involves centralizing chrome customization for headers and previews, applying per-tool guidance for Bash and Edit workflows, and establishing guardrails to prevent UI regressions.

How do I prevent UI regressions when modifying approval prompts and presenters?▼

You can prevent UI regressions during approval prompt modifications by applying guardrails and safe preview mechanisms that enforce UX consistency and protect against breaking changes.

Does this approval UI workflow approach support Bash, Read, Write, and Edit workflows?▼

Yes, the approval UI workflow approach provides specific guidance and safe defaults for Bash, Read, Write, and Edit workflows to preserve clear UX flows across different tool implementations.

Why do my approval prompts have inconsistent headers and previews across modules?▼

Inconsistent approval headers and previews occur without centralized chrome customization; standardizing these UI patterns ensures a cohesive user experience and Claude Code parity across modules.

Can I customize the approval UI headers and previews without breaking keyboard navigation?▼

Yes, you can customize approval UI chrome for headers and previews while maintaining reliable keyboard navigation by following standardized workflow guidelines that enforce safe defaults.

Related Skills

Explore More Software Engineering Skills→
bkywksjbkywksj
309

ui-frontend

Define standardized React UI patterns for Tauri desktop apps.

Community
Intermediate
michaelvolzmichaelvolz

agent-native-architecture

Design agent-native architecture with autonomous loops, parity tooling, and context.md files.

Community
Advanced
AngelP17AngelP17
1

tailwind-design-system

Standardize UI design with Tailwind-based design tokens and component patterns.

Community
Advanced
GraffiohGraffioh

web-browser

Automate Chrome browser interactions via the Chrome DevTools Protocol.

Community
Advanced