Bump actions/checkout from v5 to v6

.claude/.gitignore

@@ -1,32 +1,25 @@
-# macOS
-.DS_Store
-
+# Build artifacts
 # Editor/IDE
-*.swp
-*.local.json
-
+# Logs
+# Node.js (for testing/examples)
 # Python (for testing/examples)
+# Temporary files
+# macOS
+*.local.json
+*.log
 *.pyc
-__pycache__/
+*.swp
+*.temp
+*.tmp
+.DS_Store
+.created-prompts/
+.pnpm-store/
 .pytest_cache/
-.venv/
 .ruff_cache/
-
-# Node.js (for testing/examples)
-node_modules/
-.pnpm-store/
-
-# Build artifacts
+.venv/
+__pycache__/
 bin/
-lib/
-dist/
 build/
-
-# Logs
-*.log
-
-# Temporary files
-*.tmp
-*.temp
-
-.created-prompts/
+dist/
+lib/
+node_modules/

.claude/commands/ai-coding-config.md

@@ -5,7 +5,9 @@ argument-hint: [update | add]
 
 # AI Coding Configuration
 
-Manages reusable AI configurations across machines and projects. The system lives in `~/.ai_coding_config` and contains Cursor rules, Claude commands, agents, skills, personalities, and GitHub workflows.
+Manages reusable AI configurations across machines and projects. The system lives in
+`~/.ai_coding_config` and contains Cursor rules, Claude commands, agents, skills,
+personalities, and GitHub workflows.
 
 ## Usage
 
@@ -15,7 +17,10 @@ Manages reusable AI configurations across machines and projects. The system live
 
 ## Interaction Guidelines
 
-Use AskUserQuestion when presenting discrete choices that save the user time (selecting a personality, choosing update strategy, handling file conflicts). This lets users quickly click options while still allowing free-form text via "Other". Only use when it genuinely speeds up the interaction.
+Use AskUserQuestion when presenting discrete choices that save the user time (selecting
+a personality, choosing update strategy, handling file conflicts). This lets users
+quickly click options while still allowing free-form text via "Other". Only use when it
+genuinely speeds up the interaction.
 
 ---
 
@@ -34,11 +39,13 @@ Detect project type and framework specifics. Django differs from FastAPI. React
 Show available configurations that match this project. Group by relevance - framework-specific first, then universal. For each option, read description from frontmatter to explain what it does.
 
 Available configurations:
+
 - Rules (`.cursor/rules/` subdirectories and files)
 - Personalities (one or none, common-personality always included)
 - Agents (specialized AI assistants, default to all)
 - Skills (modular packages, default to all)
-- Commands (always copy all, create in `.claude/commands/` with symlinks in `.cursor/commands/`)
+- Commands (always copy all, create in `.claude/commands/` with symlinks in
+  `.cursor/commands/`)
 - Standard configs (VSCode settings, Prettier, GitHub workflows)
 
 Use AskUserQuestion to present personality options as quick-select.
@@ -47,32 +54,37 @@ Use AskUserQuestion to present personality options as quick-select.
 <file-installation>
 Copy selected configurations intelligently, respecting existing customizations. Compare files with diff when they exist. For conflicts, use AskUserQuestion to offer choices (overwrite, skip, show diff, or custom action). Never silently overwrite.
 
-Installation mapping: Rules → `.cursor/rules/` (preserve subdirectory structure), Commands → `.claude/commands/` with symlinks in `.cursor/commands/`, Context → `.claude/context.md`, Agents → `.claude/agents/`, Skills → `.skills/` (entire directories), Personalities → `.cursor/rules/personalities/` (common always, additional with `alwaysApply: true`), VSCode → `.vscode/`, Prettier → `.prettierrc`, GitHub workflows → `.github/workflows/`, Gitignore → `.cursor/.gitignore` and `.claude/.gitignore`.
+Installation mapping: Rules → `.cursor/rules/` (preserve subdirectory structure),
+Commands → `.claude/commands/` with symlinks in `.cursor/commands/`, Context →
+`.claude/context.md`, Agents → `.claude/agents/`, Skills → `.skills/` (entire
+directories), Personalities → `.cursor/rules/personalities/` (common always, additional
+with `alwaysApply: true`), VSCode → `.vscode/`, Prettier → `.prettierrc`, GitHub
+workflows → `.github/workflows/`, Gitignore → `.cursor/.gitignore` and
+`.claude/.gitignore`.
 
-Report what was copied, skipped, and how conflicts were handled.
-</file-installation>
+Report what was copied, skipped, and how conflicts were handled. </file-installation>
 
 <installation-verification>
 Confirm files are in expected locations. List installed rules (framework-specific, then universal), commands, agents, skills. Confirm symlinks point correctly. Verify personality selection and `alwaysApply` setting. Confirm VSCode settings, Prettier config, GitHub workflows, and gitignore files.
 
-Provide clear summary without deep validation.
-</installation-verification>
+Provide clear summary without deep validation. </installation-verification>
 
 <recommendations>
 After successful installation, provide actionable next steps.
 
 Always recommend:
+
 1. Generate AGENTS.md if missing at project root (run /generate-AGENTS-file)
-2. List available commands (/load-cursor-rules, /personality-change, /create-prompt, /troubleshoot, /setup-environment, /handoff-context, /product-intel)
+2. List available commands (/load-cursor-rules, /personality-change, /create-prompt,
+   /troubleshoot, /setup-environment, /handoff-context, /product-intel)
 
 Conditional recommendations:
+
 - Git worktrees → suggest /setup-environment
 - Error monitoring detected → mention /troubleshoot
 - Competitive product → suggest /product-intel
 
-Show only genuinely useful recommendations.
-</recommendations>
-</setup-mode>
+Show only genuinely useful recommendations. </recommendations> </setup-mode>
 
 ---
 
@@ -90,11 +102,12 @@ Compare this command file with repo version. If repo version is newer or differe
 <configuration-comparison>
 Use diff to compare each config file. Categorize changes as trivial (typos, comments) or significant. List files in repo but not in project. List files in project but not in repo (possible local customizations).
 
-Explain what changed and why updates matter. Use AskUserQuestion for update strategy: "Update all", "Update none", "Pick individually", or custom instructions. Handle customized files carefully.
+Explain what changed and why updates matter. Use AskUserQuestion for update strategy:
+"Update all", "Update none", "Pick individually", or custom instructions. Handle
+customized files carefully.
 
 Copy selected files. Never silently overwrite. Verify and highlight changes.
-</configuration-comparison>
-</update-mode>
+</configuration-comparison> </update-mode>
 
 ---
 
@@ -112,42 +125,50 @@ Fetch latest Claude Code documentation for the mechanism you're implementing (co
 <mechanism-selection>
 Decision framework:
 
-Trigger: User manually → Command, Claude autonomously → Skill, Claude delegates focused work → Agent, Bundling multiple mechanisms → Plugin
+Trigger: User manually → Command, Claude autonomously → Skill, Claude delegates focused
+work → Agent, Bundling multiple mechanisms → Plugin
 
 Context: Needs isolation → Agent, Uses main conversation → Command or Skill
 
-Compatibility: Commands work in both Claude Code and Cursor, Skills are Claude Code only (create companion Command for Cursor if needed), Agents work in Claude Code (Cursor can @ mention paths), Plugins are Claude Code only
+Compatibility: Commands work in both Claude Code and Cursor, Skills are Claude Code only
+(create companion Command for Cursor if needed), Agents work in Claude Code (Cursor can
+@ mention paths), Plugins are Claude Code only
 
 Clarifying questions:
+
 1. Who triggers this - user manually or Claude autonomously?
 2. Needs isolated context window or uses main conversation?
 3. Must work in Cursor or Claude Code only acceptable?
-4. Single capability or bundling multiple features?
-</mechanism-selection>
+4. Single capability or bundling multiple features? </mechanism-selection>
 
 <artifact-creation>
 Commands: Create `.claude/commands/command-name.md` with frontmatter including description.
 
-Skills: Create `.claude/skills/skill-name/SKILL.md` with frontmatter (name, description). Description is critical - Claude uses it to decide when to activate. Add supporting files as needed. Create companion Command for Cursor if needed.
+Skills: Create `.claude/skills/skill-name/SKILL.md` with frontmatter (name,
+description). Description is critical - Claude uses it to decide when to activate. Add
+supporting files as needed. Create companion Command for Cursor if needed.
 
-Agents: Determine plugin location (or create new plugin). Create `plugins/plugin-name/agents/agent-name.md` with frontmatter (name, description, tools, model). Agents live in plugins.
+Agents: Determine plugin location (or create new plugin). Create
+`plugins/plugin-name/agents/agent-name.md` with frontmatter (name, description, tools,
+model). Agents live in plugins.
 
-Plugins: Create `plugins/plugin-name/` directory structure with `.claude-plugin/plugin.json` manifest. Bundle commands (via symlinks), skills, agents, hooks, MCP servers. Add README.md. Update `.claude-plugin/marketplace.json`.
+Plugins: Create `plugins/plugin-name/` directory structure with
+`.claude-plugin/plugin.json` manifest. Bundle commands (via symlinks), skills, agents,
+hooks, MCP servers. Add README.md. Update `.claude-plugin/marketplace.json`.
 </artifact-creation>
 
 <creation-verification>
 Verify files are in correct locations, frontmatter includes required fields, skill descriptions clearly define activation criteria, commands work when invoked, plugins are properly structured.
 
-Explain what was created and how to test it.
-</creation-verification>
-</add-mode>
+Explain what was created and how to test it. </creation-verification> </add-mode>
 
 ---
 
 <execution-philosophy>
 Work conversationally, not robotically. Focus on outcomes. Determine best approach for each situation. Show file paths when copying. Let users make all choices. Verify everything works before finishing.
 
-Respect existing files - always check before overwriting. Use diff to understand differences, then decide intelligently or ask. Better to be thoughtful than fast.
+Respect existing files - always check before overwriting. Use diff to understand
+differences, then decide intelligently or ask. Better to be thoughtful than fast.
 
-Explain choices helpfully. Don't just list files - explain what they do and why someone might want them.
-</execution-philosophy>
+Explain choices helpfully. Don't just list files - explain what they do and why someone
+might want them. </execution-philosophy>

.claude/commands/autotask.md

@@ -38,36 +38,48 @@ Create isolated development environment using /setup-environment. The command au
 <autonomous-execution>
 Implement the solution following project patterns and standards. Available agents:
 
-- Dixon (.claude/agents/dev-agents/debugger.md): Root cause analysis, reproduces issues, identifies underlying problems
-- Ada (.claude/agents/dev-agents/autonomous-developer.md): Implementation work, writes tests
-- Phil (.claude/agents/dev-agents/ux-designer.md): Reviews user-facing text, validates accessibility, ensures UX consistency
-- Rivera (.claude/agents/code-review/code-reviewer.md): Architecture review, validates design patterns, checks security
-- Petra (.claude/agents/dev-agents/prompt-engineer.md): Prompt optimization and refinement
+- Dixon (.claude/agents/dev-agents/debugger.md): Root cause analysis, reproduces issues,
+  identifies underlying problems
+- Ada (.claude/agents/dev-agents/autonomous-developer.md): Implementation work, writes
+  tests
+- Phil (.claude/agents/dev-agents/ux-designer.md): Reviews user-facing text, validates
+  accessibility, ensures UX consistency
+- Rivera (.claude/agents/code-review/code-reviewer.md): Architecture review, validates
+  design patterns, checks security
+- Petra (.claude/agents/dev-agents/prompt-engineer.md): Prompt optimization and
+  refinement
 - Explore (general-purpose): Investigation, research, evaluates trade-offs
 
-Build an execution plan based on task type. Use /load-cursor-rules to load relevant project standards. Execute agents in parallel when possible, sequentially when they depend on each other.
+Build an execution plan based on task type. Use /load-cursor-rules to load relevant
+project standards. Execute agents in parallel when possible, sequentially when they
+depend on each other.
 
-Provide targeted context when launching agents: task requirements, implementation decisions, relevant standards, and specific focus area. Tailor context to agent type.
+Provide targeted context when launching agents: task requirements, implementation
+decisions, relevant standards, and specific focus area. Tailor context to agent type.
 
-Maintain context throughout the workflow. Decisions and clarifications from earlier phases inform later ones.
-</autonomous-execution>
+Maintain context throughout the workflow. Decisions and clarifications from earlier
+phases inform later ones. </autonomous-execution>
 
 <obstacle-and-decision-handling>
 Pause only for deal-killers: security risks, data loss potential, or fundamentally unclear requirements. For everything else, make a reasonable choice and document it.
 
-Document design decisions in the PR with rationale and alternatives considered. The executing model knows when to ask vs when to decide and document.
+Document design decisions in the PR with rationale and alternatives considered. The
+executing model knows when to ask vs when to decide and document.
 </obstacle-and-decision-handling>
 
 <validation-and-review>
 Adapt validation intensity to task risk:
 
-Default (trust git hooks): Make changes, commit, let hooks validate, fix only if hooks fail.
+Default (trust git hooks): Make changes, commit, let hooks validate, fix only if hooks
+fail.
 
-Targeted validation: Run specific tests for changed code, use Rivera for architecture review if patterns change.
+Targeted validation: Run specific tests for changed code, use Rivera for architecture
+review if patterns change.
 
 Full validation: Comprehensive test suite, multiple agent reviews, security scanning.
 
-Principle: Validation intensity should match task risk. Git hooks handle formatting, linting, and tests. Add extra validation only when risk justifies it.
+Principle: Validation intensity should match task risk. Git hooks handle formatting,
+linting, and tests. Add extra validation only when risk justifies it.
 </validation-and-review>
 
 <create-pr>
@@ -76,54 +88,62 @@ Deliver a well-documented pull request with commits following .cursor/rules/git-
 PR description must include:
 
 Summary:
+
 - What was implemented and why
 - How it addresses the requirements
 
 Design Decisions (if any were made):
+
 - Each significant decision with rationale
 - Alternatives considered and trade-offs
 - Why each approach was chosen
 
 Obstacles Encountered (if any):
+
 - Challenges faced
 - How they were resolved or worked around
 
 Testing:
+
 - What validation was performed
-- Edge cases considered
-</create-pr>
+- Edge cases considered </create-pr>
 
 <bot-feedback-loop>
 Autonomously address valuable bot feedback, reject what's not applicable, and deliver a PR ready for human review with all critical issues resolved.
 
-After creating the PR, wait for AI code review bots to complete initial analysis. You have context bots lack: project standards, implementation rationale, trade-offs considered, and user requirements. Evaluate feedback against this context.
+After creating the PR, wait for AI code review bots to complete initial analysis. You
+have context bots lack: project standards, implementation rationale, trade-offs
+considered, and user requirements. Evaluate feedback against this context.
 
-Fix what's valuable (security issues, real bugs, good suggestions). Reject what's not (use WONTFIX with brief explanation for context-missing or incorrect feedback). Trust your judgment on what matters.
+Fix what's valuable (security issues, real bugs, good suggestions). Reject what's not
+(use WONTFIX with brief explanation for context-missing or incorrect feedback). Trust
+your judgment on what matters.
 
-Iterate on bot feedback until critical issues are resolved.
-</bot-feedback-loop>
+Iterate on bot feedback until critical issues are resolved. </bot-feedback-loop>
 
 <completion>
 Provide a summary scaled to task complexity:
 
 What was accomplished:
+
 - Core functionality delivered
 - Design decisions made autonomously
 - Obstacles overcome without user intervention
 
 Key highlights:
+
 - Elegant solutions or optimizations
 - Significant issues found and fixed
 - Bot feedback addressed
 
-Include the PR URL and worktree location. If design decisions were made autonomously, note they're documented in the PR for review.
-</completion>
+Include the PR URL and worktree location. If design decisions were made autonomously,
+note they're documented in the PR for review. </completion>
 
 <error-recovery>
 Recover gracefully from failures when possible. Capture decision-enabling context: what was attempted, what state preceded the failure, what the error indicates about root cause, and whether you have enough information to fix it autonomously.
 
-Attempt fixes when you can. For issues you can't resolve autonomously, inform the user with clear options and context.
-</error-recovery>
+Attempt fixes when you can. For issues you can't resolve autonomously, inform the user
+with clear options and context. </error-recovery>
 
 ## Key Principles
 
@@ -145,6 +165,7 @@ Attempt fixes when you can. For issues you can't resolve autonomously, inform th
 ## Configuration
 
 The command adapts to your project structure:
+
 - Detects git hooks (husky, pre-commit)
 - Detects test runners (jest, mocha, vitest, etc.)
 - Finds linting configs (eslint, prettier, etc.)

.claude/commands/create-prompt.md

@@ -28,10 +28,10 @@ Structure the prompt using XML tags for clarity:
 Ensure .created-prompts/ directory exists and is in .gitignore.
 
 Save with descriptive Title-Case-With-Hyphens name:
+
 - Implement-User-Authentication.md
 - Fix-Database-Connection-Bug.md
-- Add-Dashboard-Analytics.md
-</file-management>
+- Add-Dashboard-Analytics.md </file-management>
 
 <execution-offer>
 After saving, offer to execute the prompt immediately using the Task tool (subagent_type: "general-purpose").