Imported from shintwelv/cs-basic-summary (AGENTS.md). Install upstream with npx skills add shintwelv/cs-basic-summary. Copyright stays with the author.

Agent Guidelines: CS-Basic-Summary

This document provides essential information for AI agents contributing to or maintaining this repository.

Project Overview

• Objective: Summarize Computer Science fundamentals at an undergraduate level.
• Primary Audience: Students preparing for exams or technical interviews.
• Source Management: Content is primarily managed via Obsidian (Markdown).
• Web Hosting: Real-time rendering via Docsify on GitHub Pages.

Tech Stack & Configuration

• Docsify: index.html acts as the entry point. It fetches .md files asynchronously. Each subdirectory should have its own README.md (Markdown) as a visual dashboard for its contents.
• Sidebar: Manual navigation is managed in _sidebar.md.
• Styling: Custom CSS embedded in index.html follows a dark, modern blue/slate theme.
• GitHub Pages: Requires a .nojekyll file in the root to bypass Jekyll processing and serve files correctly.

Directory Structure

• /operating-system/: OS concepts (Process, Deadlock, Scheduling, Memory).
• /network/: Networking protocols (OSI, TCP/UDP, HTTP).
• /database/: DB design and performance (SQL/NoSQL, Index, ACID).
• /data-structure/: Logical data arrangements (Stack, Queue, Tree).
• /algorithm/: Algorithm problem-solving patterns (Sort, Search, DP).
• /problems/: BOJ, LeetCode problem solutions.

Content Guidelines

When editing or creating new Markdown files, follow these rules:

1. Obsidian Compatibility: Use Callouts for Q&A sections.
2. Technical Precision:
   • Always differentiate between Single-core (Time-sharing) and Multi-core (Parallelism) when discussing multitasking.
   • Include low-level details where applicable (e.g., PCB/TCB in context switches, Stack/Register/PC in thread contexts).
3. Language: Use Korean for the content (unless requested otherwise), but internal documentation (like this file) should be in English.
4. Markdown Formatting: Use standard GFM (GitHub Flavored Markdown) with clear hierarchies (#, ##, ###).

Maintenance Tasks

• Updating Sidebar: When adding a new file or directory, ensure the link is added to _sidebar.md.
• Directory Index (README.md): When the contents of core directories (/operating-system/, /network/, /data-structure/, /algorithm/) are updated (files added/renamed), update the corresponding README.md index file with a visual card-style link to the new section. Use HTML within Markdown for card-based dashboards.
• Algorithm Problem List: When a new problem (.md) is added to /problems/, update the grid list in /problems/README.md by adding a new problem-item card with appropriate metadata (Platform, Problem ID/Title, Description).
• Docsify Theme: If styles are updated, ensure they are compatible with Docsify's internal structure (e.g., .markdown-section).
• Static Assets: Avoid large binaries. Use externally hosted images or generated icons where possible.

Last Updated: 2026-04-09