以下为本文档的中文说明该技能用于分析用户的Claude Code聊天历史记录识别编码模式、开发技能差距和潜在的改进领域。它通过分析对话中暴露的编程习惯、技术栈使用频率、错误类型和问题解决模式生成个性化的开发者成长报告。该技能帮助开发者在日常编码实践中获得元认知层面的反馈了解自己的技术优势和待提升方向。适用于希望系统化提升编程技能的个人开发者、技术团队管理者需要了解团队成员技术成长状况的场景。通过数据驱动的分析该技能为用户提供定制化的学习路径建议和资源推荐帮助开发者在AI辅助编程时代持续成长填补知识盲区提升整体开发效率。该技能提供了详细的操作指南和最佳实践帮助用户快速上手并深入掌握。通过系统的功能模块划分和丰富的应用场景说明用户可以在实际项目中有效运用该技能提升工作效率。该技能注重实用性和可操作性涵盖从基础配置到高级功能的完整知识体系满足不同层次用户的学习需求。持续更新和优化的内容确保用户始终能够接触到最新的技术发展和行业实践。通过此技能的学习和应用用户可以减少摸索时间快速获得可用的解决方案将精力集中在核心业务逻辑和创新工作上从而在技术快速迭代的环境中保持竞争力。该技能的模块化设计使其易于扩展和定制用户可以根据自身需求灵活调整应用方式实现最大化的价值产出。该技能整合了常见的设计模式和最佳实践提供了清晰的学习路径和参考资料帮助用户在短时间内建立起完整的知识框架并有能力在实际项目中灵活运用所学内容解决问题。Developer Growth AnalysisThis 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.When to Use This SkillUse this skill when you want to:Understand your development patterns and habits from recent workIdentify specific technical gaps or recurring challengesDiscover which topics would benefit from deeper studyGet curated learning resources tailored to your actual work patternsTrack improvement areas across your recent projectsFind high-quality articles that directly address the skills you’re developingThis skill is ideal for developers who want structured feedback on their growth without waiting for code reviews, and who prefer>What This Skill DoesThis skill performs a six-step analysis of your development work: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.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.Detects Improvement Areas: Recognizes patterns that suggest skill gaps, repeated struggles, inefficient approaches, or areas where you might benefit from deeper knowledge.Generates a Personalized Report: Creates a comprehensive report showing your work summary, identified improvement areas, and specific recommendations for growth.Finds Learning Resources: Uses HackerNews to curate high-quality articles and discussions directly relevant to your improvement areas, providing you with a reading list tailored to your actual development work.Sends to Your Slack DMs: Automatically delivers the complete report to your own Slack direct messages so you can reference it anytime, anywhere.How to UseAsk Claude to analyze your recent coding work:Analyze my developer growth from my recent chatsOr be more specific about which time period:Analyze my work from today and suggest areas for improvementThe skill will generate a formatted report with:Overview of your recent workKey improvement areas identifiedSpecific recommendations for each areaCurated learning resources from HackerNewsAction items you can focus onInstructionsWhen a user requests analysis of their developer growth or coding patterns from recent work:Access Chat HistoryRead the chat history from~/.claude/history.jsonl. This file is a JSONL format where each line contains:display: The user’s message/requestproject: The project being worked ontimestamp: Unix timestamp (in milliseconds)pastedContents: Any code or content pastedFilter for entries from the past 24-48 hours based on the current timestamp.Analyze Work PatternsExtract 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 topicsProblems that took multiple attempts to solveQuestions indicating knowledge gapsComplex architectural decisionsApproach Patterns: How does the user solve problems? (e.g., methodical, exploratory, experimental)Identify Improvement AreasBased 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”Generate ReportCreate a comprehensive report with this structure:# 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 users 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] --- [Repeat for 2-4 additional areas] ## Strengths Observed [2-3 bullet points highlighting things youre 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] ## Learning Resources [Will be populated in next step]Search for Learning ResourcesUse Rube MCP to search HackerNews for articles related to each improvement area:For each improvement area, construct a search query targeting high-quality resourcesSearch HackerNews using RUBE_SEARCH_TOOLS with queries like:“Learn [Technology/Pattern] best practices”“[Technology] advanced patterns and techniques”“Debugging [specific problem type] in [language]”Prioritize posts with high engagement (comments, upvotes)For each area, include 2-3 most relevant articles with:Article titlePublication dateBrief description of why it’s relevantLink to the articleAdd this section to the report:## Curated Learning Resources ### For: [Improvement Area] 1. **[Article Title]** - [Date] [Description of what it covers and why its relevant to your improvement area] [Link] 2. **[Article Title]** - [Date] [Description] [Link] [Repeat for other improvement areas]Present the Complete ReportDeliver the report in a clean, readable format that the user can:Quickly scan for key takeawaysUse for focused learning planningReference over the next week as they work on improvementsShare with mentors if they want external feedbackSend Report to Slack DMsUse Rube MCP to send the complete report to the user’s own Slack DMs:Check if Slack connection is active via RUBE_SEARCH_TOOLSIf not connected, use RUBE_MANAGE_CONNECTIONS to initiate Slack authUse RUBE_MULTI_EXECUTE_TOOL to send the report as a formatted message:Send the report title and period as the first messageBreak the report into logical sections (Summary, Improvements, Strengths, Actions, Resources)Format each section as a well-structured Slack message with proper markdownInclude clickable links for the learning resourcesConfirm delivery in the CLI outputThis ensures the user has the report in a place they check regularly and can reference it throughout the week.Example UsageInputAnalyze my developer growth from my recent chatsOutput# Your Developer Growth Report **Report Period**: November 9-10, 2024 **Last Updated**: November 10, 2024, 9:15 PM UTC ## 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. ## Improvement Areas (Prioritized) ### 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. Theres an opportunity to use discriminated unions and type guards more effectively. **Recommendation**: Study TypeScripts 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 ### 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 ### 3. Component Architecture and Responsive UI Patterns **Why This Matters**: Youre 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. Theres 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) ## 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 ta sks into manageable steps ## 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 ## Curated Learning Resources ### For: Advanced TypeScript Patterns 1. **TypeScripts Advanced Types: Generics, Utility Types, and Conditional Types** - HackerNews, October 2024 Deep dive into TypeScripts type system with practical examples and real-world applications. Covers discriminated unions, type guards, and patterns for ensuring compile-time safety in complex applications. [Link to discussion] 2. **Building Type-Safe APIs in TypeScript** - HackerNews, September 2024 Practical guide to designing APIs with TypeScript that catch errors early. Particularly relevant for your connection configuration work. [Link to discussion] ### For: Secure Data Handling in Frontend 1. **Preventing Information Leakage in Web Applications** - HackerNews, August 2024 Comprehensive guide to data security in frontend applications, including filtering sensitive information, secure logging, and audit trails. [Link to discussion] 2. **OAuth and API Key Management Best Practices** - HackerNews, July 2024 How to safely handle authentication tokens and API keys in applications, with examples for different frameworks. [Link to discussion] ### For: Component Architecture and Responsive Design 1. **Advanced React Patterns: Composition Over Configuration** - HackerNews Explores component composition strategies that scale, with examples using modern React patterns. [Link to discussion] 2. **CSS Layout Mastery: Flexbox, Grid, and Container Queries** - HackerNews, October 2024 Learn responsive design patterns that prevent overflow issues and work across all screen sizes. [Link to discussion]Tips and Best PracticesRun this analysis once a week to track your improvement trajectory over timePick one improvement area at a time and focus on it for a few days before moving to the nextUse the learning resources as a study guide; work through the recommended materials and practice applying the patternsRevisit this report after focusing on an area for a week to see how your work patterns changeThe learning resources are intentionally curated for your actual work, not generic topics, so they’ll be highly relevant to what you’re buildingHow Accuracy and Quality Are MaintainedThis skill:Analyzes your actual work patterns from timestamped chat historyGenerates evidence-based recommendations grounded in real projectsCurates learning resources that directly address your identified gapsFocuses on actionable improvements, not vague feedbackProvides specific time estimates based on complexityPrioritizes areas that will have the most impact on your development velocity3d:[“,,,L40”,null,{“content”:“$41”,“frontMatter”:{“name”:“developer-growth-analysis”,“description”:“Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.”}}]3e:[“KaTeX parse error: Expected }, got EOF at end of input: …,children:[[”,“div”,null,{“className”:“flex items-center justify-between border-b border-border bg-muted/30 px-4 py-2.5”,“children”:[[“KaTeX parse error: Expected }, got EOF at end of input: …,children:[”,“span”,null,{“className”:“truncate text-xs font-medium text-muted-foreground”,“children”:“同仓库更多 Skills”}]}],[“KaTeX parse error: Expected EOF, got } at position 88: …ldren:同仓库}]]}̲],[”,“div”,null,{“className”:“p-4 sm:p-5”,“children”:[[“,h2,null,id:related−skills−heading,className:text−2xlfont−semiboldtracking−normaltext−foreground,children:同仓库更多Skills],[,h2,null,{id:related-skills-heading,className:text-2xl font-semibold tracking-normal text-foreground,children:同仓库更多 Skills}],[,h2,null,id:related−skills−heading,className:text−2xlfont−semiboldtracking−normaltext−foreground,children:同仓库更多Skills],[”,“div”,null,{“className”:“mt-4 grid gap-3 sm:grid-cols-2”,“children”:[“L42,L42,L42,L43”,“L44,L44,L44,L45”,“L46,L46,L46,L47”]}]]}]]}]48:I[206516,[“/_next/static/chunks/051aanbhrv4br.js”,“/_next/static/chunks/0mizr60h7ayzt.js”,“/_next/static/chunks/0v9lm1dmbdoo-.js”,“/_next/static/chunks/0rxr1j1j3j-.r.js”,“/_next/static/chunks/02ftybezfvqjd.js”,“/_next/static/chunks/0.v9ksvnnj8ia.js”,“/_next/static/chunks/0bn6id96nx3k.js,“/_next/static/chunks/13ybnhn37c.tc.js”,“/_next/static/chunks/0_fnrdtruz8uf.js”,“/_next/static/chunks/0r6l15utt1mwb.js”,“/_next/static/chunks/0dm9a5into854.js”,/_next/static/chunks/07k6hqoibtcn.js”,“/next/static/chunks/0b4cao.4y…j.js”,“/_next/static/chunks/02i-n28z7kjd0.js”],“default”]