zed-format

Configures Zed IDE format-on-save and ESLint-on-save for Vue, TypeScript, JSON across workspaces and repos.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/sathish099/zed-format-skill --skill zed-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zed-format
Source: https://github.com/sathish099/zed-format-skill/tree/main
Command: npx skills add https://github.com/sathish099/zed-format-skill --skill zed-format

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configures or debugs Zed IDE format-on-save and ESLint-on-save for cross-filetype projects (Vue, TypeScript, JSON) and across operating systems, addressing misconfigurations that break formatting or linting.

Core Features & Use Cases

  • Validates and standardizes the workspace- vs repo-level .zed/settings.json approach to ensure consistent formatting across the codebase.
  • Provides a clear workflow: inspect config boundaries, validate settings shape, and wire the save pipeline (source.fixAll.eslint, source.organizeImports, and prettier).
  • Supports complex layouts like monorepos or multi-repo setups with a shared workspace and per-repo ESLint paths.
  • Documents prerequisites (eslint, prettier, eslint-config-prettier, a repo ESLint config) and recommended practices for cross-OS consistency.

Quick Start

Inspect the nearest workspace and repo settings, verify prerequisites, and wire the save pipeline to enable format-on-save and ESLint-on-save across Vue, TypeScript, and JSON.

Frequently Asked Questions about zed-format

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Zed IDE format-on-save for Vue, TypeScript, and JSON files?

Configure Zed IDE format-on-save by aligning workspace-level and repo-level settings to ensure consistent formatting across Vue, TypeScript, and JSON. This involves wiring the save pipeline with source.fixAll.eslint, source.organizeImports, and Prettier.

Why does ESLint on save not work in my Zed monorepo setup?

ESLint on save fails in Zed monorepos when workingDirectories are misconfigured or repo-level ESLint paths are incorrect. You must validate the nearest workspace and repo settings boundaries and ensure per-repo ESLint paths are correctly specified.

Do I need Prettier and eslint-config-prettier to format TypeScript in Zed?

Yes, you need Prettier and eslint-config-prettier installed alongside a repo ESLint config to properly wire the Zed save pipeline and prevent conflicts between ESLint and Prettier formatting rules for TypeScript.

What is the best way to manage Zed settings across different operating systems?

The best way to manage Zed settings across operating systems is to standardize the workspace-level versus repo-level .zed/settings.json approach, documenting prerequisites and recommended practices to ensure cross-OS formatting consistency.

Can I use Zed IDE ESLint-on-save with a multi-repo layout?

Yes, Zed IDE ESLint-on-save supports multi-repo layouts with a shared workspace and per-repo ESLint paths. You need to configure ESLint workingDirectories and ensure a trusted Zed worktree to validate the setup.