about-awdcs

Define scope-based keybindings for Neovim and Zed configurations.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/nikbrunner/dots --skill about-awdcs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: about-awdcs
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/about-awdcs
Command: npx skills add https://github.com/nikbrunner/dots --skill about-awdcs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope-based keymapping in modal editors to organize bindings by operation context rather than tool, reducing cognitive load and conflict.

Core Features & Use Cases

  • Five scopes: App, Workspace, Document, Change, Symbol, each with a dedicated leader pattern to simplify navigation.
  • Semantic consistency: Format: <Scope><Group><Operation>, with uppercase variants yielding persistent panels.
  • Implementation guidance: Applies to Neovim and Zed configurations, with a single source of truth in AWDCS spec.

Quick Start

Install AWDCS in your editor and load the five scopes so you can organize bindings by scope.

Frequently Asked Questions about about-awdcs

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

FAQPage Schema
How do I organize modal editor keybindings to reduce cognitive load?

Modal editor keybindings can be organized by operation context rather than tool to reduce cognitive load and conflicts. AWDCS provides a single source of truth using five scopes to manage mappings in Neovim and Zed configurations.

What is scope-based keymapping in Neovim and Zed?

Scope-based keymapping organizes editor bindings by operation context using App, Workspace, Document, Change, and Symbol scopes. AWDCS provides a clear set of rules and a single source of truth to implement this consistently across Neovim and Zed.

Can I use AWDCS with both Neovim and Zed configurations?

Yes, AWDCS can be applied across both Neovim and Zed configurations. It provides implementation guidance to establish a single source of truth for editor keybindings, ensuring semantic consistency across both platforms.

How do I structure keybindings by operation context in modal editors?

Keybindings in modal editors can be structured by operation context using the semantic format of Scope, Group, and Operation. AWDCS defines five scopes with dedicated leader patterns, where uppercase variants yield persistent panels.

What are the five scopes for managing editor keybindings in AWDCS?

The five scopes for managing editor keybindings are App, Workspace, Document, Change, and Symbol. Each scope in AWDCS has a dedicated leader pattern to simplify navigation and organize mappings by operation context.

Does scope-based keymapping help with keybinding conflicts in modal editors?

Yes, scope-based keymapping reduces keybinding conflicts in modal editors by organizing mappings by operation context rather than tool. AWDCS applies this approach to Neovim and Zed to lower cognitive load and prevent overlapping bindings.