菜单
Keep seed.md (the repository DNA) in sync with the actual repo state. Use when: ending a growth tick; after adding content or structure; whenever the seed's inventories may have drifted from reality. Concept-agnostic. Regenerates seed.md sections 1–7 from the live repo; never touches the Evolution Log (section 8).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Add one or more topics to this knowledge-base repository. Use when: adding a new item (event, person, work, discovery, etc.) within the repo concept; unsure whether a topic deserves a knowledge-table row or a full dedicated article; bulk-adding multiple topics at once; auto-discovering coverage gaps across the concept's categories. Concept-agnostic — reads subject/taxonomy from seed.md. Orchestrates research, format selection, file creation, README linking, and session logging.
Generate and refresh the structural artifacts of this knowledge base — category index pages, a timeline, a master index/TOC, and cross-reference links. Use when: new topic files were added and indices need updating; building out repository structure beyond flat content; running a structure item from the roadmap. Concept-agnostic and idempotent — derives everything from the concept and existing content; only rewrites generated regions.
Decide what this knowledge base should grow next and update ROADMAP.md. Use when: starting a growth tick and need to choose the next 1–3 items; the backlog is low and needs refilling; reconciling completed work into Done. Concept-agnostic — reads the concept and current state from seed.md and the repo. Reads/writes ROADMAP.md only.
Publish the current working session for this repository. Use when: finishing a session and ready to commit and push changes; wanting to log session work to seed.md before committing; pushing new topics, articles, README updates, or instruction changes to GitHub. Concept-agnostic. Runs encode-seed → git status review → commit → push in one orchestrated flow.
Research a topic within this repository's concept and return structured findings. Use when: looking up items (events, people, works, discoveries, etc.) within the concept; crawling authoritative sources; verifying facts and attribution; gathering facts before deciding whether to create a knowledge-table row or a dedicated file. Concept-agnostic — reads subject/scope/source_strategy from seed.md. Does NOT write files on its own — use add-topic for that.
Generate and refresh the structural artifacts of this knowledge base — category index pages, a timeline, a master index/TOC, and cross-reference links. Use when new topic files were added and indices need updating, when building repository structure beyond flat content, or when running a structure item from the roadmap. Concept-agnostic and idempotent — derives everything from the concept and existing content; only rewrites generated regions.
| name | sync-seed |
| description | Keep seed.md (the repository DNA) in sync with the actual repo state. Use when: ending a growth tick; after adding content or structure; whenever the seed's inventories may have drifted from reality. Concept-agnostic. Regenerates seed.md sections 1–7 from the live repo; never touches the Evolution Log (section 8). |
| argument-hint | No arguments. Run after content/structure changes to refresh the DNA. |
seed.md is the repository's DNA and rebuild blueprint. This skill regenerates its generated sections (1–7) so they always reflect the real repo. The Evolution Log (section 8) is append-only and must never be regenerated or reordered here.
.github/ (skills, prompts, agents, instructions), README.md,
ROADMAP.md, and all category folders / generated artifacts.Rewrite each section to match reality:
concept block unless the concept genuinely changed
(changing it is a deliberate retarget, not a sync). Do not invent changes.concept.subject..github/
(one row per file, with its purpose). Add/remove rows as files change.TIMELINE.md,
index.md/TOC, cross-refs) vs. not-yet-generated.Leave section 8 exactly as-is. Appending to it is the job of the encode-seed prompt, not this skill.
Report which sections changed and a one-line diff summary (e.g. "Architecture: +1 file; Content: 13→15 rows").
add-topic / plan-roadmap).