# Database Foundation Course Writer

Write Chinese "数据库筑基课" Markdown articles for database architects, DBAs, and application...

- Repository: https://github.com/digoal/blog (8605 stars)
- Category: Data and ML
- License: GPL-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add digoal/blog --skill database-foundation-course-writer -g -a claude-code -y`
Codex: `npx skills add digoal/blog --skill database-foundation-course-writer -g -a codex -y`
Cursor: `npx skills add digoal/blog --skill database-foundation-course-writer -g -a cursor -y`
Gemini CLI: `npx skills add digoal/blog --skill database-foundation-course-writer -g -a gemini-cli -y`

## Description

Write Chinese "数据库筑基课" Markdown articles for database architects, DBAs, and application developers. Use when the user provides a database foundation article title and references such as technical docs, product manuals, open-source repositories, DeepWiki pages, papers, source code, or related blog posts, and wants a rigorous, SVG-rich, practice-oriented GitHub-renderable Markdown article saved as a .md file.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Database Foundation Course Writer

## Overview

Write a publishable Chinese Markdown article in the "数据库筑基课" style. The article must help database architects, DBAs, and application developers understand the mechanism, tradeoffs, practice path, and operational boundaries of a database technology. Default to GitHub-renderable Markdown plus referenced SVG figure files.

## Inputs

Require or infer:

- Article title.
- Reference materials: official docs, product manuals, source repositories, DeepWiki pages, papers, source code, existing local articles, SQL examples, benchmark data, or issue discussions.
- Target technology category: table storage, index structure, data type/operator, optimizer scan algorithm, execution operator, maintenance mechanism, or scenario practice.

If key references are missing, search primary sources first. Prefer official docs, source code, papers, and project README over secondary summaries.

## Output

Save the final article as a `.md` file. Use the current project's `markdown` folder when that is the established article-output convention; otherwise use an existing article/output folder if the repository clearly has one. Use a filename derived from the title when no filename is provided, or follow the repository's existing naming convention if obvious.

Save SVG figures as standalone `.svg` files in a sibling asset directory such as `<article-slug>-assets/`, unless the repository has an established image/asset convention. Reference them from Markdown with relative image syntax:

```markdown
![图 1：页面、元组与可见性信息的关系](./<article-slug>-assets/page-tuple-visibility.svg)
```

Do not save until the article has passed the validation checklist.

## Workflow

The rest: https://github.com/digoal/blog/blob/HEAD/skills/database-foundation-course-writer/SKILL.md