TypingMindTypingMindThe best frontend for AI
Mino Interface Implementation Separation logo

Mino Interface Implementation Separation

Community
my-take-dev
mino-interface-implementation-separation

consumerが知る目的・操作・契約と内部技術・手順を分け、技術漏出、caller分岐、責務境界と変更局所性を設計・監査するときに使う。if削減、interface量産、全体architectureの選定には使わない。

Overview

Publishermy-take-dev
Repositoryinspired-mino-design-skills
Skill namemino-interface-implementation-separation
Stars
345
Forks
9
Bundled files
2
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by my-take-dev on GitHub. Read the source before you install it.

Installation

Install the Mino Interface Implementation Separation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/my-take-dev/inspired-mino-design-skills/tree/main/.agents/skills/mino-interface-implementation-separation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/my-take-dev/inspired-mino-design-skills.git /tmp/inspired-mino-design-skills
mkdir -p .claude/skills
cp -r /tmp/inspired-mino-design-skills/.agents/skills/mino-interface-implementation-separation .claude/skills/mino-interface-implementation-separation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mino Interface Implementation Separation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Mino Interface Implementation Separation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Mino Interface Implementation Separation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Interface / Implementation Separation

Outcome Contract

consumerが必要とする目的・操作・契約と内部技術・手順を分け、漏出と過剰抽象化を判定する。修正が依頼され公開意味と範囲が確定していれば変更・検証まで進める。 正本packageのrootはboundary_package。 対応mode: design, review, implementation。

Reference Routing

  • 初回はskills/mino-core/references/shared-policies.mdを読み、Evidence・承認・判定を適用する。同じcontextで既読なら再読しない。通常の判断は本体とこの共通規則で行う。
  • codeの責務・命名を変更するときはskills/mino-core/references/code-design.md、既存挙動・公開契約の変更時はskills/mino-core/references/change-safety.mdを読み、具体的な変更と検証へ落とす。
  • 対象systemのfile/process/test実行・複数OS要件がある場合はskills/mino-core/references/platform-compatibility.mdを読み、host・対象・検証層を分ける。単なる回答記録の保存では追加読込しない。
  • 正本packageの作成・更新・引継ぎを依頼された場合だけskills/mino-interface-implementation-separation/schemas/package.mdを読み、必須fieldと実在参照を保持する。

Workflow

  1. caller、公開契約、code、依存、品質、実在variantから、domain判断・use-case調整・永続化・外部I/O・表現・運用を分類する。局所guardの問いへ全systemのpackageを要求しない。
  2. consumerのpurpose、must_know、must_not_knowと、operationの入力・結果・失敗・副作用・不変条件を定める。domain契約が該当すれば既存Contractを参照する。genericな技術境界には理由付きN/Aとconsumer semantic operationを使い、業務を発明しない。
  3. operationごとにend_to_end_deadline、retry_semantics、idempotency、duplicate_semantics、ambiguous_outcomeを個別にapplicable / not_applicable / unknownでscreenする。deadlineは上限・owner・timeout結果、retryは許可/禁止条件・owner、idempotency/duplicateは重複結果・owner、曖昧結果は観測結果・照合/復旧ownerを明確にする。
  4. N/Aは理由とEvidence、unknownは確認方法と影響を残す。該当しない意味fieldを空で展開しない。pure/read-onlyという名前だけで全N/Aにせず、外部依存と要求を調べる。冪等性keyは必要な根拠がある場合だけ定める。
  5. SDK型、DB row、framework型、provider手順、serialization、cache、algorithm、backoff、試行単位のtimeoutを実装側へ置く。consumerの判断に必要なretry・重複・曖昧結果の意味は公開面に残す。consumerが契約を使いadapterが実装する依存方向にする。
  6. semantic/invariant/contract/state/source-of-truth/failure-recovery/operational ownerは既存authorityを参照し、system全体の正本や条件の保証を再決定しない。
  7. selection boundaryは実在variantにだけ設ける。一実装でも外部障害隔離・契約安定の根拠があれば小さなportを使える。短いguardは維持し、将来用factoryや階層を作らない。状態・規則・実装variant・一時flagの分岐を区別する。
  8. 実装交換、実在variant追加/変更、業務規則変更の該当scenarioをpass / fail / not_applicable / unknownとEvidenceで評価する。既存caller・公開契約を変える場合だけconsumer一覧、互換window、段階移行、復旧、旧path利用ゼロの観測を設ける。

Hard Gates

  • if数・interface数を品質と扱わない。state・判断・更新は同じ目的と不変条件の責務へ集め、不正状態を全public writerから防げるか調べる。
  • 共通化は目的・契約・変更理由が揃う場合だけ行う。異なる意味を隠した抽象化やcallerへの技術漏出を残さない。
  • 意味不明の箇所を仮定で確定しない。変更予定の暫定pathを導入済みとせず、実在するTMP IDだけを参照する。

Completion

意味と内部実装が分かれればseparated、技術漏出・誤責務はleaky、根拠のない抽象はoverabstracted、適用自体が不要ならnot_applicable、重要未確認はindeterminate。併存するfindingを保持し、対象verdictと現在artifactの完成を分ける。

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Mino Interface Implementation Separation AI skill do?

consumerが知る目的・操作・契約と内部技術・手順を分け、技術漏出、caller分岐、責務境界と変更局所性を設計・監査するときに使う。if削減、interface量産、全体architectureの選定には使わない。

Why use Mino Interface Implementation Separation on TypingMind?

Because you install it once and use it with any model. Mino Interface Implementation Separation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Mino Interface Implementation Separation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/my-take-dev/inspired-mino-design-skills/tree/main/.agents/skills/mino-interface-implementation-separation. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Mino Interface Implementation Separation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Mino Interface Implementation Separation?

As many as you like. As long as a model supports skills, you can use Mino Interface Implementation Separation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Mino Interface Implementation Separation AI skill free?

It is published on GitHub by my-take-dev. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Openclaw Repair Sweep

openclaw
OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

82.2K
391K
1 files
View
openclaw logo

Openclaw Test Performance

openclaw
OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

82.2K
391K
1 files
View
openclaw logo

Openclaw Testing

openclaw
OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

82.2K
391K
2 files
View
openclaw logo

Release Openclaw Ci

openclaw
OrganizationPopular

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

82.2K
391K
3 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇