Skip to content

Learn Anything

Role: You are a (role). I am a high school student. Objective: To quickly learn {XYZ}. Please generate a comprehensive set of "Getting Started" notes with a target volume of 15 pages and at least 600 lines (excluding line wraps). For any developments occurring after your training data cutoff, mandatory web search must be enabled to prevent misinformation. Output Formatting Requirements: 1. Language: Use English 2. Tech Stack Preference (Descending Order): Python, Shell (zsh > bash > korn), TypeScript, or Node.js. Configuration files should prioritize Markdown > YAML > JSON > XML. 3. Markdown Standards (VS Code & Obsidian compatible): - Use 2-space indentation; do not use tabs. - Use - or 1. for bullet points. - Do not use Markdown dividers (e.g., --- or ***). - Use Level 4 to Level 6 Headers (#### to ######) with the following numbering schema: - Level 4: Sequential integers followed by a period (e.g., #### 1. Overview). - Level 5: Parent index followed by a sequential sub-index (e.g., ##### 3.1. Top-level Diagram). - Level 6: Sequential integers in parentheses without parent reference (e.g., ###### (1) Method A). Note Framework: (The top section must include the current timestamp, relevant tags, and reference sources.)

📅 Sun. 2026-03-15 🕐 16:06 from Gemini 3 Flash

👉 #AI

📎 [Reference1](https://www.google.com/search?q=https://reference-link&authuser=1

1. Overview

  • Instruction 1: Focus on the Why (Design intent, pain points solved). List Features and Use Cases. Keep it concise, avoiding excessive detail in favor of a top-down, structured, and comprehensive overview.
  • Instruction 2: Include a Competitors section. Analyze from market, user segment, and technical domain perspectives to provide a global viewpoint.

2. Concept, Component, & Architecture

2.1. Key Concepts
  • Instruction: Do not simply stack terms. Introduce concepts from simple to complex, respecting logical dependencies.
2.2. Core Components
  • Instruction: Introduce component functions, features, and how they collaborate. Follow the simple-to-complex/dependency-based order.
2.3. Architecture & Design
  • Instruction: Use diagrams (Web links or Mermaid source code) where possible. Emphasize design philosophy and iterative evolution.
2.4. Eco-system
  • Instruction: Emphasize interactions, integrations, and dependencies with external systems from an implementation perspective.

3. Install, Configure, Secure, & Cheatsheet (if needed)

  • Install: Provide core launch configurations, parameters, and dependency setup (Homebrew preferred).
  • Configure: Focus on specific settings for the previously mentioned Use Cases.
  • Secure: Focus on practical Best Practices.
  • Cheatsheet: Provide the most common operations and CLI/SDK code snippets.

4. Bootcamp & Workshops

  • Provide links to official or popular training resources and their learning objectives.
  • Provide a Troubleshooting section for rapid Root Cause Analysis (RCA).
  • Include a Q&A section based on common community/forum interactions.