Testing OpenLogi UI
AprilNEA/OpenLogi
Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.
A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices.
Install Mock Best Practices
$ npx skills add thedaviddias/Front-End-Checklist --skill mock-best-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist mock-best-practices --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/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mock-best-practices .claude/skills/mock-best-practices && 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 "mock-best-practices" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/mock-best-practices into .claude/skills/mock-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mock-best-practices", 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/thedaviddias/Front-End-Checklist/tree/main/skills/mock-best-practicesType 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 thedaviddias/Front-End-Checklist --skill mock-best-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist mock-best-practices --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/mock-best-practices .agents/skills/mock-best-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mock-best-practices" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/mock-best-practices into .agents/skills/mock-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mock-best-practices", 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 thedaviddias/Front-End-Checklist --skill mock-best-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist mock-best-practices --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/mock-best-practices .cursor/skills/mock-best-practices && 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 "mock-best-practices" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/mock-best-practices into .cursor/skills/mock-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mock-best-practices", 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/thedaviddias/Front-End-Checklist.git --path skills/mock-best-practices--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 thedaviddias/Front-End-Checklist --skill mock-best-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist mock-best-practices --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/mock-best-practices .gemini/skills/mock-best-practices && 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 "mock-best-practices" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/mock-best-practices into .gemini/skills/mock-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mock-best-practices", 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 thedaviddias/Front-End-Checklist mock-best-practicesInstalls 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 thedaviddias/Front-End-Checklist --skill mock-best-practices -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/mock-best-practices .github/skills/mock-best-practices && 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 "mock-best-practices" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/mock-best-practices into .github/skills/mock-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mock-best-practices", 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 thedaviddias/Front-End-Checklist --skill mock-best-practices -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist mock-best-practices --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/mock-best-practices .opencode/skills/mock-best-practices && 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 "mock-best-practices" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/mock-best-practices into .opencode/skills/mock-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mock-best-practices", 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
mock-best-practices- GitHub stars
- 74k
- Token cost
- ~425 tokens
- SKILL.md length
- 160 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices.
- Reviewing CI coverage
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Automated checks
What it does
Mock Best Practices is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices. Focus on whether the rule is continuously verified, not just documented.
Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Testing & QA, covering Test strategy. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Reviewing CI coverage
- Automated checks
- Test strategy related to Follow mocking best practices
Example prompts
- “/mock-best-practices”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
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
Mock Best Practices loads about 425 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 160 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 thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 160 words, ~425 tokens.
Download SKILL.mdSave it as
.claude/skills/mock-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- mock-best-practices
- description
- Use when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices. Focus on whether the rule is continuously verified, not just documented.
- metadata.category
- testing
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 20
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/testing/mock-best-practices
Follow mocking best practices
Proper mocking isolates units under test while keeping tests realistic—over-mocking creates false confidence when tests pass but production breaks.
Quick Reference
- Mock external dependencies (APIs, databases, file system), not business logic
- Always clean up mocks with jest.restoreAllMocks() in afterEach
- Use MSW for realistic API mocking without coupling to implementation
- Test behavior and outputs, not internal implementation details
Check
Review this test file for mocking patterns, checking for over-mocking, missing mock cleanup, and proper mock implementation.
Fix
Improve mocking strategy by removing unnecessary mocks, adding proper cleanup, and mocking at the right level of abstraction.
Explain
Explain mocking best practices including when to mock, what to mock, and common mocking pitfalls.
Code Review
Review tests, CI workflows, and enforcement points related to Follow mocking best practices. Flag exact gaps where the rule is not automatically verified or where failures do not block regressions.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/testing/mock-best-practices
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/mock-best-practices of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Mock Best Practices 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 |
|---|---|---|---|---|---|---|
| Mock Best Practices this skillthedaviddias/Front-End-Checklist | 74k | — | ~425 | Automated safety check: Pass | MIT | |
| Testing OpenLogi UIAprilNEA/OpenLogi | 23k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Testing Hashqlhashintel/hash | 1.7k | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| Dynamo Unit TestingDynamoDS/Dynamo | 2k | — | ~622 | Automated safety check: Pass | Apache-2.0 | |
| Bmad Testarch Test Designbmad-code-org/bmad-method-test-architecture-enterprise | 105 | 3 repos | ~1.4k | Automated safety check: Pass | Custom licence | |
| Test RoadmapOvid/paad | 131 | — | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
Testing Hashql
hashintel/hash
HashQL testing strategies including compiletest (UI tests), unit tests, and snapshot tests.
Dynamo Unit Testing
DynamoDS/Dynamo
Write comprehensive NUnit tests for the Dynamo codebase following Dynamo testing patterns, conventions, and architectural constraints.
Bmad Testarch Test Design
bmad-code-org/bmad-method-test-architecture-enterprise
Create system-level or epic-level test plans. An agent skill from bmad-code-org/bmad-method-test-architecture-enterprise.
Test Roadmap
Ovid/paad
Analyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes…
Designing Tests
CloudAI-X/opencode-workflow
Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Mock Best Practices
What does Mock Best Practices do?
A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices. Mock Best Practices is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices.
When should I use Mock Best Practices?
Mock Best Practices fits situations like: reviewing CI coverage; automated checks; test strategy related to Follow mocking best practices.
How do I install Mock Best Practices in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill mock-best-practices -a claude-code`. Or copy the skill folder (skills/mock-best-practices in thedaviddias/Front-End-Checklist) into .claude/skills/mock-best-practices in your project. Claude Code loads it when a task matches its description.
How do I install Mock Best Practices in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill mock-best-practices -a codex`. Or copy the skill folder (skills/mock-best-practices in thedaviddias/Front-End-Checklist) into .agents/skills/mock-best-practices in your project. Codex loads it when a task matches its description.
Can I use Mock Best Practices 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 thedaviddias/Front-End-Checklist --skill mock-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mock-best-practices, .gemini/skills/mock-best-practices, .github/skills/mock-best-practices and .opencode/skills/mock-best-practices in your project.
What does Mock Best Practices need to run?
SKILL.md names no scripts, command-line tools or credentials: Mock Best Practices is instructions for the agent only.
Does Mock Best Practices access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Mock Best Practices 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 Mock Best Practices use?
Mock Best Practices 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 Mock Best Practices use?
About 425 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 998 tokens, read only when the agent opens those files.
What are the alternatives to Mock Best Practices?
Skills that share tags, products or a category with Mock Best Practices: Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars), Testing Hashql (hashintel/hash, 1.7k stars), Dynamo Unit Testing (DynamoDS/Dynamo, 2k stars) and Bmad Testarch Test Design (bmad-code-org/bmad-method-test-architecture-enterprise, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mock Best Practices?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.