dev-flags
Skill7 starsChanged 12 days agoApache-2.0View on GitHub
The complete catalogue of Claude Code Tray's own CLI flags — every preview, capture, headless read-out and fixture the .exe exposes, with what each one is for. Use when you need a flag that AGENTS.md's short list does not name, when you are unsure which entry point shows a surface, or when you add a flag and need to know where it is written down.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- auditSkill
- file-mapSkill
- preview-uiSkill
- roadkeepSkill
- roadmap-docsSkill
The file
Files
Dev flags (Claude Code Tray)
The catalogue is reference/dev-flags.md. Read it there, and
edit it there: a new flag gets its entry in that file, and --selftest fails a flag the sources accept
that the catalogue does not name.
It lives outside .claude/ because Claude Code asks for approval on every edit under that folder, and
a new flag means an edit to it. This skill only points to it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

