A personal collection of skills for AI coding agents. Each skill packages instructions, references, and workflows that extend agent capabilities beyond their defaults.
Skills are packaged instructions that teach AI agents new workflows and specialized knowledge. Think of them as plugins — a SKILL.md file with YAML frontmatter tells the agent when to activate, and markdown content tells it what to do. Supporting files (references, templates, scripts) are loaded on demand to keep context usage minimal.
Skills follow the Agent Skills open standard, which originated in Claude Code and has been adopted across all major AI coding agents.
Install any skill with a single command using the Skills CLI:
npx skills add adeonir/agent-skillsOr install a single skill:
npx skills add adeonir/agent-skills/<skill-name>| Skill | Description |
|---|---|
| debug-tools | Iterative investigate–fix–verify debugging with confidence scoring |
| git-helpers | Conventional commits, pull requests, and branch lifecycle |
| plain-spoken | STE-inspired technical prose with less jargon and preserved precision |
| review-lens | Confidence-scored pre-PR code review in quick and deep modes |
| rule-creator | Create and manage Claude Code rules in .claude/rules/ |
| spec-driven | Spec-driven feature development from spec to audited delivery, with requirements traceability |
| Skill | Description |
|---|---|
| brainstorm | Structured idea exploration and plan stress-testing, diverge to converge |
| copywriting | Authors copy.yaml — write, extract, refresh, plus critique and audit |
| craft-ui | Wireframe the arrangement, then mockup the visual direction, and deliver the chosen one |
| design-brief | Visual identity — explore a direction, assess or evolve an existing one, and author DESIGN.md |
| docs-writer | Structured docs: PRD, Brief, Design Doc, ADR |
| epic-tracker | Epics, stories, bugs, and tasks — tracked in Linear or GitHub |
| Skill | Description |
|---|---|
| anti-slop | Edit drafts into sharper, more human prose, or detect AI tells without rewriting |
| notes | Obsidian notes for projects, meetings, challenges, and brag docs |
| handoff | Save and resume conversation state across sessions |
| wrap-up | End-of-session context persistence to Obsidian |
flowchart TD
BR[brainstorm] -->|direction| DW_PRD[docs-writer · product]
BR -->|direction| DB[design-brief]
BR -.->|direction| SD[spec-driven]
DW_PRD -->|requirements| DW_DD[docs-writer · technical]
DW_PRD -->|requirements| ET[epic-tracker]
DW_PRD -->|requirements| DB
DW_PRD -->|requirements| CU[craft-ui]
DW_PRD -->|requirements| CW[copywriting]
CW -->|content| CU
DB -->|tokens| CU
CU -->|interface| SD
DW_DD -->|technical doc| SD
DW_DD -->|technical doc| ET
DW_DD -->|technical doc| DB
DW_DD -.->|extract decision| DW_ADR[docs-writer · decision]
ET -->|stories| SD
SD -->|commits & pull requests| GH[git-helpers]
SD -.->|coherence gap| DW_DD
Dashed arrow: optional shortcut for small, well-scoped work. debug-tools, rule-creator, notes, handoff, and wrap-up are available at any point — utilities and reviews used as needed, not mandatory pipeline stages.
The full flow when building a new product or feature with non-trivial business logic:
1. brainstorm --> direction and constraints
2. docs-writer --> requirements (what to build, for whom, why)
3. docs-writer --> technical decisions and trade-offs
4. design-brief --> visual identity and design tokens
5. copywriting --> content and copy
6. craft-ui --> wireframe the arrangement, mockup the visual direction
7. epic-tracker --> epics, stories, acceptance criteria
8. spec-driven --> per-story spec, design, tasks, implementation
9. review-lens --> review changes before commit
10. git-helpers --> commit, pull request, finish branch
spec-driven discovers coherence gaps during implementation and signals back:
spec-driven discovers gap (missing entity, orphan flow, NFR drift)
--> records the gap in PROJECT.md ## Gotchas
--> user reruns docs-writer with update mode
--> docs-writer re-enters the responsible phase scoped to the gap
--> spec-driven resumes with updated technical doc
docs/
├── product/ # brainstorm: brainstorm.md · docs-writer: PRD, brief
├── tech/ # docs-writer: design-doc
├── adr/ # docs-writer: append-only decision log
└── design/ # design-brief: locked direction (moodboard.md) · copywriting: content · craft-ui: chosen mockup
PROJECT.md # spec-driven: committed project memory
.artifacts/
├── specs/ # spec-driven: per-feature artifacts, state, and signals
├── archive/ # spec-driven: features archived manually, in any state
├── LESSONS.md # spec-driven: canonical lessons (machine-owned)
├── research/ # spec-driven: research cache
└── design/ # design-brief: tune session events · craft-ui: structure.yaml + VARIANTS.md + wireframes/ + mockups/
epic-tracker writes no artifacts here — its epics, stories, bugs, and tasks
live in the tracker (Linear or GitHub).
Skills write to docs/ (committed, human-facing) and .artifacts/ (gitignored agent workspace).
MIT