zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-04-06 17:23:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: shift repo guidance to skills-first workflows

Browse Source
This commit is contained in:
Affaan Mustafa
2026-04-01 02:11:24 -07:00
parent 5194d2000a
commit f3db349984
11 changed files with 56 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
the-shortform-guide.md
View File

@@ -12,24 +12,24 @@ Here's my complete setup after 10 months of daily use: skills, hooks, subagents,
## Skills and Commands
Skills operate like rules, constricted to certain scopes and workflows. They're shorthand to prompts when you need to execute a particular workflow.
Skills are the primary workflow surface. They act like scoped workflow bundles: reusable prompts, structure, supporting files, and codemaps when you need a particular execution pattern.
After a long session of coding with Opus 4.5, you want to clean out dead code and loose .md files? Run `/refactor-clean`. Need testing? `/tdd`, `/e2e`, `/test-coverage`. Skills can also include codemaps - a way for Claude to quickly navigate your codebase without burning context on exploration.
After a long session of coding with Opus 4.5, you want to clean out dead code and loose .md files? Run `/refactor-clean`. Need testing? `/tdd`, `/e2e`, `/test-coverage`. Those slash entries are convenient, but the real durable unit is the underlying skill. Skills can also include codemaps - a way for Claude to quickly navigate your codebase without burning context on exploration.
![Terminal showing chained commands](./assets/images/shortform/02-chaining-commands.jpeg)
*Chaining commands together*
Commands are skills executed via slash commands. They overlap but are stored differently:
ECC still ships a `commands/` layer, but it is best thought of as legacy slash-entry compatibility during migration. The durable logic should live in skills.
- **Skills**: `~/.claude/skills/` - broader workflow definitions
- **Commands**: `~/.claude/commands/` - quick executable prompts
- **Skills**: `~/.claude/skills/` - canonical workflow definitions
- **Commands**: `~/.claude/commands/` - legacy slash-entry shims when you still need them
```bash
# Example skill structure
~/.claude/skills/
pmx-guidelines.md # Project-specific patterns
coding-standards.md # Language best practices
tdd-workflow/ # Multi-file skill with README.md
tdd-workflow/ # Multi-file skill with SKILL.md
security-review/ # Checklist-based skill
```
@@ -149,7 +149,7 @@ Your 200k context window before compacting might only be 70k with too many tools
# Check enabled MCPs
/mcp
# Disable unused ones in ~/.claude.json under projects.disabledMcpServers
# Disable unused ones in ~/.claude/settings.json or in the current repo's .mcp.json
```
---