ワンクリックで
memba
memba には mattwynne から収集した 8 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 skill 詳細ページを表示します。
このリポジトリの skills
Interview Matt about the next product/dev iteration, turn the discussion into a focused iteration plan, publish planning artifacts, validate the plan, and ask whether this LLM session should launch the Fabro implementation-and-review delivery workflow. Use when planning the next iteration, shaping work before implementation, or preparing a plan for delivery.
Delegate self-contained research, review, planning, debugging, or implementation subtasks to a Pi subagent running the openai-codex/gpt-5.5 model. Use when the user asks for Pi, GPT-5.5, a subagent, independent analysis, parallel investigation, or a second coding-agent opinion.
Use when writing or reviewing Gherkin scenarios, especially after discovering examples or edge cases that reveal a business rule
Offer to capture and, when accepted, write a docs/kaizen observation when we notice friction, imperfections, waste, opacity, brittleness, or failure in the pipeline/factory/workflows/tooling used to create the product. Use for workflow/tooling problems, not ordinary product bugs.
Read, audit, and safely manipulate Resend email configuration and message data through the Resend API. Use when inspecting domains, API keys, audiences, contacts, broadcasts, emails, webhooks, or making explicit Resend changes with an API key from the environment.
Read, audit, and safely manipulate Postmark configuration and message data through the Postmark API. Use when inspecting servers, streams, senders, domains, templates, messages, webhooks, suppressions, or making explicit Postmark changes with API tokens from the environment.
Read, audit, and safely manipulate DNSimple DNS configuration through the DNSimple API. Use when inspecting domains, zones, DNS records, or making explicit DNS changes with a DNSimple API token from the environment.
Investigate and resolve docs/kaizen problem observation notes. Use when Matt asks to fix a kaizen note, investigate root cause, suggest repair options, or apply an obvious workflow/tooling fix and update the note with the resolution.