Skip to content
Skills Library
Programming · Testing

engineering-testing-performance-code-design

/engineering-testing-performance-code-design

Use when the user tests a web page in a real browser, speeds up slow code or pages, or wants help shaping the structure of a codebase.

Repository
studio-os ↗
Licence
MIT
Last repository change
10.11.2026

Assessment and security

81/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content16 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
7
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user tests a web page in a real browser, speeds up slow code or pages, or wants help shaping the structure of a codebase.

Original author description

Use when the user tests a web page in a real browser, speeds up slow code or pages, or wants help shaping the structure of a codebase.

How it works

SKILL.md has no level-two headings · 11 lines, 197 words

SKILL.md preview
---
name: engineering-testing-performance-code-design
description: Use when the user tests a web page in a real browser, speeds up slow code or pages, or wants help shaping the structure of a codebase.
---

# Engineering: browser testing, performance and code design

Find the skill that fits the task in the table, read its file in full before you start, and follow it. If a skill needs a local tool and you are on claude.ai without one, follow that skill's "Without local tools" section.

| Skill | What it does | When to use | File |
|---|---|---|---|
| Browser testing with devtools | Tests in real browsers via the Chrome DevTools MCP. | Use when building or debugging anything that runs in a browser (richicinschi-website, the OOP platform) — inspect the DOM, capture console errors, analyze network, run a Lighthouse audit, profile… | skills/browser-testing-with-devtools.md |
| Codebase design | Shared vocabulary for designing deep modules. | Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill (tdd… | skills/codebase-design.md |
| Performance optimization | Optimizes application performance — measure first, optimize only what matters. | Use when performance requirements exist, you suspect a regression, Core Web Vitals / load times need improvement, or profiling reveals a bottleneck. | skills/performance-optimization.md |
Files in this package (7)
  • SKILL.md 1 KB
  • SOURCE.md 1 KB
  • skills/browser-testing-with-devtools.md 11 KB
  • skills/codebase-design.md 6 KB
  • skills/performance-optimization.md 12 KB
  • skills/codebase-design/DEEPENING.md 2 KB
  • skills/codebase-design/DESIGN-IT-TWICE.md 3 KB

Versions

The database has no other skills named engineering-testing-performance-code-design.

Database snapshot: 13.11.2026 · package version 4eb4f021e151 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100qa
    QA testing skill with real browser automation. Use when asked to "test this site", "QA this page", "check for visual bugs", "verify the deploy", or when Hydra needs browser validation for UI changes. Requires the browse binary.
  • 100performance-optimization
    Make a slow web frontend faster — web vitals, bundle size, code splitting, chunking, render behaviour. Use when a page is slow, the bundle grew, or web vitals regressed. API throughput and latency belong to load-testing.
  • 100performance-optimization
    Make a slow web frontend faster — web vitals, bundle size, code splitting, chunking, render behaviour. Use when a page is slow, the bundle grew, or web vitals regressed. API throughput and latency belong to load-testing.
  • 90gstack-review
    Multi-layered review pipeline for code and design. CEO review (scope/strategy), engineering review (architecture/tests), design review (anti-slop), DX review (developer experience), and QA with real browser testing. Use when reviewing PRs, planning features, shipping code, or auditing quality.
  • 100browser-testing
    Use when building, debugging, or verifying browser-rendered code, or running browser tests for PR- or branch-affected pages. Not for source, remote-system, credential, publish, or deploy changes.
  • 85browser-journey-testing
    Exercise user journeys in a real browser and compare UI behavior and presentation with the agreed product and design expectations. Use for meaningful UI changes or requested end-to-end browser checks.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.