Reusable Claude Code skills shared across projects via symlinks into ~/.claude/skills/. Includes the /reflect skill for structured milestone reflections. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
911 B
911 B
Custom Claude Skills — Future Ideas
F1: Pre-commit validation skill
- Problem: The "validate locally, deploy once" pattern is frequently violated — errors caught in prod that could be caught locally
- Idea: A
/validateskill that detects the project type and runs appropriate local validation (helm template, kustomize build, docker compose config, etc.) - Open questions: How to detect project type reliably? Should it be one skill or per-type?
- Depends on: More experience with which validations are commonly missed
F2: Milestone setup skill
- Problem: Starting a new milestone has boilerplate (create verify script skeleton, update README table, etc.)
- Idea: A
/new-milestone M9 "Velero backup"skill that scaffolds the milestone - Open questions: How much should be templated vs. left to Claude?
- Depends on: Stable milestone conventions across projects