T-Tools plugin
A Claude Code plugin with stage commands from PRD and design to implementation, acceptance and release on Rust and React.
- 106 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Subagents write and edit code and run commands and tests, and `t-push` sends changes to the repository.
Install
- Works in
Manual install
claude --plugin-dir /path/to/skillsRun after cloning the repository, in your project folder. A configured context7 MCP server is required.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Subagents write and edit code and run commands and tests, and `t-push` sends changes to the repository.
This is third-party code. Review the repository files before installing.
What it does
T-Tools turns AI development into a repeatable process. One command matches one stage: `t-decision` and `t-prd` for framing, `t-design` for technical design, `t-super-run` for implementation with tests and independent acceptance, `t-web-demo-run` and `t-web-demo-accept` for user scenarios and `t-prd-publish` for release. Artifacts are written to disk and an interrupted stage resumes by rerunning the same command without relying on session memory. Acceptance runs in a separate read-only subagent under a shared protocol: required gates must pass and unresolved P0 and P1 findings block delivery. Product choices stay with the human, and `t-prd` asks clarifying questions before writing. The plugin covers Rust and React, Chrome extensions, mini programs, Flutter, Shopify and Figma reconstruction. `t-how` helps you start by suggesting an entry command for your goal.
Who it is for. Teams building Rust and React projects with Claude Code who want framing, implementation and acceptance in separate steps.
Good fit when
- An idea arrives and you must go from PRD to technical design without losing decisions.
- A session broke mid-implementation and work must resume from where it stopped.
- A feature is done and needs independent browser acceptance of user scenarios before release.
- The project is a Chrome extension or Flutter app with stage-specific checks.
Not a fit when
- The project uses another stack with no Rust, React, Flutter, Shopify or extensions.
- You need a one-off fix: a staged process would outweigh the task.
- The `context7` MCP server is unavailable though it is a stated prerequisite.
Example request
Run t-how and suggest which command to start a new user management feature with, then take it through the stages to acceptance.Limitations
A configured `context7` MCP server is required. Checking live pages and extensions needs Chrome DevTools MCP, Figma needs the official Figma server and asset handling also relies on Python `Pillow`, `ffmpeg`, `svgo` and `kyz`. The plugin is loaded by launching `claude --plugin-dir`, and Codex and ZCode, which lack that flag, use a separate guide. The `.ai/` and `docs/` folders are created while work runs and the logging library for Demo is installed by `t-init`. Shopify deployment with `shopify app deploy` is done by the user after `t-push`. Documentation is mostly Chinese with an English README.
How to disable. Start Claude Code without the `--plugin-dir` flag and delete the cloned plugin folder. The project's `.ai/` and `docs/` folders with artifacts stay.
FAQ
How do I load the plugin?
Clone the repository and run `claude --plugin-dir /path/to/skills` from your project folder. Configure the `context7` MCP server first.
Which command do I start with?
Run `t-how`: it explains the process for your goal and recommends an entry command. The short path begins with `t-decision`.
What if work breaks off?
Run the same command again. Artifacts live on disk and the stage resumes where it stopped.
Who accepts the work?
A separate read-only subagent. Required gates must pass and unresolved P0 and P1 findings block delivery.
How do I start a project from scratch?
`t-init <name>` builds a Rust and React skeleton and Shopify has the `--shopify` flag.
Discussion
No questions or reviews yet.
Related
PluginsGTPlanner turns a task description into a PRD and design document: planning, stack choice and design docs inside Claude Code.
Claude Code plugins with development recipes: agree on the outcome, design, implement with checks and run an independent review
A Claude Code plugin of eight builder skills: UI cloning, PRDs, CLAUDE.md scaffolding, terse research and a refactor tournament.
A plugin that readies a project for Claude Code: guidance, tests, review, TDD, refactoring and a resumable fix loop
Claude Code plugin with 17 skills: task sizing, design review, TDD, fresh-context subagents and a PR after three human decisions.
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
README in short
The README explains why the process is built on stages, how to install it, what the shortest path is and which commands cover different platforms. A separate file describes skills, subagents and protocols.