[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79RP3Z7Q2WD89HMEPJQRERT":3,"skill-same:01M79RP3Z7Q2WD89HMEPJQRERT":54},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79RP3Z7Q2WD89HMEPJQRERT","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\".","jamon8888\u002Fhacienda-engine","jamon8888","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145190?v=4","01M79RNFE7K7JZ1AZG8TACAV98","Jamin Rubio","01M79RNFEV6ZC1SZ4K04SHDY8Z",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdesign-an-interface\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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\n- [ ] Who are the callers? (other modules, external users, tests)\n\n- [ ] What are the key operations?\n\n- [ ] Any constraints? (performance, compatibility, existing patterns)\n\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```text\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```text\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\n- [ ] Who are the callers? (other modules, external users, tests)\n\n- [ ] What are the key operations?\n\n- [ ] Any constraints? (performance, compatibility, existing patterns)\n\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```text\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```text\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","613e6deee7a2f31f95bac8beec31dd5171193c8d",".agents\u002Fskills\u002Fdesign-an-interface",0,"https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine","https:\u002F\u002Fhacienda-engine-hacienda-studio.vercel.app","https:\u002F\u002Fgithub.com\u002Fjamon8888","hacienda.diy","Maker","2026-11-15 05:01:55",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add jamon8888\u002Fhacienda-engine --skill design-an-interface",{"tool":40,"command":41},"bunx","bunx skills add jamon8888\u002Fhacienda-engine --skill design-an-interface",{"tool":43,"command":44},"pnpm","pnpm dlx skills add jamon8888\u002Fhacienda-engine --skill design-an-interface","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdesign-an-interface\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",110,"https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdesign-an-interface\u002Fagents\u002Fopenai.yaml",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M79RTKG5HB5PQ251W7J9C4S6","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.","https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fimpeccable\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79RTFDA4MAD9PPF3N15B68Y","wasm-constraints","WASM build constraints for the crates\u002Fxberg-wasm crate — the wasm-target feature set, no-tokio sync-only internal APIs, the mandatory SyncExtractor trait for WASM-compatible extractors, the 2 MB HTML size limit, size-optimized build config (opt-level=\"z\"), and the async-wrapper\u002Fsync-internal API pattern. Load when building for wasm32, adding or modifying a WASM-compatible extractor, or debugging WASM build\u002Fruntime failures.","https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.ai-rulez\u002Fskills\u002Fwasm-constraints\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79RTC4SV7NENKJXK2PSHK7H","release-versioning","How xberg versions are synced and released — Cargo.toml is the single source of truth, `task version:sync` propagates it to alef-managed binding manifests AND the integrations under integrations\u002F, which are versioned and published in lockstep with core (including -rc.N). Load before bumping a version, editing the version-sync task, or touching an integration's version\u002Fxberg dependency.","https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.ai-rulez\u002Fskills\u002Frelease-versioning\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79RT94KWTS5R5T61S71H1AD","plugin-architecture-patterns","Plugin architecture, registration, and trait patterns","https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.ai-rulez\u002Fskills\u002Fplugin-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79RT3X076QPZYK10QF6Q22X","mime-detection-routing","MIME type detection and extractor routing in core\u002Fmime.rs and core\u002Fextractor\u002Fbytes.rs — the extension→EXT_TO_MIME→validate→registry→extractor flow, key detection functions, the 118+ case-insensitive extension map, priority-based registry selection, wildcard MIME families, and how to add a new MIME type. Load when adding a format, wiring an extractor to a MIME type, or debugging why a file routes to the wrong (or no) extractor.","https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.ai-rulez\u002Fskills\u002Fmime-detection-routing\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79RSZYWZ6RSAM31N2Y0TXMN","format-specific-extraction","Format-specific document extraction workflows","https:\u002F\u002Fgithub.com\u002Fjamon8888\u002Fhacienda-engine\u002Fblob\u002Fmain\u002F.ai-rulez\u002Fskills\u002Fformat-specific-extraction\u002FSKILL.md",[],[]]