Skip to content
TrustedSkillsbeta
Back to all skills

Type Vs Interface

Checked
marius-townhouse·vlatest·backend

This skill generates code snippets for specific Visual Studio versions, streamlining development and ensuring compatibility across different environments.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add marius-townhouse/effective-typescript-skills --skill type-vs-interface -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

marius-townhouse

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned marius-townhouse/effective-typescript-skills at d754db2077.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d754db2077
Manifest
skills/type-vs-interface/SKILL.md
Scanned
1 file, 290 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps distinguish between TypeScript's type and interface constructs, explaining their subtle differences and when to prefer one over the other. It clarifies that while they often achieve similar results, there are nuanced behavioral distinctions related to declaration merging and intersection types. The skill aims to provide a practical understanding for writing more precise and maintainable TypeScript code.

When to use it

  • When encountering conflicting advice on whether to use type or interface.
  • During code reviews where the choice between type and interface is unclear.
  • For developers new to TypeScript who want a deeper understanding of these core concepts.
  • To optimize existing TypeScript code for clarity and maintainability by choosing the right construct.

Key capabilities

  • Explains declaration merging behavior with types.
  • Details how intersection types work with types.
  • Clarifies differences in usage scenarios between type and interface.
  • Provides guidance on when to use each construct for optimal code clarity.

Example prompts

  • "Explain the difference between a TypeScript type alias and an interface."
  • "When should I prefer using a 'type' over an 'interface' in my TypeScript code?"
  • "How does declaration merging work with type aliases?"

Tips & gotchas

The skill assumes basic familiarity with TypeScript syntax. While type and interface are often interchangeable, understanding their subtle differences is crucial for advanced TypeScript usage and avoiding unexpected behavior.