| name | lesaruss-internal-page |
| description | LESARUSS internal HTML page guardrail. USE THIS SKILL automatically whenever creating, editing, or rewriting any HTML file in a LESARUSS folder, even if the user does not ask. Applies to playbooks, briefings, reports, blueprints, mocks, daily briefs, ops docs, agendas, meeting notes, the console, huddle pages, module registry entries, platform audits, incident logs, and any member-facing internal page. Triggers on: "build a playbook", "write a briefing", "draft a report", "create a mock", "daily brief", "new internal page", "put this on the site", LESARUSS HQ, lesaruss.ai. Also triggers when a file path ends in .html inside a LESARUSS project folder. Never hand-write the nav, drawer, footer, CSS variables, or module icons. Copy the locked template file and edit only the main block. The same drift correction has already cost multiple round trips with Sean, this skill prevents the next.
|
LESARUSS Internal Page Template -- Pre-Flight Guardrail
Run this before writing any internal LESARUSS HTML file. The goal is
mechanical: the locked template already exists, already passes ADA, already
matches brand, and already carries the correct nav, drawer, footer, and icons.
Hand-written pages drift. Drift costs round trips. This skill prevents that.
STEP 0 -- Read the file. This is not optional. (Rule 2.10)
Before writing a single line of HTML, call the Read tool on
_templates/internal-page-LOCKED.html from the active LESARUSS workspace.
This is Rule 2.10: the locked template file on disk is the only valid source
for nav, drawer, top bar, footer, and CSS variables. Memory is not a valid
source. A prior session's output is not a valid source. The file is the source.
How to find it -- search in order:
-
Use Glob or Bash to locate it across connected workspace folders:
find /sessions/*/mnt -name "internal-page-LOCKED.html" 2>/dev/null | head -5
-
The canonical copy lives in the LESARUSS Project folder (local Mac, not
Google Drive). The Drive copy is a mirror; the local Project folder wins.
-
If two results differ, use the one mapped to:
/Users/seanrussell_1/Documents/Claude/Projects/LESARUSS Project/
If the file cannot be found: stop. Do not hand-write a replacement.
Ask Sean to verify the workspace is mounted before continuing.
Also read _templates/READ-ME-FIRST.md from the same folder. It contains
the drift log and pre-flight checklist. Read it every session.
1. Copy, do not rewrite
After reading the template (Step 0), copy internal-page-LOCKED.html to the
destination path using Bash or Write. Then:
- Edit only the content inside the main block marked EDIT BELOW.
- Swap the three module icons in .nav-right to match the page's modules.
Keep the SR avatar last.
- Set the title and meta description.
- Leave nav, drawer, footer, CSS variables, head scripts, and all --lr-*
values untouched.
If a reason to deviate surfaces, stop and ask Sean before continuing.
2. What is locked
Recap only. The template is canonical; this section is orientation.
- Top bar: LESARUSS.AI wordmark with pulsing dot on the left. On the right,
32px circle module icons plus the SR avatar. No horizontal nav links.
- Module icons: 32x32, border-radius 50%, bg --lr-surface2, border
--lr-border, 14px SVG at --lr-text-50, hover to --lr-orange-text.
- Left-edge drawer toggle: 26x64 orange rectangle, default closed, subtle
pulse every ~12 seconds.
- Left drawer links: Mission Control, Brand, Directory, Library, Playbooks,
Modules, Settings. Closes on scrim click, X, or Escape.
- Font: Montserrat via Google Fonts, weights 400, 600, 700, 800, 900.
- CSS variables: --lr-* prefix. Light-mode orange-text is #7d4a00 for ADA.
- Theme: white default. Dark is opt-in only (Rule 2.1). No auto time-of-day
switching -- strip any such JavaScript found in older copies.
- Footer: LESARUSS.AI mark, footer nav, copyright.
- main wrap: max-width 1100px, padding 110px 28px 80px.
3. Known drift incidents (do not repeat)
The drift log in READ-ME-FIRST.md is the authoritative record. Short list:
- Used a wrong page as reference and inherited the wrong nav.
- Used an older template with dark outer background plus viewport switcher.
- Kept horizontal nav links in top bar because a live page still had them.
- Used square module icons instead of 32px circles.
- Hand-wrote a standalone page, hit surface brand rules, mistook it for a
structural template issue.
- Reconstructed nav from working memory instead of reading the file. Looked
close but differed in CSS variable names and drawer structure. Required full
rebuild. (2026-05-06 -- this entry is why Rule 2.10 exists.)
Every entry cost a round trip. The point is that the next entry never gets
written.
4. Pre-write checklist
[ ] Read _templates/internal-page-LOCKED.html this session (Rule 2.10 Step 0)
[ ] Read _templates/READ-ME-FIRST.md this session
[ ] Destination path is a LESARUSS folder (Project, HQ, or lesaruss.ai repo)
[ ] Copying the template -- not constructing a new skeleton from memory
[ ] Editing only the main block
[ ] Module icons in .nav-right updated, SR avatar kept
[ ] title and meta description set
[ ] Nav, drawer, footer, CSS variables untouched
[ ] No em-dashes in any content (Rule 3.1)
[ ] Font is Montserrat loaded from Google Fonts (Rule 2.6)
[ ] If deviating from any of the above, Sean was asked first
5. If a page already exists and has drifted
Use relock.py in the canonical _templates/ folder:
python _templates/relock.py <path-to-drifted-page.html>
It rewraps the existing main content inside the locked template. Do not
try to hand-patch an already-drifted page.
6. ADA check before delivery
Run the ada-checker skill before delivering any page to Sean. The locked
template passes WCAG 2 AA structurally, but custom content inside main
can still introduce contrast, heading order, or ARIA failures. Do not skip.
7. Compact report after delivery
Page:
Template: internal-page-LOCKED.html (read from disk, structural surfaces unchanged)
Main block: edited
Module icons: SR
ADA:
Rule 2.10: satisfied
Do not narrate what is in the page. Sean can read it.
8. Universality note
This skill lives in the lesaruss-context GitHub repo under skills/. It is
fetched as part of the station-setup process and must be installed on every
station. Rule 2.10 in console/locked-rules.md is the canonical statement of
the requirement. This skill is the enforcement layer. Both must be present.