agentleFS
th3r-devth3r-dev/th3-skills/skills/documentation/SKILL.md

documentation

Skill2 starsChanged 2 days agoMITView on GitHub

Documentation toolkit, one skill with sub-skills. (1) doc-style: write and build documentation for any work product (API, deploy or update, system, feature, release, test round) in one house style, seven fixed skeletons, a TH Sarabun theme with change highlighting, and a matching PDF + DOCX from one Markdown source; (2) pdf-operations: merge, split, extract, reorder, rotate or overlay PDF pages through an existing pdf-lib pipeline instead of reimplementing it. Use WHENEVER the user wants to document, write up, report on or hand over something ("write an API spec", "เขียนเอกสาร", "ทำรายงานอัปเดต", "make a user guide", "changelog for this release", "export as PDF and Word"), make a document match the house style, or merge / split / rotate / stamp PDFs. Read the sub-skill's SKILL.md before acting.

115 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-media-pack, project-preferences and 10 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.
  • DepressionCenterSkill

    create-media-pack

    Create a coordinated project branding and media pack with three accessible design options, approved vector artwork, image exports, a branding guide, and README integration. Use when asked for a repository media pack, brand kit, or complete project visual identity.

    Also in 5 projects that use this

  • DepressionCenterSkill

    project-preferences

    Apply repository-specific preferences when planning, implementing, or reviewing changes in this project.

    Also in 6 projects that use this

  • thistleknotSkill

    response-style

    Response and prose protocol. Use when drafting user-facing prose, expanding a user's ideas, or tuning tone and format to preserve voice, avoid AI cliches, and maintain coherent answers.

    Also in 7 projects that use this

  • BrowserWorksSkill

    accessibility-frontend-review

    Performs an accessibility code review of a local diff or Phabricator revision in the style of the Firefox accessibility team. Use this skill whenever the user asks to review a Phabricator patch or revision for accessibility issues, mentions a D-number (like D284142) in the context of accessibility review, asks "does this patch have any a11y issues", or wants to check a diff against accessibility guidelines. Also use it when the user says things like "can you review this for a11y", "check this patch", or "give me an accessibility review of D[number]". Invoke proactively when the user pastes a phabricator.services.mozilla.com URL or shares a revision ID alongside any accessibility concern. Invoke when questions about the following topics are raised: aria properties, aria roles, high contrast mode, forced colors, prefers contrast, focus order, screen readers, assistive technology.

    Also in 4 projects that use this

  • BrowserWorksSkill

    android-new-module

    Guide for creating new Android gradle modules in the android-components project.

    Also in 4 projects that use this

  • +7 more from BrowserWorks

The file

Files
SKILL.md

documentation: sub-skills

When the work is…ReadScripts
"write an API spec", "เขียนเอกสาร", "user guide", "README", "changelog", "export as PDF and Word"doc-style/SKILL.md + references/doc-types.mddoc-style/scripts/build_doc.py (Markdown → HTML/PDF/DOCX)
"merge these PDFs", "split into pages", "rotate / reorder pages", "stamp an overlay"pdf-operations/SKILL.mdnone: reuses the project's pdf-lib pipeline

They chain: doc-style builds the PDF; pdf-operations merges it with annexes or stamps it.

Rules every sub-skill keeps

  • Ground every fact in the source. A document states only what the code, ticket or output shows.
  • Reuse before building. One theme file, one existing PDF pipeline; no second copy of either.

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.