High-performance structured JSON logging for Node.js. Use when building production APIs that need fast, structured logs for observability platforms (Datadog, ELK, CloudWatch). Provides request logging middleware, child loggers for context, and sensitive data redaction. Choose Pino over console.log for any production TypeScript backend.
Add business metrics using AWS EMF (Embedded Metric Format) to API endpoints. Focus on domain-specific metrics only - AWS AppRunner provides default SLO/SLA metrics. Use when implementing new endpoints, adding command handlers, or instrumenting business events.
Sentry error monitoring and user behavior tracking via CLI. Use when: (1) debugging user-reported issues, (2) checking recent errors/crashes, (3) tracing user actions before an error occurred, (4) searching issues by user email, (5) user asks "Sentryのログを確認して" or similar.
AI面试教练，提供全面的面试准备、模拟和反馈。覆盖技术面试、系统设计、行为面试（STAR法则）、HR面试。生成面试题、模拟真实面试、提供详细反馈和改进建议。当用户准备面试或进行模拟面试时自动触发。
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when: (1) Working with ANY external library (React, Next.js, Supabase, etc.) (2) User asks about library APIs, patterns, or best practices (3) Implementing features that rely on third-party packages (4) Debugging library-specific issues (5) Need current documentation beyond training data cutoff Always prefer this over guessing library APIs or using outdated knowledge.
Guidance for maintaining memory quality through curation. Covers updating outdated memories, marking obsolete content, and linking related knowledge. Use when memories need modification, when new information supersedes old, or when building knowledge graph connections.
AI-native code commenting system with grep-searchable AICODE-* markers for cross-session memory. Use when: working with code files, leaving notes for future sessions, breaking down complex tasks, documenting non-obvious logic, recording bug fixes. Triggers: start coding session, edit code, complex logic, leave note, todo for later, debug session, bug fix, AICODE markers, self-commenting.
Conducts systematic investigations across diverse information sources with cross-validation and credibility assessment. Use when researching complex topics, fact-checking claims, understanding different perspectives, or building comprehensive understanding. Triggers on phrases like "investigate", "verify", "fact check", "cross-reference", "multiple sources", "different perspectives on".
Guidance for using Forgetful semantic memory effectively. Applies Zettelkasten atomic memory principles. Use when deciding whether to query or create memories, structuring memory content, or understanding memory importance scoring.
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
整理与重构已有学习笔记：重划边界、归类重组、合并冗余、精简口语化表达；优化排版与可读性；为各部分补充引导与注释；按从基础到高级建立学习路径并打通知识关联；同时尽量保留原文 Markdown/HTML 强调标记（如 ==高亮==、<u>、Setext 标题等），输出结构清晰、可检索、便于长期维护的笔记体系。
基于 Markdown 笔记，仅用全部标题与少量正文线索，生成学习笔记重构清单：新规划目录（基础→进阶）、旧标题→新目录映射、重命名建议；遵循 planning-with-files（task_plan/notes）与 learning-notes-organizer 的重划边界/归类重组思路，不改正文。
Up-to-date library documentation retrieval using Context7 MCP tools. Process THINK → RESOLVE → FETCH → APPLY. Use when fetching library docs, resolving package names to IDs, getting implementation guides, exploring API references. Provides package resolution strategy, trust score evaluation, token scaling (3K-20K), topic selection patterns.
Use when designing or architecting Rust applications, creating comprehensive project documentation, planning async/await patterns, defining domain models with ownership strategies, structuring multi-crate workspaces, or preparing handoff documentation for Director/Implementor AI collaboration
API 文档生成工具。适用于任何后端技术栈的 API 接口文档生成和维护，确保前后端接口规范统一。
Generate enterprise module documentation with 26-section structure and folder hierarchy. Use for module docs, enterprise features, detailed specs in docs/business-features/{Module}/. Includes README, INDEX, API-REFERENCE, detailed-features/. Triggers on "module docs", "enterprise feature docs", "business module", "26-section docs", "detailed feature specs". For single-file quick docs, use feature-docs instead.
