bearings
Skill2 starsChanged 31 days agoApache-2.0View on GitHub
Explore frontend architecture by reframing journeys, ownership, and the experience of time. Use before committing a product direction, not as a compulsory frontend architecture checklist.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- kunchenguid/firstmatetheir own version, first seen Oct 8, 2026
- EvanBatten/firstmate-for-windowstheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- kunchenguid/firstmate★ 8.7ksame name
- EvanBatten/firstmate-for-windows★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- canonSkill
- colorSkill
- formSkill
- graphicsSkill
- layoutSkill
- motionSkill
- pilotSkill
- systemsSkill
- typeSkill
- holdfastSkill
- aegisSkill
- assaySkill
- flightlineSkill
- gaugeSkill
- groundworkSkill
- gungnirSkill
- husbandrySkill
- load-bearingSkill
- pilotSkill
- plumbSkill
- stationkeepingSkill
- crucibleSkill
- envoySkill
- forgeSkill
- ledgerSkill
- prospectSkill
- reckoningSkill
- forageSkill
- touchstoneSkill
- bulwarkSkill
- keelSkill
- liverySkill
- lookoutSkill
- pilotSkill
- seaworthySkill
- trialsSkill
- wellspringSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Treat the experience as a conversation, a workbench, or a guided expedition.
- Distinctive: line 50
Read selectively when a thread needs another perspective or a concrete technique.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
<!--
Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0.
See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0
-->bearings
Explore frontend architecture by reframing journeys, ownership, and the experience of time. Use before committing a product direction, not as a compulsory frontend architecture checklist.
Starting point
A frontend is one interpretation of a user journey. Change the story of where the user is, what they know, or what waiting means, and a different architecture may become natural.
Bring a question, fragment, reference, or tension. Follow whichever association becomes useful; these invitations are not a sequence to complete. Speculation should remain distinguishable from an observed fact.
Thought experiments
Change the journey metaphor
Treat the experience as a conversation, a workbench, or a guided expedition. What should persist, what should be visible, and what can remain unfinished in each?
Design under a different clock
Imagine instant responses, intermittent connectivity, then hour-long jobs. Invent continuity for each world rather than hiding every delay behind a spinner.
Move ownership
Imagine the URL owns the workspace, the server owns it, or the person carries it as a local document. What new sharing, recovery, and collaboration behaviours appear?
A possible turn
A reporting product begins as a dashboard. Treating it as a notebook suggests saved questions and annotations; treating it as a control room suggests live exceptions; treating it as correspondence suggests scheduled narratives. The rendering strategy follows the chosen experience, not the other way around.
Leave the space open
Offer a few genuinely different possibilities, a sketch, an analogy, or a sharper question when useful. Do not turn every prompt into a scored diagnostic, a completion gate, or a demand for an action plan. The human may choose a direction, combine them, or leave the question open.
Keel can build one selected journey end to end. Wellspring explores state representations; neither requires a certificate from this lens.
Optional references
Read selectively when a thread needs another perspective or a concrete technique. The notes supply possibilities, examples, and limits; none is a prerequisite or a requirement to close the exploration.
- Navigate by the experience being proposed
- Different meanings of better
- What does the surface promise during uncertainty?
- Use context without inventing the requirement
- Authorship and continuity in a frontend
- Different stories for the same frontend
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
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.