cs-note

Appends short project-specific facts to AGENTS.md under fixed categorized sections.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/wildlily1021/XW_Software --skill cs-note-wildlily1021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cs-note
Source: https://github.com/wildlily1021/XW_Software/tree/main/.agents/skills/cs-note
Command: npx skills add https://github.com/wildlily1021/XW_Software --skill cs-note-wildlily1021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Small but critical project facts—build flags, startup prerequisites, path conventions, environment variable rules—often get lost or repeated across sessions. This Skill records them into AGENTS.md, which is automatically loaded every session, so the AI always knows these one-line project constraints without being told again. ## Core Features & Use Cases - Fragment Knowledge Capture: Appends one-line facts (build prerequisites, command traps, path conventions, credential rules) to a fixed "Project Fragment Knowledge" section in AGENTS.md. - Strict Entry Criteria: Filters candidates by length, frequency, and stability, redirecting longer or task-specific content to other documentation skills to prevent file bloat. - Deduplication and Structure Control: Locates entries via a managed anchor comment, checks for duplicates before appending, and enforces fixed sections with a soft 150-line limit. - Use Case: After discovering that a project requires pnpm run gen before compiling, tell the AI to record it, and every future session will automatically know this constraint. ## Quick Start Tell the AI to record a project fact by saying something like "记一笔:编译前要先运行 pnpm run gen" and it will append the entry to the correct section of AGENTS.md.

Frequently Asked Questions about cs-note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI remember project-specific build requirements every session?▼

Record them as one-line entries in AGENTS.md, which is automatically loaded each session. This Skill appends facts like build prerequisites or command traps to a fixed categorized section, so the AI always sees them without being reminded.

What kind of notes should go into AGENTS.md versus separate documentation files?▼

AGENTS.md should hold short (one or two lines), frequently needed, stable facts like compile flags or path conventions. Longer explanations, bug fixes, or library usage guides belong in separate documentation files that are retrieved on demand.

Does this Skill create an AGENTS.md file if the project does not have one?▼

It does not create one automatically. If neither AGENTS.md variant exists, it asks the user for confirmation before creating a new AGENTS.md file at the project root.

How does it prevent AGENTS.md from becoming bloated?▼

It enforces fixed sections, one-entry-per-invocation writes, deduplication checks, and a soft 150-line limit. When limits are approached, it prompts the user to migrate entries to longer-form documentation instead of silently expanding.

When should I not use AGENTS.md for a project note?▼

Avoid it for temporary workarounds, short-term status like current sprint goals, multi-line explanations, or decision rationales. Those expire or need context and belong in issue specs, decision records, or dedicated knowledge documents.