Test Writing Workflow
iOfficeAI/AionUi
Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.
Workflows for developing, building, bundling, and testing the TypeScript / Lit Lovelace dashboard strategy in lovelacestrategy/.
Install Lovelace Strategy
$ npx skills add FutureTense/keymaster --skill lovelace-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FutureTense/keymaster lovelace-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FutureTense/keymaster.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/lovelace-strategy .claude/skills/lovelace-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lovelace-strategy" agent skill from https://github.com/FutureTense/keymaster/tree/main/.agents/skills/lovelace-strategy into .claude/skills/lovelace-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lovelace-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FutureTense/keymaster/tree/main/.agents/skills/lovelace-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FutureTense/keymaster --skill lovelace-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FutureTense/keymaster lovelace-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FutureTense/keymaster.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/lovelace-strategy .agents/skills/lovelace-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lovelace-strategy" agent skill from https://github.com/FutureTense/keymaster/tree/main/.agents/skills/lovelace-strategy into .agents/skills/lovelace-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lovelace-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FutureTense/keymaster --skill lovelace-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FutureTense/keymaster lovelace-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FutureTense/keymaster.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/lovelace-strategy .cursor/skills/lovelace-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lovelace-strategy" agent skill from https://github.com/FutureTense/keymaster/tree/main/.agents/skills/lovelace-strategy into .cursor/skills/lovelace-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lovelace-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FutureTense/keymaster.git --path .agents/skills/lovelace-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FutureTense/keymaster --skill lovelace-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FutureTense/keymaster lovelace-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FutureTense/keymaster.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/lovelace-strategy .gemini/skills/lovelace-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lovelace-strategy" agent skill from https://github.com/FutureTense/keymaster/tree/main/.agents/skills/lovelace-strategy into .gemini/skills/lovelace-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lovelace-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FutureTense/keymaster lovelace-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FutureTense/keymaster --skill lovelace-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FutureTense/keymaster.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/lovelace-strategy .github/skills/lovelace-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lovelace-strategy" agent skill from https://github.com/FutureTense/keymaster/tree/main/.agents/skills/lovelace-strategy into .github/skills/lovelace-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lovelace-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FutureTense/keymaster --skill lovelace-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FutureTense/keymaster lovelace-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FutureTense/keymaster.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/lovelace-strategy .opencode/skills/lovelace-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lovelace-strategy" agent skill from https://github.com/FutureTense/keymaster/tree/main/.agents/skills/lovelace-strategy into .opencode/skills/lovelace-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lovelace-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lovelace-strategy- GitHub stars
- 349
- Token cost
- ~345 tokens
- SKILL.md length
- 93 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Workflows for developing, building, bundling, and testing the TypeScript / Lit Lovelace dashboard strategy in lovelacestrategy/.
- Works in 3 steps: Run yarn test to verify Vitest unit specs. → Build the bundle with yarn build. → If applicable, run Python strategy…
- Testing & QA work in your project
- SKILL.md covers Directory Layout & Assets, Commands and Testing Dashboard Generation
- Calls yarn and python3
What it does
Lovelace Strategy is an agent skill from FutureTense/keymaster. Workflows for developing, building, bundling, and testing the TypeScript / Lit Lovelace dashboard strategy in lovelacestrategy/.
Its SKILL.md is about 350 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA. It works with TypeScript and Vitest. The repository describes itself as: Home Assistant integration for managing Z-Wave enabled locks. The licence is MIT.
When your agent uses it
- Testing & QA work in your project
Example prompts
- “Use the lovelace-strategy skill to workflow for developing, building, bundling, and testing the TypeScript / Lit Lovelace dashboard strategy in…”
- “/lovelace-strategy”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Run yarn test to verify Vitest unit specs.
- Build the bundle with yarn build.
- If applicable, run Python strategy comparison
What it can do on your machine
Read from SKILL.md and the folder at commit d94ffb2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
yarnpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use yarn, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Lovelace Strategy loads about 345 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 93 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from FutureTense/keymaster at commit d94ffb2, republished under its MIT licence (© FutureTense). 93 words, ~345 tokens.
Download SKILL.mdSave it as
.claude/skills/lovelace-strategy/SKILL.md (or your agent's skills folder).- name
- lovelace-strategy
- description
- Workflows for developing, building, bundling, and testing the TypeScript / Lit Lovelace dashboard strategy in lovelace_strategy/.
Keymaster Lovelace Strategy Development Guide
This skill guides development on the TypeScript/Lit custom strategy located in
lovelace_strategy/.
Directory Layout & Assets
lovelace_strategy/: TypeScript source files for the Lovelace strategy.custom_components/keymaster/www/: Destination directory for built JavaScript bundle distribution.vitest.config.ts: Vitest test runner configuration.rollup.config.js: Rollup bundling configuration.scripts/compare_lovelace_output.py: Verifies generated Lovelace dashboard views.
Commands
All frontend operations should be executed via yarn:
# Install dependencies
yarn install
# Run build / Rollup compilation
yarn build
# Run unit tests using Vitest
yarn test
# Run tests with coverage
yarn test:coverage
# Run ESLint on TypeScript files
yarn lint
# Auto-fix ESLint formatting/lint issues
yarn lint:fixTesting Dashboard Generation
When altering card definitions or view strategies:
Run
yarn testto verify Vitest unit specs.Build the bundle with
yarn build.If applicable, run Python strategy comparison:
bash python3 scripts/compare_lovelace_output.py
© FutureTense, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/lovelace-strategy of FutureTense/keymaster.
Open the folder on GitHubat commit d94ffb2
Compare with similar skills
Lovelace Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lovelace Strategy this skillFutureTense/keymaster | 349 | — | ~345 | Automated safety check: Pass | MIT | |
| Test Writing WorkflowiOfficeAI/AionUi | 33k | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Creating A Packagec15t/c15t | 1.9k | — | ~913 | Automated safety check: Pass | Apache-2.0 | |
| Svelte Testingspences10/sveltest | 113 | — | ~579 | Automated safety check: Pass | MIT | |
| Effect TStellahq/opensession | 392 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Ha Frontend Testinghome-assistant/frontend | 5.7k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Creating A Package
c15t/c15t
Scaffold a new workspace package in the c15t monorepo. An agent skill from c15t/c15t.
Svelte Testing
spences10/sveltest
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.
Effect TS
tellahq/opensession
Write idiomatic Effect v4 TypeScript verified against the pinned effect@4.0.0-rc.112 source.
Ha Frontend Testing
home-assistant/frontend
Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.
Eslint Vitest Rule Tester
antfu-collective/eslint-vitest-rule-tester
Help users test ESLint rules with Vitest, supporting snapshot testing and custom assertions
More from FutureTense/keymaster
Ha Code Quality
FutureTense/keymaster
Standards and commands for linting, code formatting, typing validation (Ruff, MyPy, Codespell, ESLint, Pre-commit/Prek, Tox), and adherence to Home Assistant Python 3.14 standards in Keymaster.
Ha Integration Testing
FutureTense/keymaster
Workflows, conventions, and commands for writing and running async Home Assistant unit and integration tests using pytest, tox, pytest-homeassistant-custom-component, and coverage tools.
Ha Lock Provider
FutureTense/keymaster
Guide for developing, testing, and maintaining lock platform providers (e.g., zwavejs, zigbee2mqtt, zha, schlage, akuvox) implementing BaseLockProvider in Keymaster.
Patch Coverage
FutureTense/keymaster
Procedure and guidelines for verifying and maintaining 100% patch test coverage on all modified and added lines across Keymaster PRs and branches.
Submit PR
FutureTense/keymaster
Procedure for preparing and submitting pull requests in keymaster, enforcing the required PR template (.github/PULLREQUESTTEMPLATE.md), checklist validation, and quality gates.
Coordinator Lifecycle
FutureTense/keymaster
Architectural patterns and lifecycle instructions for KeymasterCoordinator, KeymasterLockCoordinator, fan-out notification architecture, child entity platforms, and storage migrations.
Related
Works with
Categories
Questions about Lovelace Strategy
What does Lovelace Strategy do?
Workflows for developing, building, bundling, and testing the TypeScript / Lit Lovelace dashboard strategy in lovelacestrategy/. Lovelace Strategy is an agent skill from FutureTense/keymaster. Workflows for developing, building, bundling, and testing the TypeScript / Lit Lovelace dashboard strategy in lovelacestrategy/.
When should I use Lovelace Strategy?
Lovelace Strategy fits situations like: testing & QA work in your project.
How do I install Lovelace Strategy in Claude Code?
Run `npx skills add FutureTense/keymaster --skill lovelace-strategy -a claude-code`. Or copy the skill folder (.agents/skills/lovelace-strategy in FutureTense/keymaster) into .claude/skills/lovelace-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Lovelace Strategy in Codex?
Run `npx skills add FutureTense/keymaster --skill lovelace-strategy -a codex`. Or copy the skill folder (.agents/skills/lovelace-strategy in FutureTense/keymaster) into .agents/skills/lovelace-strategy in your project. Codex loads it when a task matches its description.
Can I use Lovelace Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FutureTense/keymaster --skill lovelace-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lovelace-strategy, .gemini/skills/lovelace-strategy, .github/skills/lovelace-strategy and .opencode/skills/lovelace-strategy in your project.
What does Lovelace Strategy need to run?
Going by SKILL.md and its folder, Lovelace Strategy needs the command-line tools its instructions call (yarn and python3). Our summary lists: Python 3.
Does Lovelace Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Lovelace Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lovelace Strategy use?
Lovelace Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lovelace Strategy use?
About 345 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Lovelace Strategy?
Skills that share tags, products or a category with Lovelace Strategy: Test Writing Workflow (iOfficeAI/AionUi, 33k stars), Creating A Package (c15t/c15t, 1.9k stars), Svelte Testing (spences10/sveltest, 113 stars) and Effect TS (tellahq/opensession, 392 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lovelace Strategy?
FutureTense (a GitHub user) maintains it in FutureTense/keymaster, which has 349 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: FutureTense/keymaster on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.