[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M748F20MPP8DKF0KWDXJJW2C":3,"skill-same:01M748F20MPP8DKF0KWDXJJW2C":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M748F20MPP8DKF0KWDXJJW2C","design-an-interface",null,"Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions \"design it twice\".","mphinance\u002Falpha-skills","mphinance","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F217996678?v=4","01M71VQC89A6CMFACD2J1CJW6E","Michael H","01M71VQC9B4C0BJ7XXKT8RWRV9",32,"MIT","https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-an-interface\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: design-an-interface\ndescription: Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions \"design it twice\".\n---\n\n# Design an Interface\n\nBased on \"Design It Twice\" from \"A Philosophy of Software Design\": your first idea is unlikely to be the best. Generate multiple radically different designs, then compare.\n\n## Workflow\n\n### 1. Gather Requirements\n\nBefore designing, understand:\n\n- [ ] What problem does this module solve?\n- [ ] Who are the callers? (other modules, external users, tests)\n- [ ] What are the key operations?\n- [ ] Any constraints? (performance, compatibility, existing patterns)\n- [ ] What should be hidden inside vs exposed?\n\nAsk: \"What does this module need to do? Who will use it?\"\n\n### 2. Generate Designs (Parallel Sub-Agents)\n\nSpawn 3+ sub-agents simultaneously using Task tool. Each must produce a **radically different** approach.\n\n```\nPrompt template for each sub-agent:\n\nDesign an interface for: [module description]\n\nRequirements: [gathered requirements]\n\nConstraints for this design: [assign a different constraint to each agent]\n- Agent 1: \"Minimize method count - aim for 1-3 methods max\"\n- Agent 2: \"Maximize flexibility - support many use cases\"\n- Agent 3: \"Optimize for the most common case\"\n- Agent 4: \"Take inspiration from [specific paradigm\u002Flibrary]\"\n\nOutput format:\n1. Interface signature (types\u002Fmethods)\n2. Usage example (how caller uses it)\n3. What this design hides internally\n4. Trade-offs of this approach\n```\n\n### 3. Present Designs\n\nShow each design with:\n\n1. **Interface signature** - types, methods, params\n2. **Usage examples** - how callers actually use it in practice\n3. **What it hides** - complexity kept internal\n\nPresent designs sequentially so user can absorb each approach before comparison.\n\n### 4. Compare Designs\n\nAfter showing all designs, compare them on:\n\n- **Interface simplicity**: fewer methods, simpler params\n- **General-purpose vs specialized**: flexibility vs focus\n- **Implementation efficiency**: does shape allow efficient internals?\n- **Depth**: small interface hiding significant complexity (good) vs large interface with thin implementation (bad)\n- **Ease of correct use** vs **ease of misuse**\n\nDiscuss trade-offs in prose, not tables. Highlight where designs diverge most.\n\n### 5. Synthesize\n\nOften the best design combines insights from multiple options. Ask:\n\n- \"Which design best fits your primary use case?\"\n- \"Any elements from other designs worth incorporating?\"\n\n## Evaluation Criteria\n\nFrom \"A Philosophy of Software Design\":\n\n**Interface simplicity**: Fewer methods, simpler params = easier to learn and use correctly.\n\n**General-purpose**: Can handle future use cases without changes. But beware over-generalization.\n\n**Implementation efficiency**: Does interface shape allow efficient implementation? Or force awkward internals?\n\n**Depth**: Small interface hiding significant complexity = deep module (good). Large interface with thin implementation = shallow module (avoid).\n\n## Anti-Patterns\n\n- Don't let sub-agents produce similar designs - enforce radical difference\n- Don't skip comparison - the value is in contrast\n- Don't implement - this is purely about interface shape\n- Don't evaluate based on implementation effort\n","# Design an Interface\n\nBased on \"Design It Twice\" from \"A Philosophy of Software Design\": your first idea is unlikely to be the best. Generate multiple radically different designs, then compare.\n\n## Workflow\n\n### 1. Gather Requirements\n\nBefore designing, understand:\n\n- [ ] What problem does this module solve?\n- [ ] Who are the callers? (other modules, external users, tests)\n- [ ] What are the key operations?\n- [ ] Any constraints? (performance, compatibility, existing patterns)\n- [ ] What should be hidden inside vs exposed?\n\nAsk: \"What does this module need to do? Who will use it?\"\n\n### 2. Generate Designs (Parallel Sub-Agents)\n\nSpawn 3+ sub-agents simultaneously using Task tool. Each must produce a **radically different** approach.\n\n```\nPrompt template for each sub-agent:\n\nDesign an interface for: [module description]\n\nRequirements: [gathered requirements]\n\nConstraints for this design: [assign a different constraint to each agent]\n- Agent 1: \"Minimize method count - aim for 1-3 methods max\"\n- Agent 2: \"Maximize flexibility - support many use cases\"\n- Agent 3: \"Optimize for the most common case\"\n- Agent 4: \"Take inspiration from [specific paradigm\u002Flibrary]\"\n\nOutput format:\n1. Interface signature (types\u002Fmethods)\n2. Usage example (how caller uses it)\n3. What this design hides internally\n4. Trade-offs of this approach\n```\n\n### 3. Present Designs\n\nShow each design with:\n\n1. **Interface signature** - types, methods, params\n2. **Usage examples** - how callers actually use it in practice\n3. **What it hides** - complexity kept internal\n\nPresent designs sequentially so user can absorb each approach before comparison.\n\n### 4. Compare Designs\n\nAfter showing all designs, compare them on:\n\n- **Interface simplicity**: fewer methods, simpler params\n- **General-purpose vs specialized**: flexibility vs focus\n- **Implementation efficiency**: does shape allow efficient internals?\n- **Depth**: small interface hiding significant complexity (good) vs large interface with thin implementation (bad)\n- **Ease of correct use** vs **ease of misuse**\n\nDiscuss trade-offs in prose, not tables. Highlight where designs diverge most.\n\n### 5. Synthesize\n\nOften the best design combines insights from multiple options. Ask:\n\n- \"Which design best fits your primary use case?\"\n- \"Any elements from other designs worth incorporating?\"\n\n## Evaluation Criteria\n\nFrom \"A Philosophy of Software Design\":\n\n**Interface simplicity**: Fewer methods, simpler params = easier to learn and use correctly.\n\n**General-purpose**: Can handle future use cases without changes. But beware over-generalization.\n\n**Implementation efficiency**: Does interface shape allow efficient implementation? Or force awkward internals?\n\n**Depth**: Small interface hiding significant complexity = deep module (good). Large interface with thin implementation = shallow module (avoid).\n\n## Anti-Patterns\n\n- Don't let sub-agents produce similar designs - enforce radical difference\n- Don't skip comparison - the value is in contrast\n- Don't implement - this is purely about interface shape\n- Don't evaluate based on implementation effort\n",{"name":5,"description":7},"main","78b6ee6816aca6e5660cc7f0382650e9e7687086","skills\u002Fdesign-an-interface",6,"https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills","https:\u002F\u002Fgithub.com\u002Fmphinance","https:\u002F\u002Fmphinance.com","2026-11-13 05:04:11",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add mphinance\u002Falpha-skills --skill design-an-interface",{"tool":38,"command":39},"bunx","bunx skills add mphinance\u002Falpha-skills --skill design-an-interface",{"tool":41,"command":42},"pnpm","pnpm dlx skills add mphinance\u002Falpha-skills --skill design-an-interface","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-an-interface\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"README.md","REFERENCE","参考文档",3366,"https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-an-interface\u002FREADME.md",[53,61,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"01M7BANC8ZXMVWWHSY3E31AAC3","order-lifecycle-safety","Idempotency, reconcile-before-retry, audit-before-forward and environment-proof preflight rules for any code or agent that places broker orders. Use when building or reviewing an order path, handling a timeout or unknown order outcome, adding client_order_id, deciding whether a retry is safe, or confirming paper vs live before sending an order.","https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fskills\u002Forder-lifecycle-safety\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":62,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":60},"01M7BAMZ37XP7XM8YDXWWSX0T9","https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fquant-skills\u002Fskills\u002Forder-lifecycle-safety\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74928K9ZC74YQ1GMYB4N2Q0","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M749259PAEA22A891D0EJTKK","wireframe-sketch","A hand-drawn wireframe exploration — graph-paper background, marker \u002F\npencil tone, multiple tab labels for variants, sticky-note annotations,\nscribbled chart placeholders, hatched fills. Reads like a designer's\nwhiteboard before any pixels are committed. Use when the brief asks for\n\"wireframe\", \"sketch wireframe\", \"hand-drawn\", \"lo-fi\", \"whiteboard\",\n\"草稿\", or \"手绘原型\".","https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwireframe-sketch\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74920ZWJS5Q1JRVJ8TSTQ5A","weekly-update","Single-file horizontal-swipe slide deck for a weekly team update —\nshipped, in flight, blocked, metrics, asks. 6–8 slides. Use when the\nbrief mentions \"weekly update\", \"team update slides\", \"weekly status\",\n\"周报演示\".","https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweekly-update\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7491YFRHYFV5QPS0MJ3DSNP","webull-openapi","Trade stocks, options, futures, crypto, and event contracts on Webull. Query real-time and historical market data. Manage accounts and positions. Supports US, HK, JP, SG, TH, MY, UK, MX, BR, EU, ZA, and AU regions with configurable risk controls.","https:\u002F\u002Fgithub.com\u002Fmphinance\u002Falpha-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebull-openapi\u002FSKILL.md",[],[]]