
Tedi Angular Contributing
- 1 repo stars
- Updated May 14, 2026
- TEDI-Design-System/ai-skills
Helps with design & ui/ux tasks.
About
tedi-angular-contributing is a Claude Code skill for design & ui/ux. It helps developers move faster with AI-assisted coding.
- tedi-angular-contributing
- Design & UI/UX
- AI-coding skill
Tedi Angular Contributing by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add TEDI-Design-System/ai-skills/plugin install tedi-angular-contributing@tediAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | May 14, 2026 |
| Repository | TEDI-Design-System/ai-skills ↗ |
What it does
Helps with design & ui/ux tasks.
README.md
TEDI AI skills
AI assistant skills for contributing to the TEDI Design System. This repo is a Claude Code plugin marketplace so contributors can install the skills with two commands; the same skill files also work with other AI tooling (instructions below).
Looking for skills to use TEDI in your own app? This repo is only for contributing to the TEDI codebase. The consumer-facing integration skills (for building apps that consume
@tedi-design-system/reactor@tedi-design-system/angular) ship inside the implementation repos themselves:
TEDI-Design-System/react→skills/tedi-react/TEDI-Design-System/angular→skills/tedi-angular/Install those from there, not from here.
What's in the box
Two plugins, one per framework:
| Plugin | Skill | What it does |
|---|---|---|
tedi-react-contributing |
contributing |
Guides creating, refactoring, testing, and a11y-auditing components in TEDI-Design-System/react. Bundles a post-edit hook that auto-runs the matching Jest spec. |
tedi-angular-contributing |
contributing |
Same workflow for TEDI-Design-System/angular, with an Angular-aware post-edit hook. |
Prerequisite: sibling working repos
The skills themselves don't need to live anywhere specific — the marketplace install handles that, and manual installs can live anywhere on disk. But the working TEDI repos (the ones you're contributing to) reference each other with relative paths: the React contributor skill peeks at ../angular/ and ../core/ for behavioral parity and design tokens, and the Angular skill mirrors that. For those references to resolve, the TEDI implementation repos must sit side-by-side:
your-workspace/
├── react/ # TEDI-Design-System/react
├── angular/ # TEDI-Design-System/angular
└── core/ # TEDI-Design-System/core (design tokens)
mkdir tedi && cd tedi
git clone https://github.com/TEDI-Design-System/react.git
git clone https://github.com/TEDI-Design-System/angular.git
git clone https://github.com/TEDI-Design-System/core.git
If you only ever work on one framework you can skip the others, but cross-references in the skill will surface as "not found" notes.
Install for Claude Code (primary path)
/plugin marketplace add TEDI-Design-System/ai-skills
/plugin install tedi-react-contributing@tedi
/plugin install tedi-angular-contributing@tedi
Then invoke from inside the relevant repo:
/tedi-react-contributing:contributing add a new Button variant per the Figma frame
The post-edit hook activates automatically — when you edit a file under src/tedi/ (React) or tedi/ (Angular), the matching spec runs.
See docs/install-claude-code.md for details, local-dev install, and uninstall.
Install for other tools
The SKILL.md format (Markdown body + YAML frontmatter) is portable across these tools; only the discovery mechanism differs.
Repo layout
ai-skills/
├── .claude-plugin/marketplace.json # marketplace manifest
├── plugins/
│ ├── tedi-react-contributing/
│ │ ├── .claude-plugin/plugin.json
│ │ ├── skills/contributing/ # SKILL.md + references/
│ │ └── hooks/ # hooks.json + post-edit-test.sh
│ └── tedi-angular-contributing/ # (mirror)
├── docs/ # per-tool install guides
├── LICENSE
└── README.md
Contributing to the skills
Skills are plain Markdown files with YAML frontmatter. Edit plugins/<plugin>/skills/contributing/SKILL.md or any file under references/. Validate with:
claude plugin validate .
Then update the marketplace cache locally to pick up your changes:
claude plugin marketplace update tedi
License
MIT — see LICENSE.