Name: update-tech-stack
Author: krzemienski

Prompt file imported from krzemienski/dotai (.claude/commands/docs/update-tech-stack.md). Fill in {{arguments}} before use. Copyright stays with the author.

Update Tech Stack Documentation

User Request: {{arguments}}

Context

Project root: !pwd
Package.json: @package.json
Current tech doc: @.taskmaster/docs/tech-stack.md
Project Structure: !bash .claude/scripts/tree.sh
Last modified: !stat -f "%Sm" .taskmaster/docs/tech-stack.md 2>/dev/null || echo "No existing document"
Recent package changes: !git diff HEAD~10 HEAD -- package.json 2>/dev/null | grep -E "^[+-]" | head -20 || echo "No recent changes"

Goal

Update the existing Tech Stack Documentation to reflect current technical state, dependency changes, new tools adoption, and infrastructure evolution. Maintain technical accuracy while documenting all changes.

Process

1. Document Analysis

Read existing tech-stack.md thoroughly
Note documented versions and configurations
Understand current technical baseline
Identify sections that may need updates

2. Technical Change Detection

Think deeply about technical evolution in the codebase.

Analyze for:

Dependency Changes: New packages, version updates, removals
Framework Evolution: Major version upgrades, breaking changes
Tool Adoption: New dev tools, linters, formatters, testing frameworks
Infrastructure Shifts: Deployment, hosting, monitoring changes
Database Evolution: Schema changes, new ORMs, migrations
Integration Updates: New APIs, services, authentication providers

Extended thinking helps identify cascading dependency updates, understand version compatibility issues, and recognize architectural implications of technical changes.

3. Automated Comparison

# Compare current vs documented dependencies
# Check for version mismatches
# Identify new configuration files
# Detect new tool configurations

4. Interactive Technical Q&A

Ask targeted questions about:

Non-discoverable infrastructure changes
Deployment and hosting updates
New external service integrations
Workflow and process changes

5. Update Documentation

Update incrementally:

Preserve accurate technical information
Update version numbers precisely
Add new sections for major additions
Mark deprecated technologies

6. Save and Verify

Suggest backup for major changes
Update CLAUDE.md commands if needed
Verify all versions are accurate

Technical Questions Template

🔄 Version Updates & Dependencies

1. Which major dependencies have been updated?

Review your recent dependency changes:

a) Framework upgrades (Next.js, React, etc.) with breaking changes
b) Tool updates (TypeScript, ESLint, etc.) requiring config changes
c) New dependencies added for features or development
d) Removed packages that are no longer needed
e) All of the above - Major technical overhaul

2. Have you changed your package manager or Node version?

a) Same setup - No changes to tooling
b) Node upgrade - Updated Node.js version
c) Package manager switch - Changed from npm/yarn/pnpm
d) Monorepo adoption - Moved to workspace setup

🏗️ Infrastructure Evolution

3. Have your deployment or hosting arrangements changed?

Current deployment is documented as: [show from existing doc]

a) Same platform - Just configuration updates
b) Platform migration - Moved to different provider
c) Architecture change - Serverless, containers, etc.
d) Multi-region - Expanded geographic deployment

4. Database or storage changes?

a) Version upgrade - Same DB, newer version
b) Migration - Switched database systems
c) New caching - Added Redis, Memcached, etc.
d) Storage addition - New file storage, CDN
e) No changes - Same setup as before

🛠️ Development Workflow Updates

5. New development tools or practices?

Select all that apply:

New testing framework or strategy
Added code quality tools (linters, formatters)
CI/CD pipeline changes
Docker/containerization adoption
New build tools or bundlers
Performance monitoring tools

6. External service integrations?

Have you added or changed:

a) Payment processing - New or updated provider
b) Authentication - Different auth service
c) Email/SMS - Communication service changes
d) Monitoring - New error tracking or analytics
e) APIs - Additional third-party integrations
f) None - Same external services

🔐 Security & Compliance

7. Security tool adoption?

Update Strategy

Version Precision

// ❌ Outdated
"next": "^13.0.0"

// ✅ Current and precise
"next": "14.2.5"

Configuration Updates

Update all config examples to match current files
Include new configuration options
Remove deprecated settings
Add migration notes for breaking changes

New Technology Sections

When adding major new tools:

### [New Tool Category]

**Tool:** [Name] [Version]
**Purpose:** [Why it was adopted]
**Configuration:** [Key settings]
**Integration:** [How it connects with other tools]

Document Update Areas

Always Check:

package.json changes

# Compare all dependencies
# Note version changes
# Identify new packages

Configuration files
- tsconfig.json updates
- New .config files
- Build tool configurations
- Linting rule changes
Development scripts
- New npm/pnpm scripts
- Changed command purposes
- Removed scripts
Infrastructure files
- Dockerfile changes
- CI/CD workflows
- Deployment configs
- Environment examples

Conditional Updates:

Architecture: Only if fundamental changes
Conventions: Only if standards changed

Execution Steps

1. Start with Analysis

# Check current dependencies vs documented
diff <(jq -r '.dependencies | keys[]' package.json | sort) \
     <(grep -E '^\*\*.*:' .taskmaster/docs/tech-stack.md | cut -d: -f1 | sed 's/\*//g' | sort)

# Review recent dependency commits
git log --oneline --grep="dep" --since="30 days ago"

# Check for new config files
find . -name "*.config.*" -newer .taskmaster/docs/tech-stack.md 2>/dev/null

Think deeply about: "What technical decisions drove these changes? How do version updates affect the overall architecture? What new capabilities do these tools enable?"

2. Interactive Q&A

Present technical questions clearly
Include current state from documentation
Wait for detailed responses

3. Update Documentation

Follow incremental approach:

<!-- Version update example -->

**Before:** React 18.2.0
**After:** React 18.3.1 - Includes new compiler optimizations

<!-- New tool example -->

### Code Quality Tools

**New Addition:**

- **Biome:** 1.8.3 - Replaced ESLint and Prettier
  - Faster performance (10x)
  - Single configuration file
  - Built-in formatting

4. Commands Update

Update CLAUDE.md if new scripts discovered:

### Development

- `pnpm dev` - Start development server
- `pnpm check` - NEW: Run Biome linting and formatting
- `pnpm test:e2e` - NEW: Run Playwright tests

5. Save and Backup

# Optional backup
cp .taskmaster/docs/tech-stack.md .taskmaster/docs/tech-stack.backup.md

# Save updated document
# Overwrite .taskmaster/docs/tech-stack.md

Key Principles

DO:

Exact Versions: Use precise version numbers from lock files
Config Accuracy: Match actual configuration files
Change Rationale: Explain why tools were adopted/changed
Migration Notes: Document breaking changes and updates
Performance Impact: Note improvements or concerns

DON'T:

Generic Updates: Avoid vague version ranges
Assumption: Verify every technical detail
Old Information: Remove outdated configurations
Wishful Documentation: Only document what exists
Sensitive Data: Never include secrets or keys

Output

Format: Markdown (.md)
Location: .taskmaster/docs/
Filename: tech-stack.md (overwrites)
Backup: Suggest for major changes

Final Checklist

✅ Read existing tech-stack.md completely
✅ Analyze all dependency changes
✅ Check configuration file updates
✅ Review infrastructure changes
✅ Ask targeted technical questions
✅ Update with exact versions
✅ Include configuration examples
✅ Update CLAUDE.md commands
✅ Suggest backup if major changes
✅ Verify technical accuracy

# Update Tech Stack Documentation **User Request:** {{arguments}} ## Context - Project root: !`pwd` - Package.json: @package.json - Current tech doc: @.taskmaster/docs/tech-stack.md - **Project Structure:** !`bash .claude/scripts/tree.sh` - Last modified: !`stat -f "%Sm" .taskmaster/docs/tech-stack.md 2>/dev/null || echo "No existing document"` - Recent package changes: !`git diff HEAD~10 HEAD -- package.json 2>/dev/null | grep -E "^[+-]" | head -20 || echo "No recent changes"` ## Goal Update the existing Tech Stack Documentation to reflect current technical state, dependency changes, new tools adoption, and infrastructure evolution. Maintain technical accuracy while documenting all changes. ## Process ### 1. Document Analysis - Read existing tech-stack.md thoroughly - Note documented versions and configurations - Understand current technical baseline - Identify sections that may need updates ### 2. Technical Change Detection **Think deeply about technical evolution in the codebase.** Analyze for: - **Dependency Changes:** New packages, version updates, removals - **Framework Evolution:** Major version upgrades, breaking changes - **Tool Adoption:** New dev tools, linters, formatters, testing frameworks - **Infrastructure Shifts:** Deployment, hosting, monitoring changes - **Database Evolution:** Schema changes, new ORMs, migrations - **Integration Updates:** New APIs, services, authentication providers _Extended thinking helps identify cascading dependency updates, understand version compatibility issues, and recognize architectural implications of technical changes._ ### 3. Automated Comparison ```bash # Compare current vs documented dependencies # Check for version mismatches # Identify new configuration files # Detect new tool configurations ``` ### 4. Interactive Technical Q&A Ask targeted questions about: - Non-discoverable infrastructure changes - Deployment and hosting updates - New external service integrations - Workflow and process changes ### 5. Update Documentation Update incrementally: - Preserve accurate technical information - Update version numbers precisely - Add new sections for major additions - Mark deprecated technologies ### 6. Save and Verify - Suggest backup for major changes - Update CLAUDE.md commands if needed - Verify all versions are accurate ## Technical Questions Template ### 🔄 Version Updates & Dependencies **1. Which major dependencies have been updated?** Review your recent dependency changes: a) **Framework upgrades** (Next.js, React, etc.) with breaking changes b) **Tool updates** (TypeScript, ESLint, etc.) requiring config changes c) **New dependencies** added for features or development d) **Removed packages** that are no longer needed e) **All of the above** - Major technical overhaul **2. Have you changed your package manager or Node version?** a) **Same setup** - No changes to tooling b) **Node upgrade** - Updated Node.js version c) **Package manager switch** - Changed from npm/yarn/pnpm d) **Monorepo adoption** - Moved to workspace setup ### 🏗️ Infrastructure Evolution **3. Have your deployment or hosting arrangements changed?** Current deployment is documented as: [show from existing doc] a) **Same platform** - Just configuration updates b) **Platform migration** - Moved to different provider c) **Architecture change** - Serverless, containers, etc. d) **Multi-region** - Expanded geographic deployment **4. Database or storage changes?** a) **Version upgrade** - Same DB, newer version b) **Migration** - Switched database systems c) **New caching** - Added Redis, Memcached, etc. d) **Storage addition** - New file storage, CDN e) **No changes** - Same setup as before ### 🛠️ Development Workflow Updates **5. New development tools or practices?** Select all that apply: - [ ] New testing framework or strategy - [ ] Added code quality tools (linters, formatters) - [ ] CI/CD pipeline changes - [ ] Docker/containerization adoption - [ ] New build tools or bundlers - [ ] Performance monitoring tools **6. External service integrations?** Have you added or changed: a) **Payment processing** - New or updated provider b) **Authentication** - Different auth service c) **Email/SMS** - Communication service changes d) **Monitoring** - New error tracking or analytics e) **APIs** - Additional third-party integrations f) **None** - Same external services ### 🔐 Security & Compliance **7. Security tool adoption?** - [ ] Vulnerability scanning (Snyk, etc.) - [ ] Secret management changes - [ ] New authentication methods - [ ] Compliance tools (GDPR, etc.) - [ ] Security headers/policies - [ ] None of the above ## Update Strategy ### Version Precision ```typescript // ❌ Outdated "next": "^13.0.0" // ✅ Current and precise "next": "14.2.5" ``` ### Configuration Updates - Update all config examples to match current files - Include new configuration options - Remove deprecated settings - Add migration notes for breaking changes ### New Technology Sections When adding major new tools: ```markdown ### [New Tool Category] **Tool:** [Name] [Version] **Purpose:** [Why it was adopted] **Configuration:** [Key settings] **Integration:** [How it connects with other tools] ``` ## Document Update Areas ### Always Check: 1. **package.json changes** ```bash # Compare all dependencies # Note version changes # Identify new packages ``` 2. **Configuration files** - tsconfig.json updates - New .config files - Build tool configurations - Linting rule changes 3. **Development scripts** - New npm/pnpm scripts - Changed command purposes - Removed scripts 4. **Infrastructure files** - Dockerfile changes - CI/CD workflows - Deployment configs - Environment examples ### Conditional Updates: - **Architecture:** Only if fundamental changes - **Conventions:** Only if standards changed ## Execution Steps ### 1. Start with Analysis ```bash # Check current dependencies vs documented diff <(jq -r '.dependencies | keys[]' package.json | sort) \ <(grep -E '^\*\*.*:' .taskmaster/docs/tech-stack.md | cut -d: -f1 | sed 's/\*//g' | sort) # Review recent dependency commits git log --oneline --grep="dep" --since="30 days ago" # Check for new config files find . -name "*.config.*" -newer .taskmaster/docs/tech-stack.md 2>/dev/null ``` **Think deeply about:** "What technical decisions drove these changes? How do version updates affect the overall architecture? What new capabilities do these tools enable?" ### 2. Interactive Q&A - Present technical questions clearly - Include current state from documentation - Wait for detailed responses ### 3. Update Documentation Follow incremental approach: ```markdown  **Before:** React 18.2.0 **After:** React 18.3.1 - Includes new compiler optimizations  ### Code Quality Tools **New Addition:** - **Biome:** 1.8.3 - Replaced ESLint and Prettier - Faster performance (10x) - Single configuration file - Built-in formatting ``` ### 4. Commands Update Update CLAUDE.md if new scripts discovered: ```markdown ### Development - `pnpm dev` - Start development server - `pnpm check` - NEW: Run Biome linting and formatting - `pnpm test:e2e` - NEW: Run Playwright tests ``` ### 5. Save and Backup ```bash # Optional backup cp .taskmaster/docs/tech-stack.md .taskmaster/docs/tech-stack.backup.md # Save updated document # Overwrite .taskmaster/docs/tech-stack.md ``` ## Key Principles ### DO: - **Exact Versions:** Use precise version numbers from lock files - **Config Accuracy:** Match actual configuration files - **Change Rationale:** Explain why tools were adopted/changed - **Migration Notes:** Document breaking changes and updates - **Performance Impact:** Note improvements or concerns ### DON'T: - **Generic Updates:** Avoid vague version ranges - **Assumption:** Verify every technical detail - **Old Information:** Remove outdated configurations - **Wishful Documentation:** Only document what exists - **Sensitive Data:** Never include secrets or keys ## Output - **Format:** Markdown (`.md`) - **Location:** `.taskmaster/docs/` - **Filename:** `tech-stack.md` (overwrites) - **Backup:** Suggest for major changes ## Final Checklist 1. ✅ Read existing tech-stack.md completely 2. ✅ Analyze all dependency changes 3. ✅ Check configuration file updates 4. ✅ Review infrastructure changes 5. ✅ Ask targeted technical questions 6. ✅ Update with exact versions 7. ✅ Include configuration examples 8. ✅ Update CLAUDE.md commands 9. ✅ Suggest backup if major changes 10. ✅ Verify technical accuracy

{ "prompt": "# Update Tech Stack Documentation\n\n**User Request:** {{arguments}}\n\n## Context\n\n- Project root: !`pwd`\n- Package.json: @package.json\n- Current tech doc: @.taskmaster/docs/tech-stack.md\n- **Project Structure:** !`bash .claude/scripts/tree.sh`\n- Last modified: !`stat -f \"%Sm\" .taskmaster/docs/tech-stack.md 2>/dev/null || echo \"No existing document\"`\n- Recent package changes: !`git diff HEAD~10 HEAD -- package.json 2>/dev/null | grep -E \"^[+-]\" | head -20 || echo \"No recent changes\"`\n\n## Goal\n\nUpdate the existing Tech Stack Documentation to reflect current technical state, dependency changes, new tools adoption, and infrastructure evolution. Maintain technical accuracy while documenting all changes.\n\n## Process\n\n### 1. Document Analysis\n\n- Read existing tech-stack.md thoroughly\n- Note documented versions and configurations\n- Understand current technical baseline\n- Identify sections that may need updates\n\n### 2. Technical Change Detection\n\n**Think deeply about technical evolution in the codebase.**\n\nAnalyze for:\n\n- **Dependency Changes:** New packages, version updates, removals\n- **Framework Evolution:** Major version upgrades, breaking changes\n- **Tool Adoption:** New dev tools, linters, formatters, testing frameworks\n- **Infrastructure Shifts:** Deployment, hosting, monitoring changes\n- **Database Evolution:** Schema changes, new ORMs, migrations\n- **Integration Updates:** New APIs, services, authentication providers\n\n_Extended thinking helps identify cascading dependency updates, understand version compatibility issues, and recognize architectural implications of technical changes._\n\n### 3. Automated Comparison\n\n```bash\n# Compare current vs documented dependencies\n# Check for version mismatches\n# Identify new configuration files\n# Detect new tool configurations\n```\n\n### 4. Interactive Technical Q&A\n\nAsk targeted questions about:\n\n- Non-discoverable infrastructure changes\n- Deployment and hosting updates\n- New external service integrations\n- Workflow and process changes\n\n### 5. Update Documentation\n\nUpdate incrementally:\n\n- Preserve accurate technical information\n- Update version numbers precisely\n- Add new sections for major additions\n- Mark deprecated technologies\n\n### 6. Save and Verify\n\n- Suggest backup for major changes\n- Update CLAUDE.md commands if needed\n- Verify all versions are accurate\n\n## Technical Questions Template\n\n### 🔄 Version Updates & Dependencies\n\n**1. Which major dependencies have been updated?**\n\nReview your recent dependency changes:\n\na) **Framework upgrades** (Next.js, React, etc.) with breaking changes \nb) **Tool updates** (TypeScript, ESLint, etc.) requiring config changes \nc) **New dependencies** added for features or development \nd) **Removed packages** that are no longer needed \ne) **All of the above** - Major technical overhaul\n\n**2. Have you changed your package manager or Node version?**\n\na) **Same setup** - No changes to tooling \nb) **Node upgrade** - Updated Node.js version \nc) **Package manager switch** - Changed from npm/yarn/pnpm \nd) **Monorepo adoption** - Moved to workspace setup\n\n### 🏗️ Infrastructure Evolution\n\n**3. Have your deployment or hosting arrangements changed?**\n\nCurrent deployment is documented as: [show from existing doc]\n\na) **Same platform** - Just configuration updates \nb) **Platform migration** - Moved to different provider \nc) **Architecture change** - Serverless, containers, etc. \nd) **Multi-region** - Expanded geographic deployment\n\n**4. Database or storage changes?**\n\na) **Version upgrade** - Same DB, newer version \nb) **Migration** - Switched database systems \nc) **New caching** - Added Redis, Memcached, etc. \nd) **Storage addition** - New file storage, CDN \ne) **No changes** - Same setup as before\n\n### 🛠️ Development Workflow Updates\n\n**5. New development tools or practices?**\n\nSelect all that apply:\n\n- [ ] New testing framework or strategy\n- [ ] Added code quality tools (linters, formatters)\n- [ ] CI/CD pipeline changes\n- [ ] Docker/containerization adoption\n- [ ] New build tools or bundlers\n- [ ] Performance monitoring tools\n\n**6. External service integrations?**\n\nHave you added or changed:\n\na) **Payment processing** - New or updated provider \nb) **Authentication** - Different auth service \nc) **Email/SMS** - Communication service changes \nd) **Monitoring** - New error tracking or analytics \ne) **APIs** - Additional third-party integrations \nf) **None** - Same external services\n\n### 🔐 Security & Compliance\n\n**7. Security tool adoption?**\n\n- [ ] Vulnerability scanning (Snyk, etc.)\n- [ ] Secret management changes\n- [ ] New authentication methods\n- [ ] Compliance tools (GDPR, etc.)\n- [ ] Security headers/policies\n- [ ] None of the above\n\n## Update Strategy\n\n### Version Precision\n\n```typescript\n// ❌ Outdated\n\"next\": \"^13.0.0\"\n\n// ✅ Current and precise\n\"next\": \"14.2.5\"\n```\n\n### Configuration Updates\n\n- Update all config examples to match current files\n- Include new configuration options\n- Remove deprecated settings\n- Add migration notes for breaking changes\n\n### New Technology Sections\n\nWhen adding major new tools:\n\n```markdown\n### [New Tool Category]\n\n**Tool:** [Name] [Version]\n**Purpose:** [Why it was adopted]\n**Configuration:** [Key settings]\n**Integration:** [How it connects with other tools]\n```\n\n## Document Update Areas\n\n### Always Check:\n\n1. **package.json changes**\n\n ```bash\n # Compare all dependencies\n # Note version changes\n # Identify new packages\n ```\n\n2. **Configuration files**\n\n - tsconfig.json updates\n - New .config files\n - Build tool configurations\n - Linting rule changes\n\n3. **Development scripts**\n\n - New npm/pnpm scripts\n - Changed command purposes\n - Removed scripts\n\n4. **Infrastructure files**\n - Dockerfile changes\n - CI/CD workflows\n - Deployment configs\n - Environment examples\n\n### Conditional Updates:\n\n- **Architecture:** Only if fundamental changes\n- **Conventions:** Only if standards changed\n\n## Execution Steps\n\n### 1. Start with Analysis\n\n```bash\n# Check current dependencies vs documented\ndiff <(jq -r '.dependencies | keys[]' package.json | sort) \\\n <(grep -E '^\\*\\*.*:' .taskmaster/docs/tech-stack.md | cut -d: -f1 | sed 's/\\*//g' | sort)\n\n# Review recent dependency commits\ngit log --oneline --grep=\"dep\" --since=\"30 days ago\"\n\n# Check for new config files\nfind . -name \"*.config.*\" -newer .taskmaster/docs/tech-stack.md 2>/dev/null\n```\n\n**Think deeply about:** \"What technical decisions drove these changes? How do version updates affect the overall architecture? What new capabilities do these tools enable?\"\n\n### 2. Interactive Q&A\n\n- Present technical questions clearly\n- Include current state from documentation\n- Wait for detailed responses\n\n### 3. Update Documentation\n\nFollow incremental approach:\n\n```markdown\n\n\n**Before:** React 18.2.0\n**After:** React 18.3.1 - Includes new compiler optimizations\n\n\n\n### Code Quality Tools\n\n**New Addition:**\n\n- **Biome:** 1.8.3 - Replaced ESLint and Prettier\n - Faster performance (10x)\n - Single configuration file\n - Built-in formatting\n```\n\n### 4. Commands Update\n\nUpdate CLAUDE.md if new scripts discovered:\n\n```markdown\n### Development\n\n- `pnpm dev` - Start development server\n- `pnpm check` - NEW: Run Biome linting and formatting\n- `pnpm test:e2e` - NEW: Run Playwright tests\n```\n\n### 5. Save and Backup\n\n```bash\n# Optional backup\ncp .taskmaster/docs/tech-stack.md .taskmaster/docs/tech-stack.backup.md\n\n# Save updated document\n# Overwrite .taskmaster/docs/tech-stack.md\n```\n\n## Key Principles\n\n### DO:\n\n- **Exact Versions:** Use precise version numbers from lock files\n- **Config Accuracy:** Match actual configuration files\n- **Change Rationale:** Explain why tools were adopted/changed\n- **Migration Notes:** Document breaking changes and updates\n- **Performance Impact:** Note improvements or concerns\n\n### DON'T:\n\n- **Generic Updates:** Avoid vague version ranges\n- **Assumption:** Verify every technical detail\n- **Old Information:** Remove outdated configurations\n- **Wishful Documentation:** Only document what exists\n- **Sensitive Data:** Never include secrets or keys\n\n## Output\n\n- **Format:** Markdown (`.md`)\n- **Location:** `.taskmaster/docs/`\n- **Filename:** `tech-stack.md` (overwrites)\n- **Backup:** Suggest for major changes\n\n## Final Checklist\n\n1. ✅ Read existing tech-stack.md completely\n2. ✅ Analyze all dependency changes\n3. ✅ Check configuration file updates\n4. ✅ Review infrastructure changes\n5. ✅ Ask targeted technical questions\n6. ✅ Update with exact versions\n7. ✅ Include configuration examples\n8. ✅ Update CLAUDE.md commands\n9. ✅ Suggest backup if major changes\n10. ✅ Verify technical accuracy", "variables": [ "arguments" ], "notes": "Update tech stack documentation based on dependency changes and technical evolution Tools: Read, Glob, Grep, Write, MultiEdit, TodoWrite, Bash.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/krzemienski/dotai", "path": ".claude/commands/docs/update-tech-stack.md", "ref": "b8635d6c12b6d57603a79fcf4fc31546adab4f08", "url": "https://github.com/krzemienski/dotai/blob/b8635d6c12b6d57603a79fcf4fc31546adab4f08/.claude/commands/docs/update-tech-stack.md", "key": "krzemienski/dotai/.claude/commands/docs/update-tech-stack.md" } } }

update-tech-stack

About