agentleFS
Sign inStart free
opensite-aiopensite-ai/opensite-skills/client-side-routing-patterns/SKILL.md

client-side-routing-patterns

Skill15 starsChanged 19 days agoNo licenceView on GitHub

Client-side routing patterns using the History API — managing URL state without full page reloads, building provider-optional routing hooks, SSR-safe browser API access, scroll behavior, and parameter parsing. Covers both the architectural patterns (custom routechange events, popstate listeners) and practical hook design for zero-dependency routing libraries. Use when building or extending routing systems, debugging navigation bugs, or working with @page-speed/router patterns.

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.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

Does it work?

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

Reviews can't be read right now.

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