Component Library Contracts logo

Component Library Contracts

Community
Sahil-SS9
component-library-contracts

Specify components with states, accessibility contracts and documented APIs.

Overview

PublisherSahil-SS9
Repositoryagent-personas
Skill namecomponent-library-contracts
Stars
67
Forks
4
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Sahil-SS9 on GitHub. Read the source before you install it.

Installation

Install the Component Library Contracts AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Sahil-SS9/agent-personas/tree/main/skills/component-library-contracts
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Sahil-SS9/agent-personas.git /tmp/agent-personas
mkdir -p .claude/skills
cp -r /tmp/agent-personas/skills/component-library-contracts .claude/skills/component-library-contracts
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Component Library Contracts in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Component Library Contracts on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Component Library Contracts is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Component library contracts

When to use

Adding or changing any shared component.

Procedure

  1. Every component owns a written contract: purpose, when-to-use/when-not, props/slots API, and full state coverage (default/hover/focus/disabled/error/loading/empty).
  2. Accessibility is part of the contract: name/role/value semantics, keyboard interaction pattern, focus management, minimum target size.
  3. Composition over configuration: split components when props multiply; a 30-prop component is a failed decomposition.
  4. Version with semver; breaking changes carry migration guides and deprecation timelines.
  5. Live documented examples with copy-paste code; undocumented components don't exist.

Decision rules

  • Duplicates get consolidated: two similar components is a pending decision, not a pattern.
  • Component changes need visual regression evidence (before/after across states).
  • New components serve ≥2 real use cases before entering the library.

Pitfalls

  • Copy-paste fork instead of extending the library.
  • State coverage discovered by consumers at integration time.

Done

Documented, versioned, state-complete components with a11y contracts and live examples.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Component Library Contracts AI skill do?

Specify components with states, accessibility contracts and documented APIs.

Why use Component Library Contracts on TypingMind?

Because you install it once and use it with any model. Component Library Contracts is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Component Library Contracts in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Sahil-SS9/agent-personas/tree/main/skills/component-library-contracts. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Component Library Contracts?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Component Library Contracts?

As many as you like. As long as a model supports skills, you can use Component Library Contracts with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Component Library Contracts AI skill free?

Yes. It is published on GitHub by Sahil-SS9 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇