claudify-agent 1.0.1 → 1.0.2

package/.claude/rules/plan-mode-structure.md

@@ -1,166 +1,166 @@
-# Plan Mode Plan Structure
-
-## Required Plan Sections
-
-Every plan MUST include:
-
-1. **Summary** (1-2 sentences)
-   - What will be done
-   - Why it's needed
-
-2. **Files to Create/Modify**
-   - Path and purpose
-   - Reference pattern: "Follow @[file]"
-   - Tools: "Use [tool] for [operation]"
-
-3. **Implementation Steps**
-   - Sequential ordering
-   - Tool for each step
-   - Success metric: "Tests pass", "Lints clear"
-
-4. **Tool Strategy**
-   - Exploration tools
-   - Implementation tools
-   - Validation tools
-   - Question strategy
-
-5. **Testing Strategy**
-   - Test types
-   - Test files to create/modify
-   - Commands to run
-
-6. **Risk Mitigation**
-   - High-risk steps flagged
-   - Fallback strategies
-   - Checkpoint locations
-
-7. **Estimated Time**
-   - Based on complexity
-   - Includes buffer (20%)
-
-## Plan Quality Gates
-
-- [ ] All steps verifiable
-- [ ] Tools specified
-- [ ] Patterns referenced
-- [ ] Risks identified
-- [ ] Tests included
-
-## Enhanced Plan Structure Template
-
-```markdown
-## Files to Create/Modify
-- `path/to/file.ts` - Purpose
-  - Pattern: Follow @[reference file]
-  - Tools: Use StrReplace for edits, Shell for testing
-
-## Implementation Steps
-1. [Step] 
-   - Tool: SemanticSearch to find [X]
-   - Tool: Task subagent to explore [Y]
-   - Tool: ReadLints to verify [Z]
-   - Success: [Verifiable metric]
-
-## Tool Strategy
-- Exploration: SemanticSearch + Task (explore)
-- Implementation: Read/Write/StrReplace
-- Validation: ReadLints + Shell (tests)
-- Questions: AskQuestion for [specific decisions]
-
-## Risk Mitigation
-- If [X] fails → Fallback: [Y]
-- If tests fail → Use /grind loop (max 5 iterations)
-- If stuck → AskQuestion with options
-```
-
-## Examples
-
-### Example 1: Simple Feature
-User: "Add login button"
-
-Plan structure:
-```markdown
-## Summary
-Add login button to header navigation following existing button patterns.
-
-## Files to Modify
-- `components/Header.tsx` - Add login button to nav
-  - Pattern: Follow @components/Button.tsx
-  - Tools: StrReplace for edit, ReadLints for validation
-
-## Implementation Steps
-1. Find existing button patterns
-   - Tool: SemanticSearch: "How are buttons styled?"
-   - Success: Pattern identified
-
-2. Add login button to Header
-   - Tool: StrReplace
-   - Success: Button renders correctly
-
-3. Verify no linting errors
-   - Tool: ReadLints
-   - Success: Zero new lints
-
-## Tool Strategy
-- Exploration: SemanticSearch for button patterns
-- Implementation: StrReplace
-- Validation: ReadLints
-
-## Estimated Time: 10 minutes
-```
-
-### Example 2: Complex Feature
-User: "Add user dashboard"
-
-Plan structure:
-```markdown
-## Summary
-Create user dashboard with stats, activity feed, and settings panel.
-
-## Files to Create
-- `app/dashboard/page.tsx` - Main dashboard page
-  - Pattern: Follow @app/profile/page.tsx
-  - Tools: Write for new file
-- `components/dashboard/StatsCard.tsx` - Stats component
-  - Pattern: Follow @components/Card.tsx
-  - Tools: Write for new file
-- `app/api/dashboard/stats/route.ts` - Stats API
-  - Pattern: Follow @app/api/users/route.ts
-  - Tools: Write for new file
-
-## Implementation Steps
-1. Research existing patterns (3 min)
-   - Tool: Task (explore): "Find page patterns"
-   - Tool: Task (explore): "Find component patterns"
-   - Success: Patterns identified
-
-2. Create API endpoint (5 min)
-   - Tool: Write
-   - Success: Endpoint created, tests pass
-
-3. Build dashboard page (10 min)
-   - Tool: Write
-   - Success: Page renders
-
-4. Create UI components (15 min)
-   - Tool: Write for each component
-   - Success: Components render
-
-5. Integration testing (5 min)
-   - Tool: Shell: npm run test
-   - Tool: ReadLints
-   - Success: All tests pass, zero lints
-
-## Tool Strategy
-- Exploration: Task (explore) x2 in parallel
-- Implementation: Write, StrReplace
-- Validation: Shell (tests), ReadLints
-- Questions: AskQuestion for dashboard widget priorities
-
-## Risk Mitigation
-- If API fails → Fallback: Mock data initially
-- If tests fail → Use /grind loop (max 5 iterations)
-- Checkpoint before: Integration step
-
-## Estimated Time: 45 minutes
-```
+# Plan Mode Plan Structure
+
+## Required Plan Sections
+
+Every plan MUST include:
+
+1. **Summary** (1-2 sentences)
+   - What will be done
+   - Why it's needed
+
+2. **Files to Create/Modify**
+   - Path and purpose
+   - Reference pattern: "Follow @[file]"
+   - Tools: "Use [tool] for [operation]"
+
+3. **Implementation Steps**
+   - Sequential ordering
+   - Tool for each step
+   - Success metric: "Tests pass", "Lints clear"
+
+4. **Tool Strategy**
+   - Exploration tools
+   - Implementation tools
+   - Validation tools
+   - Question strategy
+
+5. **Testing Strategy**
+   - Test types
+   - Test files to create/modify
+   - Commands to run
+
+6. **Risk Mitigation**
+   - High-risk steps flagged
+   - Fallback strategies
+   - Checkpoint locations
+
+7. **Estimated Time**
+   - Based on complexity
+   - Includes buffer (20%)
+
+## Plan Quality Gates
+
+- [ ] All steps verifiable
+- [ ] Tools specified
+- [ ] Patterns referenced
+- [ ] Risks identified
+- [ ] Tests included
+
+## Enhanced Plan Structure Template
+
+```markdown
+## Files to Create/Modify
+- `path/to/file.ts` - Purpose
+  - Pattern: Follow @[reference file]
+  - Tools: Use Edit for edits, Bash for testing
+
+## Implementation Steps
+1. [Step] 
+   - Tool: Explore (quick) to find [X]
+   - Tool: Agent subagent to explore [Y]
+   - Tool: Lint check to verify [Z]
+   - Success: [Verifiable metric]
+
+## Tool Strategy
+- Exploration: Explore (quick) + Agent (Explore)
+- Implementation: Read/Write/Edit
+- Validation: Lint check + Bash (tests)
+- Questions: AskUserQuestion for [specific decisions]
+
+## Risk Mitigation
+- If [X] fails → Fallback: [Y]
+- If tests fail → Use the fix-and-retest loop (max 5 iterations)
+- If stuck → AskUserQuestion with options
+```
+
+## Examples
+
+### Example 1: Simple Feature
+User: "Add login button"
+
+Plan structure:
+```markdown
+## Summary
+Add login button to header navigation following existing button patterns.
+
+## Files to Modify
+- `components/Header.tsx` - Add login button to nav
+  - Pattern: Follow @components/Button.tsx
+  - Tools: Edit for edit, Lint check for validation
+
+## Implementation Steps
+1. Find existing button patterns
+   - Tool: Explore (quick): "How are buttons styled?"
+   - Success: Pattern identified
+
+2. Add login button to Header
+   - Tool: Edit
+   - Success: Button renders correctly
+
+3. Verify no linting errors
+   - Tool: Lint check
+   - Success: Zero new lints
+
+## Tool Strategy
+- Exploration: Explore (quick) for button patterns
+- Implementation: Edit
+- Validation: Lint check
+
+## Estimated Time: 10 minutes
+```
+
+### Example 2: Complex Feature
+User: "Add user dashboard"
+
+Plan structure:
+```markdown
+## Summary
+Create user dashboard with stats, activity feed, and settings panel.
+
+## Files to Create
+- `app/dashboard/page.tsx` - Main dashboard page
+  - Pattern: Follow @app/profile/page.tsx
+  - Tools: Write for new file
+- `components/dashboard/StatsCard.tsx` - Stats component
+  - Pattern: Follow @components/Card.tsx
+  - Tools: Write for new file
+- `app/api/dashboard/stats/route.ts` - Stats API
+  - Pattern: Follow @app/api/users/route.ts
+  - Tools: Write for new file
+
+## Implementation Steps
+1. Research existing patterns (3 min)
+   - Tool: Agent (Explore): "Find page patterns"
+   - Tool: Agent (Explore): "Find component patterns"
+   - Success: Patterns identified
+
+2. Create API endpoint (5 min)
+   - Tool: Write
+   - Success: Endpoint created, tests pass
+
+3. Build dashboard page (10 min)
+   - Tool: Write
+   - Success: Page renders
+
+4. Create UI components (15 min)
+   - Tool: Write for each component
+   - Success: Components render
+
+5. Integration testing (5 min)
+   - Tool: Bash: npm run test
+   - Tool: Lint check
+   - Success: All tests pass, zero lints
+
+## Tool Strategy
+- Exploration: Agent (Explore) x2 in parallel
+- Implementation: Write, Edit
+- Validation: Bash (tests), Lint check
+- Questions: AskUserQuestion for dashboard widget priorities
+
+## Risk Mitigation
+- If API fails → Fallback: Mock data initially
+- If tests fail → Use the fix-and-retest loop (max 5 iterations)
+- Checkpoint before: Integration step
+
+## Estimated Time: 45 minutes
+```

package/.claude/rules/plan-mode-validation.md

@@ -1,130 +1,129 @@
-# Plan Mode Plan Validation
-
-## Automatic Validation Steps
-
-Before presenting plan to user:
-
-1. **Feasibility Check**
-   - Task subagent: "Validate this plan"
-   - Check file accessibility
-   - Verify tool availability
-   - Estimate time accuracy
-
-2. **Dependency Analysis**
-   - Step ordering correct
-   - No missing prerequisites
-   - Parallel opportunities identified
-
-3. **Risk Assessment**
-   - High-risk steps flagged
-   - Fallback strategies defined
-   - Checkpoint locations set
-
-4. **Tool Availability**
-   - MCP servers running
-   - Permissions verified
-   - Alternative tools identified
-
-## Validation Output
-
-If PASS: Present plan to user
-If FAIL: 
-- List specific issues
-- Suggest fixes
-- Auto-correct if possible
-- Re-validate
-
-## Validation Checklist
-
-### Feasibility Check
-- [ ] All required files accessible
-- [ ] No circular dependencies
-- [ ] Estimated time realistic (based on complexity)
-- [ ] Tools available for all steps
-
-### Dependency Analysis
-- [ ] Step ordering correct
-- [ ] No missing prerequisites
-- [ ] Parallel opportunities identified
-
-### Risk Assessment
-- [ ] High-risk steps flagged
-- [ ] Fallback strategies defined
-- [ ] Rollback plan (Checkpoints) identified
-
-### Tool Availability
-- [ ] Required MCP servers running
-- [ ] Permissions verified
-- [ ] Alternative tools identified
-
-## Validation Subagent Pattern
-
-```
-Task:
-  description="Validate implementation plan"
-  prompt="Review this plan for feasibility:
-  
-  ## Plan to Validate
-  [Plan content]
-  
-  ## Validation Checklist
-  1. Check if all referenced files exist
-  2. Verify tool availability
-  3. Estimate actual time based on complexity
-  4. Identify potential blockers
-  5. Suggest improvements
-  
-  ## Output Format
-  Pass/Fail: [Your verdict]
-  Issues: [List specific problems]
-  Suggestions: [Concrete improvements]
-  Confidence: [High/Medium/Low]"
-  subagent_type="generalPurpose"
-  readonly=true
-```
-
-## Examples
-
-### Example 1: Simple Plan Validation
-
-Plan: "Add login button to header"
-
-Validation checks:
-- ✅ File exists: components/Header.tsx
-- ✅ Tool available: StrReplace
-- ✅ Time realistic: 10 minutes
-- ✅ No dependencies
-- ✅ Low risk
-
-Result: PASS → Present to user
-
-### Example 2: Complex Plan Validation
-
-Plan: "Migrate authentication from JWT to sessions"
-
-Validation checks:
-- ✅ Files accessible: src/auth/, app/api/auth/
-- ⚠️ Risk: Breaking change (checkpoint needed)
-- ⚠️ Time: 2 hours might be optimistic → suggest 3 hours
-- ✅ Tools available: Read, Write, Shell, ReadLints
-- ✅ Fallback: Keep JWT code until tests pass
-
-Result: PASS with warnings → Present with caveats
-
-### Example 3: Failed Validation
-
-Plan: "Rewrite entire backend in Rust"
-
-Validation checks:
-- ❌ Time unrealistic: 1 week → needs 2-3 months
-- ❌ Risk: Critical system rewrite
-- ❌ Missing: Testing strategy
-- ❌ Missing: Rollback plan
-- ❌ Dependencies: Team training needed
-
-Result: FAIL → Suggest phased approach:
-1. Start with non-critical service
-2. Add testing strategy
-3. Create rollback plan
-4. Revise time estimate
-5. Re-validate
+# Plan Mode Plan Validation
+
+## Automatic Validation Steps
+
+Before presenting plan to user:
+
+1. **Feasibility Check**
+   - Agent subagent: "Validate this plan"
+   - Check file accessibility
+   - Verify tool availability
+   - Estimate time accuracy
+
+2. **Dependency Analysis**
+   - Step ordering correct
+   - No missing prerequisites
+   - Parallel opportunities identified
+
+3. **Risk Assessment**
+   - High-risk steps flagged
+   - Fallback strategies defined
+   - Checkpoint locations set
+
+4. **Tool Availability**
+   - MCP servers running
+   - Permissions verified
+   - Alternative tools identified
+
+## Validation Output
+
+If PASS: Present plan to user
+If FAIL: 
+- List specific issues
+- Suggest fixes
+- Auto-correct if possible
+- Re-validate
+
+## Validation Checklist
+
+### Feasibility Check
+- [ ] All required files accessible
+- [ ] No circular dependencies
+- [ ] Estimated time realistic (based on complexity)
+- [ ] Tools available for all steps
+
+### Dependency Analysis
+- [ ] Step ordering correct
+- [ ] No missing prerequisites
+- [ ] Parallel opportunities identified
+
+### Risk Assessment
+- [ ] High-risk steps flagged
+- [ ] Fallback strategies defined
+- [ ] Rollback plan (Checkpoints) identified
+
+### Tool Availability
+- [ ] Required MCP servers running
+- [ ] Permissions verified
+- [ ] Alternative tools identified
+
+## Validation Subagent Pattern
+
+```
+Agent:
+  description="Validate implementation plan"
+  prompt="Review this plan for feasibility:
+  
+  ## Plan to Validate
+  [Plan content]
+  
+  ## Validation Checklist
+  1. Check if all referenced files exist
+  2. Verify tool availability
+  3. Estimate actual time based on complexity
+  4. Identify potential blockers
+  5. Suggest improvements
+  
+  ## Output Format
+  Pass/Fail: [Your verdict]
+  Issues: [List specific problems]
+  Suggestions: [Concrete improvements]
+  Confidence: [High/Medium/Low]"
+  subagent_type="Plan"  // read-only architect agent
+```
+
+## Examples
+
+### Example 1: Simple Plan Validation
+
+Plan: "Add login button to header"
+
+Validation checks:
+- ✅ File exists: components/Header.tsx
+- ✅ Tool available: Edit
+- ✅ Time realistic: 10 minutes
+- ✅ No dependencies
+- ✅ Low risk
+
+Result: PASS → Present to user
+
+### Example 2: Complex Plan Validation
+
+Plan: "Migrate authentication from JWT to sessions"
+
+Validation checks:
+- ✅ Files accessible: src/auth/, app/api/auth/
+- ⚠️ Risk: Breaking change (checkpoint needed)
+- ⚠️ Time: 2 hours might be optimistic → suggest 3 hours
+- ✅ Tools available: Read, Write, Bash, Lint check
+- ✅ Fallback: Keep JWT code until tests pass
+
+Result: PASS with warnings → Present with caveats
+
+### Example 3: Failed Validation
+
+Plan: "Rewrite entire backend in Rust"
+
+Validation checks:
+- ❌ Time unrealistic: 1 week → needs 2-3 months
+- ❌ Risk: Critical system rewrite
+- ❌ Missing: Testing strategy
+- ❌ Missing: Rollback plan
+- ❌ Dependencies: Team training needed
+
+Result: FAIL → Suggest phased approach:
+1. Start with non-critical service
+2. Add testing strategy
+3. Create rollback plan
+4. Revise time estimate
+5. Re-validate

package/.claude/rules/security-critical.md

@@ -1,19 +1,19 @@
-# Security-Critical Operations
-
-## Triggers
-Keywords: "auth", "security", "password", "token", "encrypt", "API key", "secret", "credential"
-
-## Critical Rules
-- Never hardcode credentials - use environment variables
-- Always validate and sanitize user input
-- Use parameterized queries (no SQL injection)
-- Hash passwords with bcrypt/argon2
-- Use strong crypto (SHA-256+, AES-256)
-
-## Security Checklist
-See `.cursor/security-report.md` for OWASP Top 10 checklist
-
-## Examples
-- Auth pattern: `@src/auth/validateToken.ts`
-- Password hashing: `@src/lib/password.ts`
-- Input validation: `@src/validators/userSchema.ts`
+# Security-Critical Operations
+
+## Triggers
+Keywords: "auth", "security", "password", "token", "encrypt", "API key", "secret", "credential"
+
+## Critical Rules
+- Never hardcode credentials - use environment variables
+- Always validate and sanitize user input
+- Use parameterized queries (no SQL injection)
+- Hash passwords with bcrypt/argon2
+- Use strong crypto (SHA-256+, AES-256)
+
+## Security Checklist
+See `.claude/security-report.md` for OWASP Top 10 checklist
+
+## Examples
+- Auth pattern: `@src/auth/validateToken.ts`
+- Password hashing: `@src/lib/password.ts`
+- Input validation: `@src/validators/userSchema.ts`