claude-code-gui
AGENTS.md1 starsChanged 9 months agoMITView on GitHub
This repository is a template with sensible defaults for building Tauri React apps. CRITICAL: Follow these strictly: CRITICAL: Use Tauri v2 docs only. Always use modern Rust formatting: format!("{variable}") Decision: Is data needed across components? → Does it persist between sessions? Adding commands: See docs/developer/tauri-commands.md
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository25 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- frontend-designSkill
- rust-async-patternsSkill
- rust-best-practicesSkill
- tauri-v2Skill
- clean-code-inspectorSkill
- unused-code-cleanerSkill
- commitSkill
- complexity-refactorSkill
- component-screenshotSkill
- deep-thinkSkill
- design-checkSkill
- figma-design-pipelineSkill
- figma-to-codeSkill
- issue-startSkill
- issue-updateSkill
- milestone-executeSkill
- milestoneSkill
- milestone-updateSkill
- plannerSkill
- react-refactoringSkill
- specSkill
- story-generatorSkill
- surveySkill
- testSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
20 rules. About 0 are common, 11 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Check docs/developer/README.md for the full documentation index
- Distinctive: line 13
Check git status and project structure
- Distinctive: line 17
CRITICAL: Follow these strictly:
- Distinctive: line 20
Read Before Editing: Always read files first to understand context
- Very specific: line 21
Follow Established Patterns: Use patterns from this file and docs/developer
- Distinctive: line 22
Senior Architect Mindset: Consider performance, maintainability, testability
- Distinctive: line 23
Batch Operations: Use multiple tool calls in single responses
- Distinctive: line 24
Match Code Style: Follow existing formatting and patterns
- Distinctive: line 25
Test Coverage: Write comprehensive tests for business logic
- Very specific: line 26
Quality Gates: Run pnpm check:all after significant changes
- Distinctive: line 27
No Dev Server: Ask user to run and report back
- Distinctive: line 28
No Unsolicited Commits: Only when explicitly requested
- Very specific: line 29
Documentation: Update relevant docs/developer/ files for new patterns
- Very specific: line 30
Removing files: Always use rm -f
- Very specific: line 32
CRITICAL: Use Tauri v2 docs only. Always use modern Rust formatting: format!("{variable}")
- Very specific: line 69
React → Rust: Use typed commands from @/lib/tauri-bindings (tauri-specta)
- Distinctive: line 70
Commands: All actions flow through centralized command system
- Very specific: line 106
Translations: All strings in /locales/*.json
- Very specific: line 107
RTL Support: Use CSS logical properties (text-start not text-left)
- Distinctive: line 112
Context7 First: Always use Context7 for framework docs before WebSearch
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI Agent Instructions
Overview
This repository is a template with sensible defaults for building Tauri React apps.
Core Rules
New Sessions
- Review
docs/developer/architecture-guide.mdfor high-level patterns - Check
docs/developer/README.mdfor the full documentation index - Check git status and project structure
Development Practices
CRITICAL: Follow these strictly:
- Use pnpm only: This project uses
pnpm(locked at 10.29.1). Always usepnpm install,pnpm run, etc. - Read Before Editing: Always read files first to understand context
- Follow Established Patterns: Use patterns from this file and
docs/developer - Senior Architect Mindset: Consider performance, maintainability, testability
- Batch Operations: Use multiple tool calls in single responses
- Match Code Style: Follow existing formatting and patterns
- Test Coverage: Write comprehensive tests for business logic
- Quality Gates: Run
pnpm check:allafter significant changes - No Dev Server: Ask user to run and report back
- No Unsolicited Commits: Only when explicitly requested
- Documentation: Update relevant
docs/developer/files for new patterns - Removing files: Always use
rm -f
CRITICAL: Use Tauri v2 docs only. Always use modern Rust formatting: format!("{variable}")
Architecture Patterns (CRITICAL)
State Management Onion
useState (component) → Zustand (global UI) → TanStack Query (persistent data)Decision: Is data needed across components? → Does it persist between sessions?
Performance Pattern (CRITICAL)
// ✅ GOOD: Selector syntax - only re-renders when specific value changes
const leftSidebarVisible = useUIStore(state => state.leftSidebarVisible)
// ❌ BAD: Destructuring causes render cascades (caught by ast-grep)
const { leftSidebarVisible } = useUIStore()
// ✅ GOOD: Use getState() in callbacks for current state
const handleAction = () => {
const { data, setData } = useStore.getState()
setData(newData)
}Static Analysis
- React Compiler: Handles memoization automatically - no manual
useMemo/useCallbackneeded - ast-grep: Enforces architecture patterns (e.g., no Zustand destructuring). See
docs/developer/static-analysis.md - Knip/jscpd: Periodic cleanup tools. Use
/cleanupcommand (Claude Code)
Event-Driven Bridge
- Rust → React:
app.emit("event-name", data)→listen("event-name", handler) - React → Rust: Use typed commands from
@/lib/tauri-bindings(tauri-specta) - Commands: All actions flow through centralized command system
Tauri Command Pattern (tauri-specta)
// ✅ GOOD: Type-safe commands with Result handling
import { commands } from '@/lib/tauri-bindings'
const result = await commands.loadPreferences()
if (result.status === 'ok') {
console.log(result.data.theme)
}
// ❌ BAD: String-based invoke (no type safety)
const prefs = await invoke('load_preferences')Adding commands: See docs/developer/tauri-commands.md
Internationalization (i18n)
// ✅ GOOD: Use useTranslation hook in React components
import { useTranslation } from 'react-i18next'
function MyComponent() {
const { t } = useTranslation()
return <h1>{t('myFeature.title')}</h1>
}
// ✅ GOOD: Non-React contexts - bind for many calls, or use directly
import i18n from '@/i18n/config'
const t = i18n.t.bind(i18n) // Bind once for many translations
i18n.t('key') // Or call directly for occasional use- Translations: All strings in
/locales/*.json - RTL Support: Use CSS logical properties (
text-startnottext-left) - Adding strings: See
docs/developer/i18n-patterns.md
Documentation & Versions
- Context7 First: Always use Context7 for framework docs before WebSearch
- Version Requirements: Tauri v2.x, shadcn/ui v4.x, Tailwind v4.x, React 19.x, Zustand v5.x, Vite v7.x, Vitest v4.x
Developer Documentation
For complete patterns and detailed guidance, see docs/developer/README.md.
Key documents:
architecture-guide.md- Mental models, security, anti-patternsstate-management.md- State onion, getState() pattern detailstauri-commands.md- Adding new Rust commandsstatic-analysis.md- All linting tools and quality gates
Claude Code Commands & Agents
These are specific to Claude Code but documented here for context.
Commands
/check- Check work against architecture, runpnpm check:all, suggest commit message/cleanup- Run static analysis (knip, jscpd, check:all), get structured recommendations/init- One-time template initialization
Agents
Task-focused agents that leverage separate context for focused work:
plan-checker- Validate implementation plans against documented architecturedocs-reviewer- Review developer docs for accuracy and codebase consistencyuserguide-reviewer- Review user guide against actual system featurescleanup-analyzer- Analyze static analysis output (used by/cleanup)
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.

