agentleFS
Sign inStart free
AterDevAterDev/Perigon.CLI/.agents/skills/docs/SKILL.md

docs

Skill54 starsChanged 2 months agoApache-2.0View on GitHub

Use for Perigon documentation work across this workspace, especially Perigon.docs/Content/docs/Perigon bilingual and versioned docs, syncing zh-CN and en-US content, updating docs from Perigon.CLI, Perigon.template, and Perigon.Modules changes, and deciding whether to revise existing pages or add new documentation.

165 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use import-memory, perf and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • amirbironSkill

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 3 projects that use this

  • MicrosoftSkill

    perf

    Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.

    Also in 4 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 4 projects that use this

  • vbrevikSkill

    work

    Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

    Also in 7 projects that use this

  • mbwsimsSkill

    impact

    This skill should be used when the user asks to "check the impact", "what will break if I change this", "blast radius", "impact analysis", "what depends on this", "who imports this", "is it safe to change this", mentions "/impact", or wants to understand the consequences of modifying a specific file or function before making changes.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 11 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check workspace changes in Perigon.template, Perigon.CLI, and Perigon.Modules first to determine what actually changed.

    line 17
  2. Very specific:

    Search existing pages under Perigon.docs/Content/docs/Perigon for the closest matching topic before creating new content.

    line 19
  3. Distinctive:

    Prefer updating or correcting an existing document when the topic already exists.

    line 20
  4. Distinctive:

    Create a new page only when the change introduces a clearly new concept, workflow, or reference topic.

    line 21
  5. Distinctive:

    Keep Chinese and English docs aligned in structure and meaning.

    line 22
  6. Distinctive:

    Place content in the correct version folder.

    line 23
  7. Distinctive:

    Keep folder symmetry when equivalent pages exist in both languages.

    line 28
  8. Distinctive:

    Document observable behavior from the repositories, not speculation or roadmap assumptions.

    line 29
  9. Distinctive:

    Prefer concise task-oriented guidance, with commands, paths, prerequisites, and limitations called out directly.

    line 30
  10. Very specific:

    When adding a new page in a section that uses .order, update the corresponding .order file so navigation stays correct.

    line 31
  11. Distinctive:

    If the source change is internal only and has no user, contributor, or operator impact, do not add noise to the docs.

    line 32
  12. Distinctive:

    Verify that new or updated pages are placed under the correct language and version directories.

    line 43
  13. Distinctive:

    Verify that paired zh-CN and en-US pages remain semantically aligned.

    line 44
  14. Distinctive:

    Verify commands, paths, and repository names against current workspace content before finishing.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 129 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Perigon Documentation Workflow

Workspace Scope

  • The authoritative documentation lives under Perigon.docs/Content/docs/Perigon.
  • Documentation is versioned by folder, then split by language: zh-CN/<version> and en-US/<version>.
  • Source changes that drive Perigon docs usually come from Perigon.CLI, Perigon.template, and Perigon.Modules.

Workflow

  1. Identify the affected feature, command, template behavior, module behavior, or contributor workflow.
  2. Check workspace changes in Perigon.template, Perigon.CLI, and Perigon.Modules first to determine what actually changed.
  3. Ignore unrelated diffs and extract only Perigon-relevant behavior, constraints, commands, paths, version notes, or user-visible workflow changes.
  4. Search existing pages under Perigon.docs/Content/docs/Perigon for the closest matching topic before creating new content.
  5. Prefer updating or correcting an existing document when the topic already exists.
  6. Create a new page only when the change introduces a clearly new concept, workflow, or reference topic.
  7. Keep Chinese and English docs aligned in structure and meaning. When one side changes, update the matching page in the other language unless the user explicitly asks for one language only.
  8. Place content in the correct version folder. If behavior differs by version, document the version-specific scope explicitly instead of silently overwriting another version's guidance.

Conventions

  • Preserve the existing section taxonomy and naming style under both zh-CN and en-US.
  • Keep folder symmetry when equivalent pages exist in both languages.
  • Document observable behavior from the repositories, not speculation or roadmap assumptions.
  • Prefer concise task-oriented guidance, with commands, paths, prerequisites, and limitations called out directly.
  • When adding a new page in a section that uses .order, update the corresponding .order file so navigation stays correct.
  • If the source change is internal only and has no user, contributor, or operator impact, do not add noise to the docs.

Search Targets

  • Perigon.docs/Content/docs/Perigon/zh-CN/<version> for Chinese pages.
  • Perigon.docs/Content/docs/Perigon/en-US/<version> for English pages.
  • Perigon.CLI/src, Perigon.template, and Perigon.Modules/src for feature and workflow changes.
  • README files, packaging scripts, command registration, AppHost/template structure, and module scripts when documenting usage or contributor flows.

Validation

  • Verify that new or updated pages are placed under the correct language and version directories.
  • Verify that paired zh-CN and en-US pages remain semantically aligned.
  • Verify commands, paths, and repository names against current workspace content before finishing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free