By kouko
Philosophical thinking frameworks for problem clarification and deeper reasoning. 哲學思考框架・問題釐清。哲学的思考フレームワーク。
Hegelian Dialectics — thesis, antithesis, synthesis for trade-off analysis.
Descartes' Methodical Doubt — systematically doubt to find what's indubitable.
Popper's Falsifiability — turn claims into testable hypotheses.
First Principles — decompose to fundamental truths and rebuild from scratch.
Aristotle's Four Causes — analyze through material, formal, efficient, and final causes.
First Principles Thinking — decompose problems to fundamental truths and rebuild from scratch, rejecting analogy and convention. Use when user wants to rethink a problem from zero, not when they want to analyze what exists or compare options. 第一原理思考。第一原理・根本から考え直す。
Aristotle's Four Causes — analyze any subject through material, formal, efficient, and final causes. Use when user wants to deeply understand what something is and why it exists, not when they want implementation. 四因説・本質分析。四原因説・本質の分析。
Methodical Doubt — systematically doubt everything until only the indubitable remains. Use when auditing trust or stress-testing whether something is truly known. Not for decomposition (use first-principles), dialogue (use socratic-method), or single hypothesis testing (use popper-falsifiability). 方法的懐疑。方法論的懷疑。
反省 — 責めではなく学びのための内省的振り返り。失敗や期待外れの後に 「なぜ気づけなかったか」を掘り下げたいときに使う。実装や情報提供には 使わない。retrospective, reflection, postmortem.
Hegel's Dialectics — examine any position through thesis, antithesis, and synthesis to find higher-order solutions. Use when user faces trade-offs, opposing views, or binary choices, not when they want information or implementation. 弁証法・正反合。辯證法・正反合。
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Personal agent skills marketplace — 4 plugins covering domain-team quality gates, Obsidian vault workflows, philosophical thinking frameworks, and skill-authoring tools.
| Plugin | Skills | Slash commands | Description |
|---|---|---|---|
domain-teams | 10 | 9 | Domain team skills with checkpoint-based quality gates (code, docs, qa, devops, design, research, planning, copywriting) + skill-team meta-skill + router |
obsidian | 13 + 1 agent | 1 | Obsidian vault workflows — daily notes, diagrams, dashboards + imported kepano & axtonliu visual skills |
philosophers-toolkit | 12 | 12 | Philosophical thinking frameworks for problem clarification and deeper reasoning |
dev-workflow | 1 | 1 | Skill creation and eval workflows (adapted from upstream) |
Total: 36 skills, 23 slash commands across 4 plugins.
Team Skill (checkpoint orchestrator)
├── worker (sonnet) ← protocols/ + standards/
└── evaluator (opus) ← checklists/ + rubrics/ + standards/
Four-level quality gates:
SELF → Agent self-checks every delivery
MUST → Auto-trigger, non-skippable (e.g., security, a11y, citation)
SHOULD → Auto-trigger, skippable with reason (e.g., quality, UX)
MAY → User-requested only (e.g., QA, tech debt, visual)
Domain knowledge (colocated in each team skill directory, open access):
protocols/ → Step-by-step SOPs (execution guidance)
checklists/ → Binary pass/fail criteria (gate evaluation)
rubrics/ → Qualitative flag criteria (gate evaluation)
standards/ → Baseline rules (shared SSOT)
Applies to domain-teams plugin; other plugins use lighter-weight patterns.
domain-teamsDomain team skills with primary-source grounding and checkpoint-based quality
gates. All 9 teams launch worker (sonnet) for execution + evaluator (opus)
for quality-gate verdicts.
| Type | Name | Role |
|---|---|---|
| Skill | using-domain-teams | Entry point — routes requests to the right team |
| Team | Slash cmd | Role | Notable grounding |
|---|---|---|---|
planning-team | /planning | Cross-domain project planning (企画); produces PRODUCT-SPEC.md | Business thesis + JTBD |
code-team | /code | Code development; implements features, fixes bugs, writes TECH-SPEC.md | External dep: feature-dev:code-architect |
docs-team | /docs | Documentation + codebase assessment; README, API docs, tech debt audit | Diátaxis + Google Developer Style + JTAP |
qa-team | /qa | Test strategy and planning; E2E, integration, performance | ISTQB + ISO/IEC/IEEE 29119 + VSTeP / HAYST / ゆもつよ |
devops-team | /devops | Ship code safely; CI/CD, Dockerfiles, IaC, deployment, monitoring | Google SRE + DORA + 12-Factor + Continuous Delivery |
design-team | /design | Design with accessibility + quality review; UI, wireframes, UX strategy | Norman / Nielsen / WCAG 2.2 + 原研哉 / 深澤 / 黒須 / 上野 |
research-team | /research | Primary-source-grounded research; investment analysis, regime diagnosis | Systematic-review rigor + Investment Clock + Dalio + CAPE |
copywriting-team | /copywriting | Persuasive marketing copy — landing pages, キャッチコピー, email, voice guides, audits | 神田 PASONA + 谷山 + 今泉 + 川喜田 + Cialdini + Schwartz + McQuarrie & Mick + Lakoff + Thornton |
skill-team | /skill | Meta-skill: build or modify domain-team skills with convention discipline | Anthropic Agent Skills spec + Conventional Commits + Semver |
Each team skill directory is self-contained with SKILL.md + protocols/ +
checklists/ + rubrics/ + standards/ + optional research/ (grounding
audit trails).
obsidianObsidian vault daily workflows, visual tools, file intelligence, and dashboard design. Combines original skills with imports from the Obsidian community.
| Type | Name | Role |
|---|---|---|
| Skill | using-obsidian | Entry point — routes vault tasks to the right skill |
| Agent | obsidian-vault-organizer | Vault cleanup and organization (haiku) |
| Skill | Slash cmd | Role |
|---|---|---|
obsidian-daily | /obsidian | Start the day — daily note, priorities |
obsidian-vault-setup | — | Interactive vault configurator |
obsidian-tldr | — | Save conversation summary to vault |
obsidian-file-intel | — | Extract file content (PDF/PPTX/XLSX/DOCX/etc.) into Obsidian notes |
dashboard-design | — | Dashboard design workflow |
Upstream: kepano/obsidian-skills
npx claudepluginhub kouko/monkey-skills --plugin philosophers-toolkitDeveloper workflow skills — skill creation, evaluation, and iterative improvement
Domain team skills — planning (企画), code, design, research, copywriting with checkpoint-based quality gates
Redshift MCP server with comment-first exploration. 11 tools for schema/table/column listing, hit-count keyword search, and SELECT-only SQL. Comments are authoritative — names are unreliable. Zero-config install: run `/redshift-comment-mcp:redshift-setup` in chat after install — host / user / database via Q&A, password via system dialog (never enters chat), connection verified. Multi-cluster via `/redshift-setup <name>` then `/redshift-switch-profile`.
Obsidian vault workflows — daily notes, markdown, bases, diagrams, canvas, file intel, vault management, dashboard design
A structured toolkit of thinking skills for Claude Code — covering logic, ethics, creativity, decision-making, systems thinking, communication, and more. Each skill is an invokable command that applies a specific reasoning framework to any situation.
個人知識管理系統
The Answer Computer — reasoning tools for brainstorming, planning, architecture design, and deep thinking
GTD workflow automation for Obsidian vaults: capture, triage, route, focus
Structured thinking methods that counteract LLM reasoning biases during problem exploration — first principles, inversion, constraint manipulation, perspective forcing, analogy search, and more, with user-gated parallel subagent exploration for deep dives
Cognitive brainstorming protocol for Claude Code. Structures thinking through GROUND (problem discovery) -> EXPLORE (divergent) -> DECIDE (convergent) -> STRESS (stress-test) -> SHIP (artifacts) phases. Includes domain skills for technical architecture and conceptual work.