Configuring Project Permissions

Set up a repository's personal, uncommitted agent permissions so development runs without prompts: Claude Code's gitignored .claude/settings.local.json and Codex CLI's gitignored .codex/rules/local.rules, each in its native format. Generic rules (git, gh, coreutils, hook-bypass and force-push denies) go to the user-level files; the project file keeps only what names the repository — recipes, scripts, dependency policy, protected files — allow by default, ask only for commands that open the app, write to GitHub, release, or change dependencies. Detects the toolchain, drops rules a global rule a

5 starsAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add tomada1114/tomada-claude-plugins

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add tomada1114/tomada-claude-plugins --skill configuring-project-permissions
Manual install
git clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/configuring-project-permissions ~/.claude/skills/configuring-project-permissions

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Configuring Project Permissions

The goal is a repository where an agent runs every build, test, lint, format, codegen,
and cleanup command without a prompt, while the few commands that act on the
developer's machine, on GitHub, on a release, or on the dependency set still stop for a
human. The user prefers loose: when a development command could go either way, propose
allow.

Two hosts, two native mechanisms, never one shared file:

| | Claude Code | Codex CLI |
|---|---|---|
| User level (every repository) | `~/.claude/settings.json` `permissions` | `~/.codex/rules/default.rules`, sandbox in `~/.codex/config.toml` | 
| This repository, personal | `.claude/settings.local.json` (gitignored) | `.codex/rules/local.rules` (gitignored), loaded only while the project is trusted |
| Precedence | deny → ask → allow across all files | forbidden > prompt > allow across all layers |

Neither project file is committed: which commands run without a prompt is each
person's choice, and a committed allow list is reviewed by nobody when it widens. A
committed `.claude/settings.json` may still carry team-wide, non-permission settings
(plugins, marketplaces, MCP servers), never `permissions` or personal hooks.

## Where a rule goes

- **User level** — anything safe and useful in every repository: git and gh reads and
  routine writes, coreutils, language toolchains installed user-wide (`cargo`, `pnpm`,
  `uv`, `mise`), hook-bypass and force-push denies, publish asks. Changing one of these
Read the full skill on GitHub

Details

Skill name
configuring-project-permissions
Path
tomada-kit/skills/configuring-project-permissions/SKILL.md
Repo updated
12 November 2026

FAQ

What does the Configuring Project Permissions skill do?

Set up a repository's personal, uncommitted agent permissions so development runs without prompts: Claude Code's gitignored .claude/settings.local.json and Codex CLI's gitignored .codex/rules/local.rules, each in its native format. Generic rules (git, gh, coreutils, hook-bypass and force-push denies) go to the user-level files; the project file keeps only what names the repository — recipes, scripts, dependency policy, protected files — allow by default, ask only for commands that open the app, write to GitHub, release, or change dependencies. Detects the toolchain, drops rules a global rule a

How do I install the Configuring Project Permissions skill?

Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Configuring Project Permissions popular?

It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.

Related skills

Auditing Prompt Docs

5

tomada1114/tomada-claude-plugins

Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m

AI, LLMs & Agents

Auditing Repositories

5

tomada1114/tomada-claude-plugins

Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst

Testing & QA

Authoring Goal Prompts

5

tomada1114/tomada-claude-plugins

Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de

AI, LLMs & Agents

Creating Agent Skills

5

tomada1114/tomada-claude-plugins

Create or improve Agent Skills (the shared SKILL.md format read by Claude Code and OpenAI Codex CLI — SKILL.md + optional references/scripts/assets). Two playbooks: build a skill from scratch or from an existing doc; or review an existing skill through parallel specialist lenses (prose quality, agent neutrality, structure, scripts, orchestration) and propose fixes. Takes a free-form request — "I want a skill that…", "turn this runbook into a skill", "audit this skill", "it never fires", "split this into sub-agents" — optionally followed by a skill name or absolute path. Also triggers on Codex

AI, LLMs & Agents

Configuring Cloud Environments

5

tomada1114/tomada-claude-plugins

Inspect, create, and edit Claude Code cloud environments (the Name, Network access, Allowed domains, Setup script, and Environment variables behind claude.ai/code's environment selector) and decide what a repository needs from one — which hosts its toolchain downloads from and whether the Trusted allowlist covers them (bundled checker script), whether an existing environment fits or a new one is warranted, and what belongs in the environment's setup script versus the repository's SessionStart hook. Use when asked to look at, create, edit, or tune a cloud environment or its setup script, to add

AI, LLMs & Agents

Debate Claude

5

Magnus-Gille/claude-skills

Run a two-round adversarial review from Codex with Claude as the independent reviewer for a consequential decision or substantive draft when cross-model critique is warranted.

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.