feat: implement profile validation mechanism
Add /validate-profile slash command and automatic validation before application generation. Implementation: - Created src/.claude/commands/validate-profile.md with validation logic - Detects placeholder patterns like [Your name], [Company], etc. - Checks required sections: Personal Info, Summary, Work Experience - Allows optional sections to be empty (Projects, Certifications) - Provides clear pass/fail feedback with actionable guidance - Updated src/CLAUDE.md to require validation before applications - Added Profile Validation section with validation process - Integrated validation as step 0 in workflow - Documented explicit skip validation option with warning - Added /validate-profile to Available Commands - All 15 tasks completed and validated Implements: add-profile-validation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -2,27 +2,27 @@
|
||||
|
||||
## 1. Create Slash Command Structure
|
||||
|
||||
- [ ] 1.1 Create `src/.claude/` directory
|
||||
- [ ] 1.2 Create `src/.claude/commands/` directory
|
||||
- [x] 1.1 Create `src/.claude/` directory
|
||||
- [x] 1.2 Create `src/.claude/commands/` directory
|
||||
|
||||
## 2. Implement Validation Slash Command
|
||||
|
||||
- [ ] 2.1 Create `src/.claude/commands/validate-profile.md` with validation instructions
|
||||
- [ ] 2.2 Define validation rules for detecting placeholder patterns
|
||||
- [ ] 2.3 Specify required sections that must be complete (Personal Info, Summary, at least one Work Experience)
|
||||
- [ ] 2.4 Specify optional sections that can be empty
|
||||
- [ ] 2.5 Include clear output format for validation results (success or list of incomplete sections)
|
||||
- [x] 2.1 Create `src/.claude/commands/validate-profile.md` with validation instructions
|
||||
- [x] 2.2 Define validation rules for detecting placeholder patterns
|
||||
- [x] 2.3 Specify required sections that must be complete (Personal Info, Summary, at least one Work Experience)
|
||||
- [x] 2.4 Specify optional sections that can be empty
|
||||
- [x] 2.5 Include clear output format for validation results (success or list of incomplete sections)
|
||||
|
||||
## 3. Update Framework Instructions
|
||||
|
||||
- [ ] 3.1 Update `src/CLAUDE.md` to add automatic validation requirement before application generation
|
||||
- [ ] 3.2 Add instructions for when to run `/validate-profile`
|
||||
- [ ] 3.3 Add guidance on handling validation failures
|
||||
- [ ] 3.4 Document the explicit skip validation option
|
||||
- [x] 3.1 Update `src/CLAUDE.md` to add automatic validation requirement before application generation
|
||||
- [x] 3.2 Add instructions for when to run `/validate-profile`
|
||||
- [x] 3.3 Add guidance on handling validation failures
|
||||
- [x] 3.4 Document the explicit skip validation option
|
||||
|
||||
## 4. Validation
|
||||
|
||||
- [ ] 4.1 Verify `/validate-profile` command file is complete and well-documented
|
||||
- [ ] 4.2 Verify `src/CLAUDE.md` correctly requires validation before applications
|
||||
- [ ] 4.3 Test validation logic detects common placeholder patterns
|
||||
- [ ] 4.4 Ensure validation provides helpful feedback on incomplete sections
|
||||
- [x] 4.1 Verify `/validate-profile` command file is complete and well-documented
|
||||
- [x] 4.2 Verify `src/CLAUDE.md` correctly requires validation before applications
|
||||
- [x] 4.3 Test validation logic detects common placeholder patterns
|
||||
- [x] 4.4 Ensure validation provides helpful feedback on incomplete sections
|
||||
|
||||
Reference in New Issue
Block a user