learn 是做什麼的？
執行六階段研究流程，將不熟悉的領域、原始碼套件或收集的資料轉換為可發佈的輸出。適用於使用者以任何語言提出研究、深入學習、彙整來源、綜合不熟悉材料或將來源套件轉化為連貫參考資料時使用。不適用於快速查詢或單一檔案閱讀。
執行六階段研究流程，將不熟悉的領域、原始碼套件或收集的資料轉換為可發佈的輸出。適用於使用者以任何語言提出研究、深入學習、彙整來源、綜合不熟悉材料或將來源套件轉化為連貫參考資料時使用。不適用於快速查詢或單一檔案閱讀。
這是一個名為「tw93/learn」的 AI 代理技能，專門用於執行一個結構化的六階段研究流程。它的核心價值在於能將開發者不熟悉的技術領域、大型原始碼套件或零散的收集資料，系統性地轉化為可直接發佈的參考文件或報告。此技能支援多種 AI 代理平台，如 Claude Code、Cursor 和 Codex，並能應對多語言的使用者請求，非常適合用於深入研究、知識綜合和資料整理。其工作流程包括發現、提煉、組織、撰寫、審查和最終發佈，確保輸出內容的完整性和準確性，但並不適合用於快速查詢或處理單一檔案。透過自動化這些繁瑣的研究步驟，它幫助開發者節省大量時間，並產出高品質的結構化知識成果。
npx skills add https://github.com/tw93/waza/tree/main/skills/learnInstalled? Explore more 研究與資料分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
執行六階段研究流程，將不熟悉的領域、原始碼套件或收集的資料轉換為可發佈的輸出。適用於使用者以任何語言提出研究、深入學習、彙整來源、綜合不熟悉材料或將來源套件轉化為連貫參考資料時使用。不適用於快速查詢或單一檔案閱讀。
This repo contains 7 individual skills — each has its own dedicated page.
Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask review/看看代码/合并前/看看issue/PR/release/push or to implement an approved plan, with safety gates for dirty and untracked worktrees. Not for exploring ideas, debugging root causes, or prose review.
Produces distinctive, production-grade UI for pages, components, visual interfaces, typography, and screenshot-driven polish. Use when users ask in any language for UI, page, component, frontend, typography, screenshot-grounded visual polish, or complaints that a screen looks unclear, ugly, inconsistent, or visually wrong. Not for backend logic or data pipelines.
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask 检查claude/检查codex/检查pi/配置检查/健康度 or report agents ignoring instructions, missing validation, or code becoming hard to maintain. Not for debugging code or reviewing PRs.
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask 看这个链接/读一下/read this/check this URL. Not for local text files already in the repo.
Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.
Rewrites and polishes prose in Chinese or English, removes AI-like wording, and reviews product localization copy while preserving intent for drafts, docs, release notes, launch copy, and social posts. Use when users ask in any language to draft, rewrite, proofread, localize, polish release notes, remove AI-like wording, or prepare launch and social copy. Not for code comments, commit messages, or inline docs.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.