Tedydev-web

Tedy Kit — Design skill for Claude Code

Design community

A Claude Code plugin (tedy) for pull request review, development and project management that keeps every write behind a draft the user approves.

How to install Tedy Kit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Tedydev-web/tedy-kit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Tedy Kit does

A Claude Code plugin (`tedy`) for pull request review, development and project management that keeps every write behind a draft the user approves. It reconciles a scope across the PRD, the design, the

Alternatives in Design

README

tedy-kit engine

A Claude Code plugin (`tedy`) for pull request review, development and project management that keeps every write behind a draft the user approves. It reconciles a scope across the PRD, the design, the backend, the contract and the frontend; drafts review comments, tracker items and Doc or Figma comments in the user's style and language; and adds hooks that stop the agent from publishing, pushing to an integration branch or crossing into another role's work without asking.

The plugin holds no personal or project data. Everything that belongs to one user (rules, writing samples, project maps, gate switches) lives in their profile directory, which the plugin reads.

Requirements

  • Claude Code with plugin support.
  • Node.js 20 or later, git, and the GitHub CLI gh logged in.
  • Optional, per channel: an OpenProject API token in ~/.config/op/config.json, a Figma token in ~/.config/figma/token, and an rclone remote named gdrive for Google Doc comments. Tokens are read at run time and never printed.

Install

/plugin marketplace add Tedydev-web/tedy-kit#v0.2.11
/plugin install tedy@tedy-kit

The `#v0.2.11` pins a release: the plugin changes only when you move the pin and run `claude plugin marketplace update tedy-kit`.

Local release worktree

A `directory` marketplace loads the plugin in place and ignores `version`, so the way to pin a local install is a git worktree checked out at a tag. Keep the development clone (here `~/Documents/workspace/tedy-kit`) for work, and point the marketplace at a release worktree:

git -C ~/Documents/workspace/tedy-kit worktree add --detach ~/Documents/workspace/tedy-kit-release v0.1.0
claude plugin marketplace add ~/Documents/workspace/tedy-kit-release
claude plugin install tedy@tedy-kit

Write the tag to `/release-tag`; `profile.mjs doctor` fails when the worktree is dirty or sits at another tag. Changing an existing marketplace path needs `claude plugin uninstall`,