Back to Details

developer-growth-analysis

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Developer Growth Analysis

开发者成长分析

This skill provides personalized feedback on your recent coding work by analyzing your Claude Code chat interactions and identifying patterns that reveal strengths and areas for growth.
本技能通过分析你的Claude Code聊天交互，识别能体现优势和成长空间的模式，为你近期的编码工作提供个性化反馈。

When to Use This Skill

何时使用本技能

Use this skill when you want to:
  • Understand your development patterns and habits from recent work
  • Identify specific technical gaps or recurring challenges
  • Discover which topics would benefit from deeper study
  • Track improvement areas across your recent projects
  • Get actionable recommendations for professional growth
This skill is ideal for developers who want structured feedback on their growth without waiting for code reviews, and who prefer data-driven insights from their own work history.
当你有以下需求时可以使用本技能：
  • 了解你近期工作体现的开发模式和习惯
  • 明确具体的技术短板或反复遇到的挑战
  • 发现值得深入学习的主题
  • 跟踪你近期多个项目中的可改进领域
  • 获取可落地的职业成长建议
本技能非常适合这类开发者：不想等待代码评审就想获得结构化的成长反馈，更偏好从自身工作历史中获得数据驱动的洞见。

What This Skill Does

本技能的功能

This skill performs a four-step analysis of your development work:
  1. Reads Your Chat History: Accesses your local Claude Code chat history from the past 24-48 hours to understand what you've been working on.
  2. Identifies Development Patterns: Analyzes the types of problems you're solving, technologies you're using, challenges you encounter, and how you approach different kinds of tasks.
  3. Detects Improvement Areas: Recognizes patterns that suggest skill gaps, repeated struggles, inefficient approaches, or areas where you might benefit from deeper knowledge.
  4. Generates a Personalized Report: Creates a comprehensive report showing your work summary, identified improvement areas, specific recommendations for growth, and prioritized action items.
本技能会对你的开发工作执行四步分析：
  1. 读取你的聊天历史：访问你本地过去24-48小时的Claude Code聊天历史，了解你近期的工作内容。
  2. 识别开发模式：分析你解决的问题类型、使用的技术、遇到的挑战，以及你处理不同任务的方式。
  3. 检测可改进领域：识别能体现技能短板、反复遇到的困难、低效的解决方式，或是你可以通过加深知识储备获益的领域的相关模式。
  4. 生成个性化报告：创建一份完整的报告，包含你的工作摘要、识别出的可改进领域、具体的成长建议，以及优先级排序的行动项。

How to Use

使用方法

Ask Claude to analyze your recent coding work:
Analyze my developer growth from my recent chats
Or be more specific about which time period:
Analyze my work from today and suggest areas for improvement
The skill will generate a formatted report with:
  • Overview of your recent work
  • Key improvement areas identified
  • Specific recommendations for each area
  • Prioritized action items to focus on
  • Suggested keywords for finding learning resources
让Claude分析你近期的编码工作即可：
Analyze my developer growth from my recent chats
也可以指定具体的时间范围：
Analyze my work from today and suggest areas for improvement
本技能会生成一份格式化的报告，包含：
  • 你近期工作的概览
  • 识别出的核心可改进领域
  • 每个领域的具体建议
  • 需要重点关注的优先级行动项
  • 用于查找学习资源的建议关键词

Instructions

使用说明

When a user requests analysis of their developer growth or coding patterns from recent work:
  1. Access Chat History
    Read the chat history from 
    ~/.claude/history.jsonl
    . This file is a JSONL format where each line contains:
    • display
      : The user's message/request
    • project
      : The project being worked on
    • timestamp
      : Unix timestamp (in milliseconds)
    • pastedContents
      : Any code or content pasted
    Filter for entries from the past 24-48 hours based on the current timestamp.
  2. Analyze Work Patterns
    Extract and analyze the following from the filtered chats:
    • Projects and Domains: What types of projects was the user working on? (e.g., backend, frontend, DevOps, data, etc.)
    • Technologies Used: What languages, frameworks, and tools appear in the conversations?
    • Problem Types: What categories of problems are being solved? (e.g., performance optimization, debugging, feature implementation, refactoring, setup/configuration)
    • Challenges Encountered: What problems did the user struggle with? Look for:
      • Repeated questions about similar topics
      • Problems that took multiple attempts to solve
      • Questions indicating knowledge gaps
      • Complex architectural decisions
    • Approach Patterns: How does the user solve problems? (e.g., methodical, exploratory, experimental)
  3. Identify Improvement Areas
    Based on the analysis, identify 3-5 specific areas where the user could improve. These should be:
    • Specific (not vague like "improve coding skills")
    • Evidence-based (grounded in actual chat history)
    • Actionable (practical improvements that can be made)
    • Prioritized (most impactful first)
    Examples of good improvement areas:
    • "Advanced TypeScript patterns (generics, utility types, type guards) - you struggled with type safety in [specific project]"
    • "Error handling and validation - I noticed you patched several bugs related to missing null checks"
    • "Async/await patterns - your recent work shows some race conditions and timing issues"
    • "Database query optimization - you rewrote the same query multiple times"
  4. Generate Report
    Create a comprehensive report with this structure:
    markdown
    # Your Developer Growth Report

**Report Period**: [Yesterday / Today / [Custom Date Range]]
**Last Updated**: [Current Date and Time]

## Work Summary

[2-3 paragraphs summarizing what the user worked on, projects touched, technologies used, and overall focus areas]

Example:
"Over the past 24 hours, you focused primarily on backend development with three distinct projects. Your work involved TypeScript, React, and deployment infrastructure. You tackled a mix of feature implementation, debugging, and architectural decisions, with a particular focus on API design and database optimization."

## Improvement Areas (Prioritized)

### 1. [Area Name]

**Why This Matters**: [Explanation of why this skill is important for the user's work]

**What I Observed**: [Specific evidence from chat history showing this gap]

**Recommendation**: [Concrete step(s) to improve in this area]

**Time to Skill Up**: [Brief estimate of effort required]

**Search Keywords**: [Suggested search terms for finding learning resources]

---

[Repeat for 2-4 additional areas]

## Strengths Observed

[2-3 bullet points highlighting things you're doing well - things to continue doing]

## Action Items

Priority order:
1. [Action item derived from highest priority improvement area]
2. [Action item from next area]
3. [Action item from next area]

## Recommended Learning Focus

Based on your improvement areas, here are search keywords you can use to find relevant resources:
- [Improvement Area 1]: "[search terms]"
- [Improvement Area 2]: "[search terms]"
- [Improvement Area 3]: "[search terms]"

These terms can be used in HackerNews, dev.to, Medium, or your preferred learning platforms.
  5. Present the Complete Report
    Deliver the report in a clean, readable format that the user can:
    • Quickly scan for key takeaways
    • Use for focused learning planning
    • Reference over the next week as they work on improvements
    • Share with mentors if they want external feedback
    • Use the search keywords to find their own learning resources
当用户请求分析其开发者成长情况或近期工作的编码模式时：
  1. 访问聊天历史
    读取
    ~/.claude/history.jsonl
    中的聊天历史。该文件为JSONL格式，每一行包含以下字段：
    • display
      ：用户的消息/请求
    • project
      ：正在处理的项目
    • timestamp
      ：Unix时间戳（单位为毫秒）
    • pastedContents
      ：用户粘贴的任意代码或内容
    根据当前时间戳筛选出过去24-48小时的记录。
  2. 分析工作模式
    从筛选后的聊天记录中提取并分析以下内容：
    • 项目和领域：用户正在处理的项目类型？（例如：后端、前端、DevOps、数据等）
    • 使用的技术：对话中出现了哪些语言、框架和工具？
    • 问题类型：用户解决的问题属于哪些类别？（例如：性能优化、调试、功能实现、重构、搭建/配置）
    • 遇到的挑战：用户在哪些问题上遇到了困难？查找以下特征：
      • 围绕相似主题的重复提问
      • 需要多次尝试才能解决的问题
      • 体现知识短板的提问
      • 复杂的架构决策
    • 处理模式：用户如何解决问题？（例如：有条理的、探索性的、实验性的）
  3. 识别可改进领域
    基于分析结果，识别3-5个用户可以提升的具体领域。这些领域需要满足：
    • 具体（不要像「提升编码技能」这样模糊）
    • 有证据支撑（基于真实的聊天历史）
    • 可落地（可以实现的实际提升）
    • 优先级排序（影响最大的排在最前面）
    优秀的可改进领域示例：
    • 「高级TypeScript模式（泛型、工具类型、类型守卫）—— 你在[具体项目]中遇到了类型安全相关的困难」
    • 「错误处理和校验 —— 我注意到你修复了多个和缺失空值检查相关的bug」
    • 「Async/await模式 —— 你近期的工作中出现了一些竞态条件和时序问题」
    • 「数据库查询优化 —— 你多次重写了同一个查询」
  4. 生成报告
    按照以下结构创建完整的报告：
    markdown
    # Your Developer Growth Report

**Report Period**: [Yesterday / Today / [Custom Date Range]]
**Last Updated**: [Current Date and Time]

## Work Summary

[2-3 paragraphs summarizing what the user worked on, projects touched, technologies used, and overall focus areas]

Example:
"Over the past 24 hours, you focused primarily on backend development with three distinct projects. Your work involved TypeScript, React, and deployment infrastructure. You tackled a mix of feature implementation, debugging, and architectural decisions, with a particular focus on API design and database optimization."

## Improvement Areas (Prioritized)

### 1. [Area Name]

**Why This Matters**: [Explanation of why this skill is important for the user's work]

**What I Observed**: [Specific evidence from chat history showing this gap]

**Recommendation**: [Concrete step(s) to improve in this area]

**Time to Skill Up**: [Brief estimate of effort required]

**Search Keywords**: [Suggested search terms for finding learning resources]

---

[Repeat for 2-4 additional areas]

## Strengths Observed

[2-3 bullet points highlighting things you're doing well - things to continue doing]

## Action Items

Priority order:
1. [Action item derived from highest priority improvement area]
2. [Action item from next area]
3. [Action item from next area]

## Recommended Learning Focus

Based on your improvement areas, here are search keywords you can use to find relevant resources:
- [Improvement Area 1]: "[search terms]"
- [Improvement Area 2]: "[search terms]"
- [Improvement Area 3]: "[search terms]"

These terms can be used in HackerNews, dev.to, Medium, or your preferred learning platforms.
  5. 展示完整报告
    以整洁、易读的格式交付报告，用户可以：
    • 快速浏览获取核心要点
    • 用于制定针对性的学习计划
    • 在接下来一周处理改进事项时参考
    • 如果需要外部反馈可以分享给导师
    • 使用搜索关键词查找适合自己的学习资源

Example Usage

使用示例

Input

输入

Analyze my developer growth from my recent chats
Analyze my developer growth from my recent chats

Output

输出

markdown
undefined
markdown
undefined

Your Developer Growth Report

Your Developer Growth Report

Report Period: November 9-10, 2024 Last Updated: November 10, 2024, 9:15 PM UTC
Report Period: November 9-10, 2024 Last Updated: November 10, 2024, 9:15 PM UTC

Work Summary

Work Summary

Over the past two days, you focused on backend infrastructure and API development. Your primary project was an open-source showcase application, where you made significant progress on connections management, UI improvements, and deployment configuration. You worked with TypeScript, React, and Node.js, tackling challenges ranging from data security to responsive design. Your work shows a balance between implementing features and addressing technical debt.
Over the past two days, you focused on backend infrastructure and API development. Your primary project was an open-source showcase application, where you made significant progress on connections management, UI improvements, and deployment configuration. You worked with TypeScript, React, and Node.js, tackling challenges ranging from data security to responsive design. Your work shows a balance between implementing features and addressing technical debt.

Improvement Areas (Prioritized)

Improvement Areas (Prioritized)

1. Advanced TypeScript Patterns and Type Safety

1. Advanced TypeScript Patterns and Type Safety

Why This Matters: TypeScript is central to your work, but leveraging its advanced features (generics, utility types, conditional types, type guards) can significantly improve code reliability and reduce runtime errors. Better type safety catches bugs at compile time rather than in production.
What I Observed: In your recent chats, you were working with connection data structures and struggled a few times with typing auth configurations properly. You also had to iterate on union types for different connection states. There's an opportunity to use discriminated unions and type guards more effectively.
Recommendation: Study TypeScript's advanced type system, particularly utility types (Omit, Pick, Record), conditional types, and discriminated unions. Apply these patterns to your connection configuration handling and auth state management.
Time to Skill Up: 5-8 hours of focused learning and practice
Search Keywords: "TypeScript discriminated unions", "TypeScript utility types advanced", "type guards TypeScript best practices"
Why This Matters: TypeScript is central to your work, but leveraging its advanced features (generics, utility types, conditional types, type guards) can significantly improve code reliability and reduce runtime errors. Better type safety catches bugs at compile time rather than in production.
What I Observed: In your recent chats, you were working with connection data structures and struggled a few times with typing auth configurations properly. You also had to iterate on union types for different connection states. There's an opportunity to use discriminated unions and type guards more effectively.
Recommendation: Study TypeScript's advanced type system, particularly utility types (Omit, Pick, Record), conditional types, and discriminated unions. Apply these patterns to your connection configuration handling and auth state management.
Time to Skill Up: 5-8 hours of focused learning and practice
Search Keywords: "TypeScript discriminated unions", "TypeScript utility types advanced", "type guards TypeScript best practices"

2. Secure Data Handling and Information Hiding in UI

2. Secure Data Handling and Information Hiding in UI

Why This Matters: You identified and fixed a security concern where sensitive connection data was being displayed in your console. Preventing information leakage is critical for applications handling user credentials and API keys. Good practices here prevent security incidents and user trust violations.
What I Observed: You caught that your "Your Apps" page was showing full connection data including auth configs. This shows good security instincts, and the next step is building this into your default thinking when handling sensitive information.
Recommendation: Review security best practices for handling sensitive data in frontend applications. Create reusable patterns for filtering/masking sensitive information before displaying it. Consider implementing a secure data layer that explicitly whitelist what can be shown in the UI.
Time to Skill Up: 3-4 hours
Search Keywords: "frontend security sensitive data handling", "preventing information leakage web apps", "secure credential management frontend"
Why This Matters: You identified and fixed a security concern where sensitive connection data was being displayed in your console. Preventing information leakage is critical for applications handling user credentials and API keys. Good practices here prevent security incidents and user trust violations.
What I Observed: You caught that your "Your Apps" page was showing full connection data including auth configs. This shows good security instincts, and the next step is building this into your default thinking when handling sensitive information.
Recommendation: Review security best practices for handling sensitive data in frontend applications. Create reusable patterns for filtering/masking sensitive information before displaying it. Consider implementing a secure data layer that explicitly whitelist what can be shown in the UI.
Time to Skill Up: 3-4 hours
Search Keywords: "frontend security sensitive data handling", "preventing information leakage web apps", "secure credential management frontend"

3. Component Architecture and Responsive UI Patterns

3. Component Architecture and Responsive UI Patterns

Why This Matters: You're designing UIs that need to work across different screen sizes and user interactions. Strong component architecture makes it easier to build complex UIs without bugs and improves maintainability.
What I Observed: You worked on the "Marketplace" UI (formerly Browse Tools), recreating it from a design image. You also identified and fixed scrolling issues where content was overflowing containers. There's an opportunity to strengthen your understanding of layout containment and responsive design patterns.
Recommendation: Study React component composition patterns and CSS layout best practices (especially flexbox and grid). Focus on container queries and responsive patterns that prevent overflow issues. Look into component composition libraries and design system approaches.
Time to Skill Up: 6-10 hours (depending on depth)
Search Keywords: "React component composition patterns", "CSS flexbox grid responsive design", "preventing overflow CSS container queries"
Why This Matters: You're designing UIs that need to work across different screen sizes and user interactions. Strong component architecture makes it easier to build complex UIs without bugs and improves maintainability.
What I Observed: You worked on the "Marketplace" UI (formerly Browse Tools), recreating it from a design image. You also identified and fixed scrolling issues where content was overflowing containers. There's an opportunity to strengthen your understanding of layout containment and responsive design patterns.
Recommendation: Study React component composition patterns and CSS layout best practices (especially flexbox and grid). Focus on container queries and responsive patterns that prevent overflow issues. Look into component composition libraries and design system approaches.
Time to Skill Up: 6-10 hours (depending on depth)
Search Keywords: "React component composition patterns", "CSS flexbox grid responsive design", "preventing overflow CSS container queries"

Strengths Observed

Strengths Observed

  • Security Awareness: You proactively identified data leakage issues before they became problems
  • Iterative Refinement: You worked through UI requirements methodically, asking clarifying questions and improving designs
  • Full-Stack Capability: You comfortably work across backend APIs, frontend UI, and deployment concerns
  • Problem-Solving Approach: You break down complex tasks into manageable steps
  • Security Awareness: You proactively identified data leakage issues before they became problems
  • Iterative Refinement: You worked through UI requirements methodically, asking clarifying questions and improving designs
  • Full-Stack Capability: You comfortably work across backend APIs, frontend UI, and deployment concerns
  • Problem-Solving Approach: You break down complex tasks into manageable steps

Action Items

Action Items

Priority order:
  1. Spend 1-2 hours learning TypeScript utility types and discriminated unions; apply to your connection data structures
  2. Document security patterns for your project (what data is safe to display, filtering/masking functions)
  3. Study one article on advanced React patterns and apply one pattern to your current UI work
  4. Set up a code review checklist focused on type safety and data security for future PRs
Priority order:
  1. Spend 1-2 hours learning TypeScript utility types and discriminated unions; apply to your connection data structures
  2. Document security patterns for your project (what data is safe to display, filtering/masking functions)
  3. Study one article on advanced React patterns and apply one pattern to your current UI work
  4. Set up a code review checklist focused on type safety and data security for future PRs

Recommended Learning Focus

Recommended Learning Focus

Based on your improvement areas, here are search keywords you can use to find relevant resources:
  • Advanced TypeScript: "TypeScript discriminated unions tutorial", "utility types deep dive", "type guards best practices"
  • Security: "frontend security checklist", "secure data handling React", "OWASP frontend security"
  • Component Architecture: "React composition patterns 2024", "advanced CSS layout techniques", "design system architecture"
These terms can be used in HackerNews, dev.to, Medium, or your preferred learning platforms.
undefined
Based on your improvement areas, here are search keywords you can use to find relevant resources:
  • Advanced TypeScript: "TypeScript discriminated unions tutorial", "utility types deep dive", "type guards best practices"
  • Security: "frontend security checklist", "secure data handling React", "OWASP frontend security"
  • Component Architecture: "React composition patterns 2024", "advanced CSS layout techniques", "design system architecture"
These terms can be used in HackerNews, dev.to, Medium, or your preferred learning platforms.
undefined

Tips and Best Practices

提示和最佳实践

  • Run this analysis once a week to track your improvement trajectory over time
  • Pick one improvement area at a time and focus on it for a few days before moving to the next
  • Use the provided search keywords to find resources on platforms like HackerNews, dev.to, Medium, or technical blogs
  • Revisit this report after focusing on an area for a week to see how your work patterns change
  • Save the reports to track your progress and see how your skills evolve over time
  • 每周运行一次本分析，跟踪你长期的提升轨迹
  • 每次选择一个可改进领域，专注学习几天再进入下一个领域
  • 使用提供的搜索关键词在HackerNews、dev.to、Medium或你偏好的学习平台上查找资源
  • 专注提升某个领域一周后，重新查看这份报告，观察你的工作模式发生了哪些变化
  • 保存报告以跟踪你的进展，查看你的技能随时间的成长情况

How Accuracy and Quality Are Maintained

如何保障准确性和质量

This skill:
  • Analyzes your actual work patterns from timestamped chat history
  • Generates evidence-based recommendations grounded in real projects
  • Provides search keywords to help you find relevant learning resources
  • Focuses on actionable improvements, not vague feedback
  • Provides specific time estimates based on complexity
  • Prioritizes areas that will have the most impact on your development velocity
本技能：
  • 基于带时间戳的聊天历史分析你的真实工作模式
  • 生成基于真实项目的、有证据支撑的建议
  • 提供搜索关键词帮助你找到相关的学习资源
  • 聚焦可落地的改进项，而非模糊的反馈
  • 基于复杂度提供具体的时间预估
  • 优先排序对你的开发效率影响最大的领域