gurixandClaude
f1ba0dd98d
Add structured workflow for managing job applications with /new-application and /populate-application commands. Users can now organize applications in dated folders, store job documents, and have AI analyze requirements to populate strategy documents. Includes bug fix for src/ path references and safe update documentation. OpenSpec: add-application-management 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
106 lines
3.5 KiB
Markdown
106 lines
3.5 KiB
Markdown
<!-- OPENSPEC:START -->
|
|
# OpenSpec Instructions
|
|
|
|
These instructions are for AI assistants working in this project.
|
|
|
|
Always open `@/openspec/AGENTS.md` when the request:
|
|
- Mentions planning or proposals (words like proposal, spec, change, plan)
|
|
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
|
|
- Sounds ambiguous and you need the authoritative spec before coding
|
|
|
|
Use `@/openspec/AGENTS.md` to learn:
|
|
- How to create and apply change proposals
|
|
- Spec format and conventions
|
|
- Project structure and guidelines
|
|
|
|
Keep this managed block so 'openspec update' can refresh the instructions.
|
|
|
|
<!-- OPENSPEC:END -->
|
|
|
|
---
|
|
|
|
# Updating the Test Framework
|
|
|
|
## ⚠️ CRITICAL: Preserve User Data During Updates
|
|
|
|
When updating the test framework at `~/workspace/test-bewerbungen/`, you MUST preserve user data files. **NEVER** use `cp -r src/* ~/workspace/test-bewerbungen/` as this overwrites everything including user work.
|
|
|
|
## Protected Files & Folders
|
|
|
|
**NEVER overwrite these in the test directory:**
|
|
- `profile.md` - Contains user's personal and professional information
|
|
- `applications/` folder - Contains all job application work in progress
|
|
- Any PDF files - User's CVs, certificates, or job-related documents
|
|
- Any user-created files or modifications
|
|
|
|
## Safe Update Process
|
|
|
|
### Method 1: Selective File Update (Recommended)
|
|
|
|
Update only framework code files, preserving user data:
|
|
|
|
```bash
|
|
# Update main instruction file
|
|
cp src/CLAUDE.md ~/workspace/test-bewerbungen/
|
|
|
|
# Update slash commands and templates
|
|
cp -r src/.claude ~/workspace/test-bewerbungen/
|
|
|
|
# ONLY create applications directory if it doesn't exist
|
|
# (don't overwrite existing one with user's applications)
|
|
if [ ! -d ~/workspace/test-bewerbungen/applications ]; then
|
|
mkdir -p ~/workspace/test-bewerbungen/applications/pending
|
|
fi
|
|
```
|
|
|
|
### Method 2: Manual Selective Copy
|
|
|
|
For more control, copy specific files individually:
|
|
|
|
```bash
|
|
# Framework instructions
|
|
cp src/CLAUDE.md ~/workspace/test-bewerbungen/
|
|
|
|
# Slash commands
|
|
cp src/.claude/commands/new-application.md ~/workspace/test-bewerbungen/.claude/commands/
|
|
cp src/.claude/commands/populate-application.md ~/workspace/test-bewerbungen/.claude/commands/
|
|
cp src/.claude/commands/validate-profile.md ~/workspace/test-bewerbungen/.claude/commands/
|
|
|
|
# Templates
|
|
cp src/.claude/templates/application-template.md ~/workspace/test-bewerbungen/.claude/templates/
|
|
```
|
|
|
|
### ❌ NEVER Use These Commands on Test Directory
|
|
|
|
```bash
|
|
# DANGEROUS - Overwrites everything including user data
|
|
cp -r src/* ~/workspace/test-bewerbungen/
|
|
|
|
# DANGEROUS - Overwrites user's profile
|
|
cp src/profile.md ~/workspace/test-bewerbungen/
|
|
|
|
# DANGEROUS - Deletes user's applications
|
|
rm -rf ~/workspace/test-bewerbungen/applications/
|
|
```
|
|
|
|
## When to Update Test Framework
|
|
|
|
Update the test directory when:
|
|
- Adding new slash commands to `src/.claude/commands/`
|
|
- Modifying the application template in `src/.claude/templates/`
|
|
- Updating framework instructions in `src/CLAUDE.md`
|
|
- Fixing bugs in command logic
|
|
|
|
**Do NOT update** `profile.md` or touch the `applications/` folder - these belong to the user.
|
|
|
|
## Workflow Summary
|
|
|
|
1. **Make changes** to framework files in `src/`
|
|
2. **Test locally** in development environment first
|
|
3. **Selectively copy** only framework files to test directory
|
|
4. **Verify** user data (`profile.md`, `applications/`) remains intact
|
|
5. **Test** the updated commands in the test environment
|
|
|
|
---
|
|
|
|
**Remember**: The test directory simulates a real user's environment. Treat user data with care! |