agentleFS
CRELLIA-S-LCRELLIA-S-L/srs-dd/.claude/skills/srs-page/SKILL.md

srs-page

Skill0 starsChanged 33 days agoMITView on GitHub

Render the specification as one self-contained HTML page and open it — for reading rather than grepping, and for handing to somebody who will never clone the repository. Invoke when the user asks to see, show, open, render or share the specification, the requirements or the documentation as a page.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    The file is self-contained: No network, no CDN, no server: it opens from file:// and it can simply be sent to somebody.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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
<!-- Copyright (c) 2026 CRELLIA S.L. — part of SRS-DD, distributed under the MIT License -->

Reading the specification as a page

One command renders it and opens it:

python3 srs-dd/tools/srs_view.py --open

It writes .srs-site/index.html — the directory ignores itself, so nothing lands in the project's history — and opens it in the reader's browser. Give a path to put it elsewhere: --html docs/spec.html --open.

What the command does not say

The file is self-contained. No network, no CDN, no server: it opens from file:// and it can simply be sent to somebody. That is what makes it the answer for a reviewer, a new joiner, or anyone outside the repository.

Links to code work only if the page knows where the code lives. Pass the forge address once:

python3 srs-dd/tools/srs_view.py --html public/index.html \
    --repo-url https://github.com/<owner>/<repo>/blob/<sha>

Without it the paths are still shown, they just do not lead anywhere.

The layers have pages of their own. Where the project keeps them, python3 srs-dd/tools/srs_arch_doc.py --html prints the architecture — the parts, what each answers for, the dependency diagram drawn as an image — and python3 srs-dd/tools/srs_grounds.py --html prints the grounds dashboard. Both print to stdout, so the caller decides where they land, and the published set is index.html, arch.html, grounds.html side by side. Tell each page which others are beside it, or it links none of them:

python3 srs-dd/tools/srs_view.py --html site/index.html --link arch.html,grounds.html
python3 srs-dd/tools/srs_arch_doc.py --html --link index.html,grounds.html > site/arch.html
python3 srs-dd/tools/srs_grounds.py --html --link index.html,arch.html > site/grounds.html

A name that is not one of the three, or the page's own, is refused rather than carried: a link exists because somebody said that file will be there.

CI may already publish it. The templates in ci/ render the same pages as a build artifact — the GitLab one from the default branch, the GitHub one on every run, for whichever layers the project keeps — and each says how to switch on publishing them through Pages, so a link may exist that is always current — check before mailing a copy that will be stale next week.

Baselines need history. The page compares frozen states by reading the commits behind them; a shallow checkout has none, and the page says so instead of pretending there are none.

When it is the wrong tool

For a question about one requirement — what it links to, what breaks if it changes — the terminal answers faster: python3 srs-dd/tools/srs_view.py <ID>, or --code <path> from the other end. The page is for reading a specification, not for interrogating it.

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.