v2.1: Unify skills and slash commands pattern (#5)

* v2.1: Unify skills and slash commands pattern

Following the new Claude Code standard where skills and slash commands
are merged into a single unified pattern:

- Convert commands to skills: /daily-workflow, /weekly-review, /push, /onboard
- Each skill has SKILL.md with frontmatter (name, description, allowed-tools)
- Skills can be invoked with /skill-name OR auto-discovered by Claude
- Remove deprecated .claude/commands/ directory
- Update all documentation to reference new unified pattern
- Update agents to reference skills instead of commands
- Update CLAUDE.md with unified skills table

This aligns with Claude Code 2.1+ where skills and slash commands
share the same features and invocation patterns.

* Simplify skill names: daily-workflow → daily, weekly-review → weekly

Rename verbose skill folders and names to shorter, cleaner invocations:
- daily-workflow/ → daily/ (invoked with /daily)
- weekly-review/ → weekly/ (invoked with /weekly)

Update all references across documentation, agents, and skill files
to use consistent short command names.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
Bill Allred
2026-01-12 11:57:37 -08:00
committed by GitHub
parent 3d66b2121a
commit fa10141e9e
16 changed files with 689 additions and 969 deletions

View File

@@ -1,12 +1,53 @@
---
name: daily-workflow
description: Morning routine, midday check-in, and evening shutdown workflows. Structure daily planning, task review, and end-of-day reflection. Use for daily productivity routines.
name: daily
description: Create daily notes and manage morning, midday, and evening routines. Structure daily planning, task review, and end-of-day reflection. Use for daily productivity routines or when asked to create today's note.
allowed-tools: Read, Write, Edit, Glob, Grep
user-invocable: true
---
# Daily Workflow Skill
Structured workflows for morning planning, midday check-ins, and evening shutdowns.
Creates daily notes and provides structured workflows for morning planning, midday check-ins, and evening shutdowns.
## Usage
Invoke with `/daily` or ask Claude to create today's note or help with daily routines.
### Create Today's Note
```
/daily
```
Or simply ask:
- "Create today's daily note"
- "Start my morning routine"
- "Help me with evening shutdown"
## Daily Note Creation
### What Happens
1. **Checks if today's note exists**
- If yes: Opens the existing note
- If no: Creates new note from template
2. **Template Processing**
- Replaces `{{date}}` with today's date
- Replaces `{{date:format}}` with formatted dates
- Handles date arithmetic (e.g., `{{date-1}}` for yesterday)
3. **Automatic Organization**
- Places note in `Daily Notes/` folder
- Names file with today's date (YYYY-MM-DD.md)
- Preserves template structure
### Template Variables
Your daily template can use:
- `{{date}}` - Today's date in default format
- `{{date:dddd}}` - Day name (e.g., Monday)
- `{{date:MMMM DD, YYYY}}` - Formatted date
- `{{date-1:YYYY-MM-DD}}` - Yesterday's date
- `{{date+1:YYYY-MM-DD}}` - Tomorrow's date
- `{{time}}` - Current time
## Morning Routine (5-10 minutes)
@@ -72,9 +113,9 @@ Structured workflows for morning planning, midday check-ins, and evening shutdow
- [ ] Tomorrow's priority identified
- [ ] Changes committed
## Daily Note Sections
## Daily Note Structure
Standard daily note structure:
Standard daily note template:
```markdown
# {{date}}
@@ -83,9 +124,9 @@ Standard daily note structure:
> What's the ONE thing that would make today successful?
## Time Blocks
- 🌅 Morning (9-12):
- ☀️ Afternoon (12-5):
- 🌙 Evening (5+):
- Morning (9-12):
- Afternoon (12-5):
- Evening (5+):
## Tasks
### Must Do Today
@@ -121,10 +162,30 @@ Standard daily note structure:
- Minimize context switching
- Protect deep work blocks
## Configuration
Customize paths to match your vault:
- Daily notes folder: `Daily Notes/`
- Template location: `Templates/Daily Template.md`
- Date format: `YYYY-MM-DD`
### Different Date Formats
- `YYYY-MM-DD` - Standard ISO format (recommended)
- `MM-DD-YYYY` - US format
- `DD-MM-YYYY` - European format
- `YYYY-MM-DD-ddd` - Include day abbreviation
### Folder Organization by Month
Organize daily notes by month/year:
```
Daily Notes/2024/01/2024-01-15.md
```
## Integration
Works with:
- `/daily` command for note creation
- `/push` command for end-of-day commit
- Productivity Coach for accountability
- Goal Tracking skill for alignment
- `/push` - Commit end-of-day changes
- `/weekly` - Weekly planning uses daily notes
- `/onboard` - Load context before planning
- Goal tracking skill - Align daily tasks to goals
- Productivity Coach - Accountability for daily routines

View File

@@ -0,0 +1,181 @@
---
name: onboard
description: Load CLAUDE.md context files from vault for comprehensive understanding. Discovers hierarchical context, recent notes, and project states. Use at start of session or when Claude needs full vault context.
allowed-tools: Read, Glob, Grep
user-invocable: true
---
# Onboard Skill
Loads all CLAUDE.md files from your vault to provide comprehensive context for intelligent assistance.
## Usage
Invoke with `/onboard` or ask Claude to learn about your vault.
### Full Context Load
```
/onboard
```
### Specific Project Context
```
/onboard Projects/MyProject
```
## What This Skill Does
1. **Discovers Context Files**
- Searches for all CLAUDE.md files
- Traverses project directories
- Respects depth limits
2. **Loads Hierarchical Context**
- Root CLAUDE.md first (global context)
- Project-specific CLAUDE.md files
- Recent daily notes for current state
3. **Builds Understanding**
- Your personal mission/goals
- Project structures and status
- Workflow preferences
- Custom conventions
## Context Hierarchy
```
vault/
├── CLAUDE.md # [1] Global context - loaded first
├── Projects/
│ ├── Project A/
│ │ └── CLAUDE.md # [2] Project context
│ └── Project B/
│ └── CLAUDE.md # [3] Another project context
└── Areas/
└── Health/
└── CLAUDE.md # [4] Area-specific context
```
## CLAUDE.md File Structure
### Root CLAUDE.md Should Include
```markdown
# System Context for Claude
## Personal Mission
[Your life mission/purpose]
## Current Focus
[What you're working on now]
## Preferences
- Writing style: [Formal/Casual/Technical]
- Detail level: [High/Medium/Low]
## Conventions
- File naming: [Your patterns]
- Tag system: [Your tags]
```
### Project CLAUDE.md Should Include
```markdown
# Project: [Name]
## Overview
[What this project is about]
## Current Status
[Where things stand]
## Key Decisions
[Important choices made]
## Next Steps
[What needs to happen]
```
## Smart Context Loading
### Recent Activity
Automatically considers:
- Last 7 days of daily notes
- Current week's review
- Recently modified projects
### Selective Loading
For focused assistance:
```
/onboard Projects/WebApp # Only specific project
/onboard Goals # Only goals context
```
## Use Cases
### Starting a Session
```
/onboard
"Help me plan my day based on my goals"
```
### Project Work
```
/onboard Projects/MyApp
"Help me refactor the authentication module"
```
### Weekly Planning
```
/onboard Goals
"Analyze my week and suggest improvements"
```
## Context Variables
Your CLAUDE.md files can include preferences:
```markdown
## Variables for Claude
- DEFAULT_LANGUAGE: JavaScript
- TIMEZONE: America/New_York
- COMMUNICATION_STYLE: Direct and concise
```
## Best Practices
### Keep Context Updated
- Review CLAUDE.md files monthly
- Update after major decisions
- Remove outdated information
- Add new learnings
### Be Specific
- Clear project descriptions
- Specific preferences
- Concrete examples
- Defined conventions
### Hierarchical Information
- Global → Area → Project → Task
- General → Specific
- Strategic → Tactical
## Privacy & Security
### Never Include in CLAUDE.md
- Passwords or credentials
- Personal identification numbers
- Financial account details
- Private API keys
### Safe Context Examples
- "I work in healthcare technology"
- "My projects involve web development"
- "I prefer morning work sessions"
## Integration
Works with:
- All other skills (provides context)
- `/daily` - Better daily planning with context
- `/weekly` - Informed weekly reviews
- Goal tracking - Understand goal cascade

View File

@@ -0,0 +1,145 @@
---
name: push
description: Commit and push vault changes to Git with smart commit messages. Auto-stages files, creates meaningful commits, and syncs with remote. Use after making vault changes or at end of day.
allowed-tools: Bash, Read, Glob
user-invocable: true
---
# Git Push Skill
Automates Git workflow to save your notes with meaningful commit messages and push to remote repository.
## Usage
Invoke with `/push` or ask Claude to save/commit your changes.
### Basic Usage
```
/push
```
### With Custom Message
```
/push "Completed project planning"
```
## What This Skill Does
1. **Stages All Changes**
- Adds all modified files
- Includes new files
- Removes deleted files
2. **Creates Smart Commit Message**
- Uses provided message, or
- Auto-generates from changes
- Includes date/time stamp
- Summarizes key modifications
3. **Syncs with Remote**
- Pulls latest changes (if enabled)
- Pushes to remote repository
- Handles merge conflicts gracefully
## Commit Message Format
### Automatic Messages
Based on your changes:
```
Daily note for 2024-01-15 + 3 project updates
- Added: Daily Notes/2024-01-15.md
- Modified: Projects/Learning Spanish/notes.md
- Modified: Goals/2. Monthly Goals.md
```
### With Timestamp
```
[2024-01-15 09:30] Completed weekly review
```
## Workflow Integration
### Morning Routine
```
/daily # Create daily note
# ... work on notes ...
/push "Morning planning complete"
```
### End of Day
```
# Complete daily reflection
/push # Auto-message with summary
```
### After Weekly Review
```
/weekly # Run weekly review
/push "Weekly review - Week 3"
```
## Git Operations
### Standard Flow
1. `git add .` - Stage all changes
2. `git commit -m "message"` - Create commit
3. `git pull --rebase origin main` - Get remote changes
4. `git push origin main` - Push to remote
### Safety Checks
- Verify Git repository exists
- Check for uncommitted changes
- Ensure remote is configured
- Validate branch exists
## Conflict Handling
If conflicts occur:
1. Auto-resolve attempts (favor local for notes)
2. If manual resolution needed, guide through process
3. Never force push without explicit request
## Security Considerations
### Never Commit
- Passwords or credentials
- API keys
- Personal identification
- Financial information
### Use .gitignore for
```
private/
credentials.md
.env
.obsidian/workspace*
.obsidian/cache
.trash/
.DS_Store
```
## Troubleshooting
### Push Rejected?
Pull first, then push again:
```bash
git pull --rebase origin main
git push origin main
```
### Not a Git Repository?
```bash
git init
git remote add origin [URL]
```
### Large Files Issue?
Consider Git LFS for images/attachments.
## Integration
Works with:
- `/daily` - Commit after creating daily note
- `/weekly` - Commit after weekly review
- `/onboard` - No git needed for context loading
- Auto-commit hook for automatic saves

View File

@@ -0,0 +1,173 @@
---
name: weekly
description: Facilitate weekly review process with reflection, goal alignment, and planning. Create review notes, analyze past week, plan next week. Use on Sundays or whenever doing weekly planning.
allowed-tools: Read, Write, Edit, Glob, Grep
user-invocable: true
---
# Weekly Review Skill
Facilitates your weekly review process by creating a review note and guiding reflection on the past week while planning the next.
## Usage
Invoke with `/weekly` or ask Claude to help with your weekly review.
```
/weekly
```
## What This Skill Does
1. **Creates Weekly Review Note**
- Uses weekly review template
- Names it with current week's date
- Places in Goals folder
2. **Guides Review Process**
- Reviews last week's accomplishments
- Identifies incomplete tasks
- Plans upcoming week
- Aligns with monthly goals
3. **Automates Housekeeping**
- Archives old daily notes
- Updates project statuses
- Cleans up completed tasks
## Review Process Steps
### Step 1: Reflection (10 minutes)
- Review daily notes from past week
- Identify wins and challenges
- Capture lessons learned
### Step 2: Goal Alignment (10 minutes)
- Check monthly goal progress
- Adjust weekly priorities
- Ensure alignment with yearly goals
### Step 3: Planning (10 minutes)
- Set ONE big thing for the week
- Schedule important tasks
- Block time for deep work
## Interactive Prompts
The skill guides you through:
1. **"What were your top 3 wins this week?"**
- Celebrates progress
- Builds momentum
- Documents achievements
2. **"What were your main challenges?"**
- Identifies obstacles
- Plans solutions
- Learns from difficulties
3. **"What's your ONE big thing next week?"**
- Forces prioritization
- Creates focus
- Drives meaningful progress
## Weekly Review Checklist
- [ ] Review all daily notes
- [ ] Process inbox items
- [ ] Update project statuses
- [ ] Check upcoming calendar
- [ ] Review monthly goals
- [ ] Plan next week's priorities
- [ ] Block time for important work
- [ ] Clean digital workspace
- [ ] Archive completed items
- [ ] Commit changes to Git
## Weekly Review Note Format
```markdown
# Weekly Review: YYYY-MM-DD
## Last Week's Wins
1.
2.
3.
## Challenges & Lessons
- Challenge:
- Lesson:
## Goal Progress
### Monthly Goals
- [ ] Goal 1 (XX%)
- [ ] Goal 2 (XX%)
### This Week's Contribution
- [Task] -> [[Goal]]
## Next Week Planning
### ONE Big Thing
>
### Key Tasks
- [ ]
- [ ]
- [ ]
### Time Blocks
- Monday:
- Tuesday:
- Wednesday:
- Thursday:
- Friday:
## Notes
```
## Automation Features
### Auto-Archive
Suggest moving daily notes older than 30 days to Archives.
### Project Status Update
For each active project:
- Update completion percentage
- Note blockers
- Set next actions
### Habit Tracking
Calculate habit success rates from daily notes:
- Count habit checkboxes
- Show completion percentage
- Identify patterns
## Best Practices
### Consistent Timing
- Same day each week (Sunday recommended)
- Same time if possible
- Block calendar time
- Treat as non-negotiable
### Preparation
- Clean inbox before review
- Have calendar ready
- Gather project updates
- Review any feedback
### Follow-through
- Share highlights with team/family
- Update external systems
- Communicate changes
- Celebrate wins
## Integration
Works with:
- `/daily` - Reviews daily notes from the week
- `/push` - Commit after completing review
- `/onboard` - Load context for informed review
- Goal tracking skill - Progress calculations
- `/daily` skill - Plan next week's routines