Evaluate user-facing interfaces against Nielsen's 10 Usability Heuristics. Complements /mycelium:service-check (Downe = service-level quality, Nielsen = interface-level quality).
日本語の概要は準備中です。原文の説明を表示しています。
63 件(haabe のリポジトリ) ・ 人気順
概要と使いどころ
Evaluate user-facing interfaces against Nielsen's 10 Usability Heuristics. Complements /mycelium:service-check (Downe = service-level quality, Nielsen = interface-level quality).
日本語の概要は準備中です。原文の説明を表示しています。
Use to evaluate a service or feature against Downe's 15 principles of good services.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for conducting Torres-style story-based interviews with the people whose experience you're researching, with bias mitigation and a JTBD lens.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP secure design review for code and architecture. Checks input validation, authentication, authorization, data protection.
日本語の概要は準備中です。原文の説明を表示しています。
Audit whether the theories/methodologies a project claims to implement are faithfully operationalized — or name-dropped, partially built, distorted, or over-claimed. Source-grounds the load-bearing theories; tags the rest provisional. Run periodically alongside /framework-health.
日本語の概要は準備中です。原文の説明を表示しています。
Derive this project's own integration conventions from what the code already does, draft them as a wiring contract, and hold new work to it. Closes the built-but-not-wired gap at L3 (walking skeleton) — a mechanism that ships and is never called reads green in every other check.
日本語の概要は準備中です。原文の説明を表示しています。
Assess team structure against Skelton's Team Topologies. Evaluate cognitive load, interaction modes, and Conway's Law alignment.
日本語の概要は準備中です。原文の説明を表示しています。
Use to conduct STRIDE threat modeling for a system or feature design.
日本語の概要は準備中です。原文の説明を表示しています。
Explainability (XAI) audit for products containing AI components. Five-stage tier-scaled check: risk classification, stakeholder×question matrix, fidelity audit, system card, recourse path. Honest about what was validated functionally vs what needs user testing.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a Wardley Map of how any domain delivers value. Maps the needs it serves, the capabilities involved, how each is evolving (genesis to commodity), and strategic plays. Applies to any domain, not only software.
日本語の概要は準備中です。原文の説明を表示しています。
Map the needs of the people you're building or exploring for, independently of solutions, using Allen's User Needs Mapping methodology. Identifies underserved needs that feed into the Opportunity Solution Tree.
日本語の概要は準備中です。原文の説明を表示しています。
One command from "plugin installed" to "running brief on your idea." Combines /mycelium:setup (project-state initialization) and /mycelium:interview (10-minute discovery brief) into a single flow. Run this immediately after installing the Mycelium plugin — it's the recommended entry point for first-time users.
日本語の概要は準備中です。原文の説明を表示しています。
First-run setup for the Mycelium plugin. Creates project-state directories (.claude/canvas, .claude/diamonds, .claude/memory, .claude/harness) and minimal starter files in the user's project. Optionally provisions opencode runtime support (a starter scaffold) when opencode is detected or requested. Idempotent — re-running on an initialized project is a no-op. Run this once after installing the Mycelium plugin and before invoking other skills.
日本語の概要は準備中です。原文の説明を表示しています。
Update canvas sections with new evidence. Ensures canvas stays current as the single source of truth.
日本語の概要は準備中です。原文の説明を表示しています。
Synchronize canvas state across team sessions via git. Ensures all team members see the same product knowledge.
日本語の概要は準備中です。原文の説明を表示しています。
Use when onboarding a new product/project. Progressive interview to understand purpose, vision, north star, and competitive landscape.
日本語の概要は準備中です。原文の説明を表示しています。
Lint canvas files for staleness, missing fields, inconsistent evidence types, and orphaned references. Run periodically or before major transitions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building anything USER-FACING (or with persuasion/retention/cancellation/consent/pricing flows, or that touches vulnerable people) to surface design-level harm the security/privacy/compliance gates miss: dark/deceptive patterns and foreseeable misuse. Assumes the product works as designed and asks who it could harm and whether it is Happier-negative. NUDGE, not a block.
日本語の概要は準備中です。原文の説明を表示しています。
Design the smallest viable test to validate or invalidate a critical assumption. Based on Torres's assumption testing framework, organized by Gilad's AFTER model (Assessment → Fact-Finding → Tests → Experiments → Release Results).
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured handoff materials for offline human tasks (interviews, observations, outreach). Creates actionable briefs with phone-friendly capture templates.
日本語の概要は準備中です。原文の説明を表示しています。
Record a diamond's next decision (set_target; start_experiment and commit_to_build; release; close; an L0's state_purpose or review). Runs the theory gates each decision needs, validates evidence, and at close runs the executable Definition of Done checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Use to evaluate the current state of a diamond. Checks theory gates, confidence levels, and recommends next action.
日本語の概要は準備中です。原文の説明を表示しています。
Accessibility audit, scoped to the surfaces a product actually has. Detects web / rendered_markdown / terminal / native_app / video_audio / document / headless, then applies only the criteria that bind. WCAG 2.1 AA in full for web; not at all for headless.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting implementation on a new or unfamiliar codebase. Auto-detects tech stack and sets up development context.
日本語の概要は準備中です。原文の説明を表示しています。