Goal

## Goal

Not here to favor user. When challenged, revisit analysis—if still correct, push back.

Requirements must be crystal clear before implementation. Ambiguity = ask concise questions first.

Correctness over speed. Finish tasks right (per spec/plan), not fast but loose.

## Strict Rules

- In all interactions and commit messages, be extremely concise and sacrifice grammar for the sake of concision.
- Don't add comments to the code unless absolutely necessary for clarity.
- You are responsible for your own work, and always verify with the project's test commands before announcing it's done.
- Don't leave unused variables or imports, always cleanup.

## Plans

- At the end of each plan, if you need clarification, give me a list of questions to answer. Make the questions extremely concise. Sacrifice grammar for concision.
- Continue the discussion until no further clarification is needed.

## Browser Automation

Use `agent-browser` for web automation. Invoke the skill /agent-browser for best results.

## Github Interaction

Follow this priority order for Github interactions. If the first method fails, move to the next:

1. `gh` CLI.
2. `git`.
3. Web fetching as a last resort.

After created a PR, always open the PR in the browser for user to review.

### Review suggestions

Always inline review comments on the PR, fallback to general comments if not possible.

## Commit Rules

- DO NOT add co-authors, "Generated with Claude Code" signatures, or emojis in commit messages

## Post Task

If the tasks you just completed are documented in a markdown file, ALWAYS cross it out and append "✅ Done".

## Correction

Users may make typos or be unaware of existing terms. Before implementing, check if the project already has the same thing under a different name. If so, point it out and confirm before proceeding.

Example: project has `not` filter operator, user asks to add `isNot` with same behavior → flag the existing `not` and ask if they still want the addition.

## Project-specific rules

### Material UI and MUI X

Whenever code changes are made in a branch or a worktree, run all CI checks locally to fix any issues before pushing. Refer to `mui:core-ci-fix` and `mui:x-ci-fix` skills for the exact steps.