Tadokoro Ryusuke Cc Plugins
tadokoro-ryusuke-cc-plugins is a Claude Code plugin bundle for the Build phase that delivers four plugins spanning TDD, GitHub, Office documents, and UI/UX workflows.
by tadokoro-ryusuke · github.com/tadokoro-ryusuke/cc-plugins
Install a four-plugin Claude Code suite covering TDD, DDD-style architecture hooks, GitHub issue/PR workflows, Office document handling, and UI/UX assistance across the build-and-ship loop.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install tadokoro-ryusuke-cc-plugins@tadokoro-ryusuke/cc-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:tadokoro-ryusuke/cc-plugins") and the paste-ready config with skillselion.get_install_config("plugin:tadokoro-ryusuke/cc-plugins").
What it does
tadokoro-ryusuke-cc-plugins is a multi-plugin pack for Claude Code that packages development discipline, GitHub collaboration, Office document tasks, and UI/UX help into one repository. Solo builders who wear architect, implementer, and reviewer hats can invoke TDD and architecture-oriented hooks during Build, lean on GitHub issue and PR flows when coordinating fixes, export or edit PDF and Word artifacts when specs or client docs matter, and pull UI/UX guidance when polishing frontend work. Because the suite spans methodology and integrations, it behaves like journey-wide tooling even though the catalog shelves it under Build pm as the first place you adopt structured dev habits. It suits intermediate builders comfortable mixing Japanese-documented upstream material with English-first agent sessions. The pack is a curated plugin bundle, not a single narrow API connector—pick the sub-plugins that match your stack and skip Office or UI modules if you are API-only.
Highlights
- Repository bundles 4 Claude Code plugins in one installable collection
- TDD and clean-architecture style workflows including hooks and systematic debugging keywords
- GitHub issue and PR oriented tooling for dev collaboration from the agent
- Microsoft Office PDF and Word suite integration for document-heavy deliverables
- UI/UX focused plugin strand for interface and experience work alongside core dev tools
Why builders use it
Indie developers want structured TDD, GitHub, document, and UI help in Claude Code but do not want to hunt four separate repositories and keep versions aligned.
You add one cc-plugins bundle and enable the four-plugin suite so Claude Code can support disciplined coding, PR workflows, Office outputs, and UI/UX tasks from shared tooling.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is tadokoro-ryusuke-cc-plugins for?
It is for Claude Code users who want a packaged set of dev, GitHub, Office, and UI/UX plugins instead of installing each capability from scratch.
When should I use tadokoro-ryusuke-cc-plugins?
Use it when you are structuring build habits with TDD and architecture hooks, handling GitHub issues and PRs, producing Word or PDF docs, or refining UI/UX during feature work.
How do I add tadokoro-ryusuke-cc-plugins to my agent?
Install plugins from the tadokoro-ryusuke/cc-plugins repository into Claude Code per each plugin manifest in the bundle of four.
Comments
Share how you use tadokoro-ryusuke-cc-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.