Svelte Testing
spences10/sveltest
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.
Mandatory testing conventions for TypeScript stacks (Vitest for CLI/SDK/Website/CDK).
$ npx skills add macalbert/envilder --skill typescript-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install macalbert/envilder typescript-testing --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/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/typescript-testing .claude/skills/typescript-testing && 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 "typescript-testing" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/typescript-testing into .claude/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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/macalbert/envilder/tree/main/.github/skills/typescript-testingType 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 macalbert/envilder --skill typescript-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install macalbert/envilder typescript-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/typescript-testing .agents/skills/typescript-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "typescript-testing" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/typescript-testing into .agents/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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 macalbert/envilder --skill typescript-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install macalbert/envilder typescript-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/typescript-testing .cursor/skills/typescript-testing && 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 "typescript-testing" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/typescript-testing into .cursor/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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/macalbert/envilder.git --path .github/skills/typescript-testing--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 macalbert/envilder --skill typescript-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install macalbert/envilder typescript-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/typescript-testing .gemini/skills/typescript-testing && 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 "typescript-testing" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/typescript-testing into .gemini/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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 macalbert/envilder typescript-testingInstalls 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 macalbert/envilder --skill typescript-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/typescript-testing .github/skills/typescript-testing && 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 "typescript-testing" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/typescript-testing into .github/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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 macalbert/envilder --skill typescript-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install macalbert/envilder typescript-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/typescript-testing .opencode/skills/typescript-testing && 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 "typescript-testing" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/typescript-testing into .opencode/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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.
typescript-testingMandatory testing conventions for TypeScript stacks (Vitest for CLI/SDK/Website/CDK).
Typescript Testing is an agent skill from macalbert/envilder. Mandatory testing conventions for TypeScript stacks (Vitest for CLI/SDK/Website/CDK). Use for unit, integration, or E2E tests with Vitest or Playwright.
Its SKILL.md is about 2.2k 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, covering Unit testing and End-to-end testing. It works with TypeScript, Vitest, Playwright and Node.js. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
pnpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Typescript Testing loads about 2.2k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 550 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.
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.
The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 550 words, ~2,188 tokens.
.claude/skills/typescript-testing/SKILL.md (or your agent's skills folder).This skill defines the MANDATORY testing conventions for TypeScript projects. These are rules, not guidelines.
// Arrange, // Act, // Assert comments are allowed in testsShould_X_When_Y already documents the intentException: SDK public API: Code under src/sdks/*/ consumed by
external developers (facade classes, public entry points) SHOULD have
JSDoc with usage examples. This exception does not apply to tests or
internal helpers.
| Stack | Test Runner | Location |
|---|---|---|
| CLI / Core | Vitest | tests/envilder/ |
| Node.js SDK | Vitest | tests/sdks/nodejs/ |
| Website | Vitest | tests/website/ |
| CDK (IaC) | Vitest | tests/iac/ |
| E2E | Vitest + TestContainers | e2e/ |
ALL tests MUST follow the AAA pattern, separated by inline comments.
// Arrange, // Act, // Assert) appears AT MOST ONCE
per test: if you need two actions or two asserts, write two testsexpect() in Arrange or Act.
If you feel tempted to assert in Arrange (precondition check), extract it to
a separate test or use a guard clause that throws: not an assertion.if, switch, or conditional logic inside Arrange, Act, or Asserttry/catch/finally inside tests: use beforeEach/afterEach for
teardown// Act & Assert combined blocks: Act and Assert are ALWAYS separateexpect(() => action()).toThrow() or
await expect(asyncAction()).rejects.toThrow()it('Should_GenerateEnvFile_When_ValidParametersProvided', async () => {
// Arrange
mockStore.getMapping.mockResolvedValue({ KEY: '/ssm/path' });
mockProvider.getSecret.mockResolvedValue('value');
// Act
await sut.handle(command);
// Assert
expect(mockStore.saveEnvironment).toHaveBeenCalled();
});Test names MUST follow exactly:
Should_{ExpectedBehavior}_When_{Condition}it() descriptionsShould_Work, TestHandler)When clause| Test Name | Scenario |
|---|---|
Should_ThrowError_When_SSMParameterIsNotFound | Error path |
Should_ReturnMaskedValue_When_SecretIsLoaded | Success path |
Should_ReturnEmptyMap_When_NoMappingsExist | Edge case |
| Purpose | Name |
|---|---|
| Subject under test | sut |
| Expected value | expected |
| Actual result | actual |
No creativity allowed here.
const mockProvider: ISecretProvider = {
getSecret: vi.fn(),
};
const mockStore: IVariableStore = {
getMapping: vi.fn(),
saveEnvironment: vi.fn(),
};
const mockLogger: ILogger = {
info: vi.fn(),
warn: vi.fn(),
error: vi.fn(),
};vi.mocked(mockProvider.getSecret).mockResolvedValue('secret-value');
vi.mocked(mockProvider.getSecret).mockRejectedValue(new Error('not found'));
vi.mocked(mockStore.getMapping).mockResolvedValue({ KEY: '/path' });expect(mockProvider.getSecret).toHaveBeenCalledWith('/ssm/path');
expect(mockProvider.getSecret).toHaveBeenCalledTimes(1);
expect(mockLogger.info).toHaveBeenCalledWith(expect.stringContaining('success'));Act and Assert MUST be separate. Wrap the action in Act, assert in Assert.
it('Should_ThrowInvalidArgument_When_ProviderIsUnsupported', () => {
// Arrange
const config = { provider: 'unsupported' };
// Act
const act = () => createProvider(config);
// Assert
expect(act).toThrow(InvalidArgumentError);
});it('Should_ThrowParameterNotFound_When_SSMKeyIsMissing', async () => {
// Arrange
mockProvider.getSecret.mockRejectedValue(new ParameterNotFoundError('/missing'));
// Act
const act = sut.handle(command);
// Assert
await expect(act).rejects.toThrow(ParameterNotFoundError);
});it('Should_ThrowError_When_Invalid', () => {
// Act & Assert ← NEVER DO THIS
expect(() => sut.handle(bad)).toThrow();
});describe('PullSecretsToEnvCommandHandler', () => {
let sut: PullSecretsToEnvCommandHandler;
let mockStore: { getMapping: Mock; saveEnvironment: Mock };
let mockProvider: { getSecret: Mock };
let mockLogger: { info: Mock; warn: Mock; error: Mock };
beforeEach(() => {
mockStore = { getMapping: vi.fn(), saveEnvironment: vi.fn() };
mockProvider = { getSecret: vi.fn() };
mockLogger = { info: vi.fn(), warn: vi.fn(), error: vi.fn() };
sut = new PullSecretsToEnvCommandHandler(
mockProvider,
mockStore,
mockLogger,
);
});
it('Should_GenerateEnvFile_When_ValidParametersProvided', async () => {
// Arrange
mockStore.getMapping.mockResolvedValue({ KEY: '/ssm/path' });
mockProvider.getSecret.mockResolvedValue('value');
// Act
await sut.handle(command);
// Assert
expect(mockStore.saveEnvironment).toHaveBeenCalled();
});
});describe('EnvilderClient', () => {
it('Should_ResolveSecrets_When_ProviderReturnsValues', async () => {
// Arrange
const mockProvider: ISecretProvider = {
getSecrets: vi.fn().mockResolvedValue(new Map([['KEY', 'value']])),
};
const sut = new EnvilderClient(mockProvider);
// Act
const actual = await sut.resolveSecrets(parsedMapFile);
// Assert
expect(actual.get('KEY')).toBe('value');
});
});describe('AppStack', () => {
it('Should_CreateLambda_When_StackSynthesized', () => {
// Arrange
const app = new cdk.App();
const stack = new AppStack(app, 'TestStack');
// Act
const actual = Template.fromStack(stack);
// Assert
actual.hasResourceProperties('AWS::Lambda::Function', {
Runtime: 'nodejs22.x',
Handler: 'index.handler',
});
});
});Tests that validate static data (i18n completeness, schema conformance,
version consistency) still MUST use AAA markers. Arrange can be omitted
if data is set up at the describe level:
it('Should_HaveNoMissingKeys_When_CatalanComparedToEnglish', () => {
// Act
const actual = enKeys.filter((k) => !caKeys.includes(k));
// Assert
expect(actual, 'Keys missing in ca.ts').toEqual([]);
});| Context | Command |
|---|---|
| CLI / Core / Website | pnpm test |
| Node.js SDK | cd tests/sdks/nodejs && pnpm vitest run --reporter=verbose |
| CDK | cd tests/iac && pnpm test |
| CI parity | pnpm test:ci |
| Lint | pnpm lint |
| Format | pnpm format |
vi.fn()Should_<Expected>_When_<Condition>sut, actual, expected used consistentlypnpm testpnpm lint© macalbert, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .github/skills/typescript-testing of macalbert/envilder.
Open the folder on GitHubat commit b6a0327
Typescript Testing 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 |
|---|---|---|---|---|---|---|
| Typescript Testing this skillmacalbert/envilder | 138 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Svelte Testingspences10/sveltest | 113 | — | ~579 | Automated safety check: Pass | MIT | |
| Ha Frontend Testinghome-assistant/frontend | 5.7k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Frontend Typescript Testingshinpr/ai-coding-project-boilerplate | 232 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Test CommanderEliasOulkadi/shokunin | 114 | — | ~3k | Automated safety check: Notes | MIT | |
| Testing Patternssoftspark/ai-toolkit | 179 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
spences10/sveltest
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.
home-assistant/frontend
Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.
shinpr/ai-coding-project-boilerplate
Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest, and Playwright when present.
EliasOulkadi/shokunin
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).
softspark/ai-toolkit
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage.
shinpr/ai-coding-project-boilerplate
リポジトリで設定済みのReactテスト・ブラウザハーネスを使用してフロントエンドテストを設計。RTL、MSW、Vitest、Playwrightが存在する場合に適用。コンポーネント、loading/error state、統合、フロントエンドE2Eテストの追加・レビュー時に使用。
macalbert/envilder
Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.
macalbert/envilder
Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions.
macalbert/envilder
Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.
macalbert/envilder
Mandatory testing conventions including the narrow diagnostic exception for testing test-only code, AAA pattern, test naming, and assertions across all stacks (.NET, TypeScript, Python).
macalbert/envilder
Workflow for maintaining changelogs, READMEs, and documentation files.
macalbert/envilder
Audit and synchronize documentation across website, READMEs, and docs/.
Works with
Categories
Mandatory testing conventions for TypeScript stacks (Vitest for CLI/SDK/Website/CDK). Typescript Testing is an agent skill from macalbert/envilder. Mandatory testing conventions for TypeScript stacks (Vitest for CLI/SDK/Website/CDK).
Typescript Testing fits situations like: E2E tests with Vitest; tasks that involve Unit testing; tasks that involve End-to-end testing.
Run `npx skills add macalbert/envilder --skill typescript-testing -a claude-code`. Or copy the skill folder (.github/skills/typescript-testing in macalbert/envilder) into .claude/skills/typescript-testing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add macalbert/envilder --skill typescript-testing -a codex`. Or copy the skill folder (.github/skills/typescript-testing in macalbert/envilder) into .agents/skills/typescript-testing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add macalbert/envilder --skill typescript-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/typescript-testing, .gemini/skills/typescript-testing, .github/skills/typescript-testing and .opencode/skills/typescript-testing in your project.
Going by SKILL.md and its folder, Typescript Testing needs the command-line tools its instructions call (pnpm). Our summary lists: Node.js.
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.
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.
Typescript Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Typescript Testing: Svelte Testing (spences10/sveltest, 113 stars), Ha Frontend Testing (home-assistant/frontend, 5.7k stars), Frontend Typescript Testing (shinpr/ai-coding-project-boilerplate, 232 stars) and Test Commander (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.
Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.