Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
A skill your agent uses when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay…
Install Formax Permissions Workflow
$ npx skills add yusifeng/formax --skill formax-permissions-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yusifeng/formax formax-permissions-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yusifeng/formax.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/formax-permissions-workflow .claude/skills/formax-permissions-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "formax-permissions-workflow" agent skill from https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-permissions-workflow into .claude/skills/formax-permissions-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formax-permissions-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-permissions-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yusifeng/formax --skill formax-permissions-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yusifeng/formax formax-permissions-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yusifeng/formax.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/formax-permissions-workflow .agents/skills/formax-permissions-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "formax-permissions-workflow" agent skill from https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-permissions-workflow into .agents/skills/formax-permissions-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formax-permissions-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yusifeng/formax --skill formax-permissions-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yusifeng/formax formax-permissions-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yusifeng/formax.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/formax-permissions-workflow .cursor/skills/formax-permissions-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "formax-permissions-workflow" agent skill from https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-permissions-workflow into .cursor/skills/formax-permissions-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formax-permissions-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yusifeng/formax.git --path .codex/skills/formax-permissions-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yusifeng/formax --skill formax-permissions-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yusifeng/formax formax-permissions-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yusifeng/formax.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/formax-permissions-workflow .gemini/skills/formax-permissions-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "formax-permissions-workflow" agent skill from https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-permissions-workflow into .gemini/skills/formax-permissions-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formax-permissions-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yusifeng/formax formax-permissions-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yusifeng/formax --skill formax-permissions-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yusifeng/formax.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/formax-permissions-workflow .github/skills/formax-permissions-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "formax-permissions-workflow" agent skill from https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-permissions-workflow into .github/skills/formax-permissions-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formax-permissions-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yusifeng/formax --skill formax-permissions-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yusifeng/formax formax-permissions-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yusifeng/formax.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/formax-permissions-workflow .opencode/skills/formax-permissions-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "formax-permissions-workflow" agent skill from https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-permissions-workflow into .opencode/skills/formax-permissions-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formax-permissions-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
formax-permissions-workflow- GitHub stars
- 195
- Token cost
- ~1.3k tokens
- SKILL.md length
- 419 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay…
- Works in 4 steps: Policy preflight (ToolCall ->… → Permissions storage + matching (rules &… → Approvals (prompt UI + persistence… → …
- Debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules
- SKILL.md covers Goal, Read First, Code Map and High-Signal Patterns, plus 3 more sections
- Calls bun and npm
What it does
Formax Permissions Workflow is an agent skill from yusifeng/formax. Use when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay parity with Claude Code).
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Terminal-first AI assistant for software engineering tasks (inspired by Claude Code v2.0.67). The licence is MIT.
When your agent uses it
- Debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules
- Workspace boundaries
- Approval prompts
- /permissions overlay parity with Claude Code)
Example prompts
- “/formax-permissions-workflow”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1b0c3f3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bunnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Formax Permissions Workflow loads about 1.3k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 419 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from yusifeng/formax at commit 1b0c3f3, republished under its MIT licence (© yusifeng). 419 words, ~1,273 tokens.
Download SKILL.mdSave it as
.claude/skills/formax-permissions-workflow/SKILL.md (or your agent's skills folder).- name
- formax-permissions-workflow
- description
- Use when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay parity with Claude Code).
Formax permissions / approvals workflow
Goal
Use this skill when changing policy preflight, approval prompts, remember side-effects, or /permissions management.
Read First
docs/contracts/permissions-policy-contract.mddocs/contracts/interactive-input-contract.mddocs/contracts/semantics-contract.mdwhen the change crosses TUI / app-server / Web
These docs are canonical. If stable behavior changes, update them before or with code.
Code Map
1) Policy preflight (ToolCall -> allow/ask/deny decision)
packages/core/src/tools/executor/policyPreflight.ts: turnsToolCallinto aPolicyActionand decides deny / prompt / allowpackages/core/src/tools/executor/policyAction.ts:ToolCall->PolicyActionmappingpackages/core/src/tools/executor/policyExplain.ts: explain / debug text for decisionspackages/core/src/tools/modules/bash/policy.ts: Bash risk classification
2) Permissions storage + matching (rules & precedence)
packages/core/src/adapters/permissions/permissionsStore.ts: read / write settings and merge precedencepackages/core/src/adapters/permissions/permissionKeys.ts: stable keys / paths for settingspackages/core/src/adapters/permissions/matcher.ts: matcher semantics
3) Approvals (prompt UI + persistence side-effects)
packages/core/src/tools/executor/approvalService.ts:ensureApprovedflow and remember writes- UI prompts:
packages/core/src/components/tool/bashApprovalPrompt.tsxpackages/core/src/components/tool/fsReadApprovalPrompt.tsxpackages/core/src/components/tool/fsWriteApprovalPrompt.tsxpackages/core/src/components/tool/skillApprovalPrompt.tsxpackages/core/src/components/tool/editApprovalPrompt.tsx
- Shared pieces:
packages/core/src/components/ui/ApprovalHeader.tsxpackages/core/src/components/ui/ConfirmMenu.tsx
4) /permissions overlay (manage rules + workspace)
packages/core/src/tui/permissions/PermissionsDialog.tsx: state machine + key handlingpackages/core/src/tui/permissions/ui.tsx: rendering primitivespackages/core/src/features/repl/controller/ui/overlays.ts: overlay open / close and dismissal messages- Slash command wiring:
packages/core/src/features/commands/registry.tspackages/core/src/screens/repl/createReplCommandRegistry.ts
If app-server or Web input behavior moves, also inspect:
packages/core/src/app-server/turn/inputStore.tspackages/core/src/app-server/server.tspackages/web-reference-react/src/store.ts
High-Signal Patterns
- Pattern A: tool approval prompt (3 options + Esc)
YesYes, ...(remember / allow in repo or session)Type here to tell Claude what to do differently- cancellation remains
Esc to cancel, not a bespoke menu item
- Pattern B: destructive confirm prompt
- use
Yes / No - still support
Esc to cancel
- use
- Pattern C: partial emphasis in menu options
- use
ConfirmMenuemphasis support instead of ad-hoc JSX or ANSI - selected rows must not leave mismatched emphasis colors behind
- use
Show full SKILL.md (182 more words)Show less
Minimal Workflow
- Read the canonical contract(s) above and define the exact behavior delta.
- Change the narrowest canonical code path first (
policyPreflight, matcher / store,approvalService, or overlay state machine). - Preserve existing UI copy / spacing / colors / keys unless the user explicitly asks for UI changes.
- Keep “what the user sees” separate from “what is injected back into model context”.
- Run the minimum regression set below, then review via
AGENTS.mdbefore commit.
Minimum Regression
bun run test -- packages/core/src/tools/executor/policyPreflight.test.tsbun run test -- packages/core/src/tools/executor/approvalService.test.tsbun run test -- packages/core/src/components/tool/bashApprovalPrompt.test.tsxbun run test -- packages/core/src/components/tool/fsReadApprovalPrompt.test.tsxbun run test -- packages/core/src/components/tool/fsWriteApprovalPrompt.test.tsxbun run test -- packages/core/src/components/tool/skillApprovalPrompt.test.tsxbun run test -- packages/core/src/tui/permissions/PermissionsDialog.test.tsx- If app-server / Web input behavior changed:
bun run test -- packages/core/src/app-server/turn/inputStore.test.ts packages/core/src/app-server/server.test.tsnpm --prefix packages/web-reference-react run test -- src/store.test.ts
Guardrails
- Do not encode permission semantics inside prompt components; contracts live in policy / approval layers.
- Do not add bespoke key handling or ANSI styling when shared approval components already cover the case.
- Do not loosen permissions or remember scope just to make parity demos pass.
- Preserve approval UI copy / spacing / colors / key paths unless the user explicitly asks for UI changes.
© yusifeng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .codex/skills/formax-permissions-workflow of yusifeng/formax.
Open the folder on GitHubat commit 1b0c3f3
Compare with similar skills
Formax Permissions Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Formax Permissions Workflow this skillyusifeng/formax | 195 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from yusifeng/formax
All 21 skills in this repoFormax Repomix Handoff Workflow
yusifeng/formax
A skill your agent uses when preparing a Formax code handoff: selecting files, generating repomix bundles, and writing a high-quality prompt for WebGPT or another coding agent with clear constraints…
Formax Skill Capture
yusifeng/formax
A skill your agent uses when we want to turn a just-finished Formax workflow (e.g.
Analyze Task
yusifeng/formax
A skill your agent uses when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an…
Formax Dev Loop Workflow
yusifeng/formax
A skill your agent uses when working on Formax code changes and you need a disciplined dev loop: keep a single mainline task, avoid scope drift, run only targeted tests (no coverage), avoid partial…
Formax Tool UI Blocks Workflow
yusifeng/formax
Implement or refactor Formax tool transcript UI using the Tool UI Blocks (C-lite) pattern (ToolUiBlocks renderer + blocks presenters) to avoid touching many tool presenter files; use when adjusting…
Formax Semantics Parity Workflow
yusifeng/formax
A skill your agent uses when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order).
Related
Categories
Questions about Formax Permissions Workflow
What does Formax Permissions Workflow do?
A skill your agent uses when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay…. Formax Permissions Workflow is an agent skill from yusifeng/formax. Use when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay parity with Claude Code).
When should I use Formax Permissions Workflow?
Formax Permissions Workflow fits situations like: debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules; workspace boundaries; approval prompts; /permissions overlay parity with Claude Code).
How do I install Formax Permissions Workflow in Claude Code?
Run `npx skills add yusifeng/formax --skill formax-permissions-workflow -a claude-code`. Or copy the skill folder (.codex/skills/formax-permissions-workflow in yusifeng/formax) into .claude/skills/formax-permissions-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Formax Permissions Workflow in Codex?
Run `npx skills add yusifeng/formax --skill formax-permissions-workflow -a codex`. Or copy the skill folder (.codex/skills/formax-permissions-workflow in yusifeng/formax) into .agents/skills/formax-permissions-workflow in your project. Codex loads it when a task matches its description.
Can I use Formax Permissions Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yusifeng/formax --skill formax-permissions-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/formax-permissions-workflow, .gemini/skills/formax-permissions-workflow, .github/skills/formax-permissions-workflow and .opencode/skills/formax-permissions-workflow in your project.
What does Formax Permissions Workflow need to run?
Going by SKILL.md and its folder, Formax Permissions Workflow needs the command-line tools its instructions call (bun and npm).
Does Formax Permissions Workflow access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Formax Permissions Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Formax Permissions Workflow use?
Formax Permissions Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Formax Permissions Workflow use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Formax Permissions Workflow?
Skills that share tags, products or a category with Formax Permissions Workflow: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Formax Permissions Workflow?
yusifeng (a GitHub user) maintains it in yusifeng/formax, which has 195 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on July 24, 2026.
Source: yusifeng/formax on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.