chore(gitignore): update ignore lists and documentation

[vancura]

This PR updates the project's gitignore rules and developer configuration files.

Changes to .gitignore:

• Refines directory ignore rules with more granular control:
  • Replaces blanket .zed/ directory ignore with .zed/* while explicitly whitelisting .zed/settings.json
  • Updates .idea/ ignore and adds *.iml pattern for WebStorm/IntelliJ, while whitelisting .vscode/settings.json and .vscode/extensions.json
  • Adds new ignore entries for VS Code project settings (launch.json, *.code-workspace)
  • Introduces Cursor-related generated files ignore rules (cursor-config/)
  • Adds Vim/Emacs swap file patterns (*.swp, *.swo, *~)
  • Maintains existing ignore entries for development artifacts (logs, coverage, test results, caches, temporary files, archives, etc.)

Adds .zed/settings.json:

• New comprehensive editor configuration for Zed with:
  • Global format_on_save enabled with auto formatter
  • Language-specific formatter configurations:
    • CSS: tailwindcss-intellisense-css and vscode-css-language-server
    • TypeScript, JavaScript, JSON: language_server formatter
    • Astro, HTML, Markdown: prettier formatter
    • Svelte: language_server formatter
  • LSP configuration for tailwindcss-language-server with experimental classRegex settings

Updates ai-rules/website.mdc:

• Documents semantic design token updates with automatic dark mode switching
• Removes need for -dark variant classes by consolidating to single semantic class names
• Updates token naming to use broader categories (page-bg, surface, border-default, text-primary, etc.)
• Notes that CSS variables auto-switch based on .dark class
• Updates usage examples and guidelines to reflect the simplified token approach

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates editor configuration and development environment setup by refining .gitignore rules for multiple IDEs/editors, adding Zed editor settings with formatter and language server configurations, and updating semantic design token documentation to reflect dark mode support and simplified naming conventions.

Changes

Cohort / File(s)	Summary
Editor Configuration .gitignore, .zed/settings.json	Refines .gitignore to handle editor-specific files with selective whitelisting for Zed, IntelliJ/WebStorm, and VS Code settings. Adds .zed/settings.json with global format_on_save enabled, language-specific formatter/language server configurations for TypeScript, JavaScript, CSS, HTML, Markdown, Svelte, Astro, and JSON, plus tailwindcss language server LSP configuration.
Documentation ai-rules/website.mdc	Updates semantic design token documentation to reflect automatic dark mode switching via .dark class, removes need for -dark token variants, and consolidates naming conventions (e.g., page-bg, surface, border-default, text-primary).

Possibly related PRs

• docs: update AI rules #52: Updates semantic design token documentation for dark mode behavior and simplified token naming conventions that align with this PR's documentation changes.
• docs: update documentation #91: Modifies .gitignore patterns and editor configuration documentation, showing overlap with this PR's editor setup and ignore rule changes.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title describes gitignore updates, but the PR actually makes three distinct changes: .gitignore refinement, new .zed/settings.json configuration, and ai-rules/website.mdc documentation updates.	Revise the title to reflect all meaningful changes, such as: 'chore: configure editor settings and update semantic design tokens' or provide a more comprehensive description that captures the .zed settings and documentation changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch toolset-update

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}