---
slug: "micro-polish-skill"
source_type: "readme"
source_url: "https://cdn.jsdelivr.net/gh/justingoertz/micro-polish-skill@master/README.md"
repo: "https://github.com/justingoertz/micro-polish-skill"
source_file: "README.md"
branch: "master"
---
# Craft Skills

Skills for [Claude Code](https://github.com/anthropics/claude-code) that help build taste in software work.

## Skills

| Skill | Description |
|-------|-------------|
| [micro-polish](https://github.com/justingoertz/micro-polish-skill/blob/HEAD/skills/micro-polish/SKILL.md) | Apply invisible refinements that compound into felt quality |

## Installation

### Quick install (symlink)

```bash
# Clone the repo
git clone https://github.com/justingoertz/craft-skills.git ~/craft-skills

# Create the Claude skills directory if it doesn't exist
mkdir -p ~/.claude/skills

# Symlink skills you want to use
ln -s ~/craft-skills/skills/micro-polish ~/.claude/skills/micro-polish
```

### Manual install (copy)

Copy individual skill folders to `~/.claude/skills/`:

```bash
cp -r ~/craft-skills/skills/micro-polish ~/.claude/skills/
```

### Verify installation

```bash
ls ~/.claude/skills/
# Should show: micro-polish
```

## Usage

Once installed, skills are available in Claude Code:

```
/micro-polish          # Apply micro-refinement sensibility to current work
/micro-polish <file>   # Review a specific file for polish opportunities
```

## Adding new skills

Each skill lives in its own directory under `skills/`:

```
skills/
└── your-skill/
    └── SKILL.md
```

### Skill file format

```markdown
---
name: your-skill
description: One-line description of what it does
---

# Skill Name

Longer explanation of the skill's purpose and philosophy.

## How to use

- `/your-skill`
  What happens when invoked without arguments.

- `/your-skill <args>`
  What happens with arguments.

## Process

The actual guidance, patterns, or workflow the skill provides.
```

### Guidelines for new skills

- **Opinionated over comprehensive** — Have a point of view. Don't document every option.
- **Patterns over rules** — Guide intuition, not checklists
- **Concrete over abstract** — Show specific examples
- **Trust the agent** — Starting points, not constraints

## Philosophy

Develop taste, not compliance. The patterns should eventually disappear into instinct.

## License

MIT