Uses the right location first, then checks forecast data and summarizes it in plain language.

It was created after a location mismatch, so future weather answers stay grounded to Fort Gordon or the location you give.

The workflow had a repeatable correction: confirm the location, fetch the forecast, then summarize without guessing.

Guides changes to Hermes itself, including config, tools, memory, voice, and integrations.

Hermes has many systems. This skill prevents guessing when changing the assistant’s actual setup.

Configuration work needs the correct commands and safe handling of existing systems.

Creates quick interface prototypes with real HTML, CSS, and basic interactions.

Visual ideas are easier to judge when you can click around instead of only reading descriptions.

Your app idea needs fast iteration before we make the backend real.

Could compare repair costs, resale value, financing, rental income, and risk on potential properties.

This is a planned skill area because your long-term goal is buying, fixing, and selling homes.

It connects directly to your future path, not just your current 25H training.

Looks up current market data and explains price movement using company fundamentals, recent news, IPO context, and investor risk.

It came from the REA stock research conversation where the deeper answer required separating hype from the company’s current business reality.

Stock questions need fresh sources and grounded reasoning instead of guessing from memory or only repeating the latest price.

Keeps the frontend chat state usable before the AI backend exists: creates new chats, sends user messages, and updates prompt totals.

The mockup looked real but the New chat and Send controls did not actually do anything yet.

A shell should still behave like an app. It needs working local interactions even before connecting to Hermes.

Uses one open skill card at a time, hidden dropdown state, aria-expanded tracking, and grid alignment that prevents sibling cards from stretching.

The Skills page originally made it look like every skill dropped down when only one was clicked.

This is a repeatable UI bug pattern: the JavaScript state and CSS grid layout both have to be checked.

Tracks stable preferences like your Jarvis-inspired assistant style, code folder location, Fort Gordon context, and long-term real estate goals.

You want this assistant to remember useful context and adapt over time instead of acting like every session starts from zero.

The app should show not just tools, but also the wants and corrections that shape how Jarvis works for you.