design-thinking
v0.1.3Design Thinking · Design Graph · Graph Protocol — draw the call graph before writing code. Turns plans, reviews, and refactors into an annotated, stack-agnostic call graph.
By widnyanaLicense: MIT7 GitHub starsUpdated 15 hours ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 2, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install design-thinking for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install design-thinking@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/widnyana/eyay-toolkitsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/design-thinking/.
Plugin files
├── .claude-plugin/plugin.json├── skills/design-graph/SKILL.md├── skills/design-method/SKILL.md└── skills/graph-protocol/SKILL.md
Included Skills3
Design Graph — the artifact: annotated call graph of a concrete problem; nodes = functions, edges = data flow; every node annotated with A, cardinality, E, R. Use when drawing a graph before writing code or reconstructing and diffing one against existing code. Includes the completeness checklist.
Design Thinking — the §1–§10 problem-first pipeline: shapes → graph(A) → cardinality → break points (E: ⟳ ↯ ☠) → requirements (R) → boundaries → behavior layers → scope → test layers → verdict. Stack-agnostic. Use when planning, designing, or refactoring any feature or system.
Graph Protocol — notation spec for Design Graphs. Fixed sections (PROBLEM, SHAPES, GRAPH, CARDINALITY, BOUNDARIES, BEHAVIOR, SCOPE, TEST LAYERS, VERDICT) and fixed markers (⟳retry ↯escape ☠die 🔒boundary (1)(N)(T) ⛈layer @scope). Use when writing, reviewing, or checking any Design Graph so notation is mechanically checkable and identical across languages.
Plugin manifests1
{
"name": "design-thinking",
"version": "0.1.3",
"description": "Design Thinking · Design Graph · Graph Protocol — draw the call graph before writing code. Turns plans, reviews, and refactors into an annotated, stack-agnostic call graph.",
"author": {
"name": "widnyana",
"email": "[email protected]"
},
"contributors": [
{
"name": "r17x",
"url": "https://github.com/r17x",
"note": "Original Design Thinking concepts and methodology"
}
],
"license": "MIT",
"repository": "https://github.com/widnyana/eyay-toolkits",
"keywords": [
"design",
"architecture",
"methodology",
"call-graph",
"planning"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[design-thinking on Agent Plugins Marketplace](https://pluginsmp.com/plugins/design-thinking)