formax-permissions-workflow

Implement and debug Formax permissions, policy, and approval flows.

192|7|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/yusifeng/formax --skill formax-permissions-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: formax-permissions-workflow
Source: https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-permissions-workflow
Command: npx skills add https://github.com/yusifeng/formax --skill formax-permissions-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers implement, test, and debug the permissions, policy, and approval flows in Formax, including allow/deny decisions, workspace boundaries, and the /permissions overlay parity with Claude Code. It centralizes understanding of canonical contracts and UI behavior to ensure safe, predictable policy interactions.

Core Features & Use Cases

  • Policy preflight and decision flow: guidance on how ToolCall is evaluated to allow, prompt, or deny, with clear traceability.
  • Approvals and persistence: UI prompts and persistence logic to capture user consent and remember decisions across sessions.
  • Overlay and wiring: controls for the in-UI permissions overlay, workspace boundaries, and command integration within the app server / web layers.
  • Use Case: debugging a new permission rule in a project and verifying that prompts appear and decisions persist as expected.

Quick Start

Run formax in your project and trigger a permissions flow to observe prompts and overlay behavior.

Frequently Asked Questions about formax-permissions-workflow

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

FAQPage Schema
How do I debug a Formax permissions policy that is not prompting for approval?

To debug a Formax permissions policy that fails to prompt, trace the policyPreflight evaluation flow to verify how ToolCall decisions are resolved as allow, prompt, or deny. Check the permission stores and approval persistence logic to ensure UI prompts and slash-command wiring are correctly configured across TUI, app-server, and Web contexts.

What is the canonical contract for Formax policy preflight and approval persistence?

The Formax policy preflight canonical contract governs how ToolCall requests are evaluated for allow, prompt, or deny decisions. Approval persistence captures user consent and remembers those decisions across sessions via permission stores integrated within the app server and web layers.

How do I enforce workspace boundaries in Formax permissions workflows?

You enforce workspace boundaries in Formax permissions workflows by configuring the overlay management and policy preflight logic to restrict ToolCall evaluations. This ensures safe, predictable policy interactions and prevents unauthorized access outside the defined workspace perimeter across TUI, app-server, and Web contexts.

Does Formax permissions overlay support parity with Claude Code command integration?

Yes, the Formax permissions overlay implementation supports parity with Claude Code by wiring slash commands and UI prompts within the app server and web layers. This integration ensures consistent overlay management, workspace boundary enforcement, and approval persistence across TUI, app-server, and Web contexts.

Why does my Formax permission store fail to remember approval decisions across sessions?

If your Formax permission store fails to remember approval decisions across sessions, the approval persistence logic may be disconnected from the permission stores. Verify the UI prompts correctly capture user consent and that the persistence layer properly saves allow or deny decisions within the app server and web layers.