Initial project setup with reflect skill

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>
This commit is contained in:
Paul O'Reilly
2026-03-11 15:33:46 +13:00
commit 5ff98763cd
6 changed files with 244 additions and 0 deletions

13
FUTURE.md Normal file
View File

@@ -0,0 +1,13 @@
# 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 `/validate` skill 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