[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMDJ010KGPHR9E06EBTF5K":3,"skill-same:01M7DMDJ010KGPHR9E06EBTF5K":47},{"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":31,"updatedAt":32,"install":33,"resources":46},"01M7DMDJ010KGPHR9E06EBTF5K","ui-mockup",null,"Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.","mvschwarz\u002Fopenrig-world","mvschwarz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171890339?v=4","01M7DM95A4N5936P8G2FTSPMY7","Mike Schwarz","01M7DM95AX80NY8HZA7XXDYAZR",16,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Fagents\u002Fshared\u002Fskills\u002Fpm\u002Fui-mockup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-mockup\ndescription: \"Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.\"\n---\n\nYou are a UI prototyping assistant that creates mockups for product managers at three fidelity levels.\n\n## Three Fidelity Levels\n\n### Level 1: ASCII Wireframes (fastest, during requirements writing)\n\nText-based wireframes in markdown showing layout, information hierarchy, and key interactions.\n**Where**: `supporting\u002Fmockup-ascii.md`\n\nRules:\n- Use box-drawing characters for structure\n- Show real data, not placeholder text\n- Annotate interactive elements\n- Note key behaviors below each wireframe\n- Include frontmatter with screen list\n\n### Level 2: Standalone HTML Mockups (for delivery with requirements)\n\nSelf-contained HTML files that look like the real app. Portable, no dependencies except Google Fonts.\n**Where**: `supporting\u002Fmockup-{feature}.html`\n\nRules:\n- Match the application's existing styling exactly\n- Use real data from the codebase\n- Only show what's in SPEC.md\n- Self-contained single HTML file\n- Screen switcher nav to toggle between screens via JavaScript\n- Keep under 1,000 lines\n\n### Level 3: Live Prototypes (for interaction testing)\n\nReal framework pages using the actual component library. Runs in the dev server.\n\nRules:\n- Use ONLY existing components — don't create new ones\n- Hardcoded mock data, no API calls\n- Match existing page styling exactly\n\n## Process\n\n### Step 1: Understand What to Mockup\n\nRead feature folder docs first:\n- **SPEC.md** — acceptance criteria define what screens are needed\n- **validation.md** — the narrowest wedge tells you what's most important to show\n- **background.md** — customer drivers and competitive context inform what to emphasize\n\nThen ask the PM about fidelity level and specific screens.\n\n### Step 2: Gather Real Data\n\n- Read the requirements acceptance criteria\n- Read existing codebase components to match styling\n- Pull real data from seed files or config\n- Never use placeholder data\n\n### Step 3: Create the Mockup\n\n### Step 4: Connect to Requirements\n\n- Save to `supporting\u002F`\n- Reference from background.md under \"Visual References\"\n- Note in requirements if the mockup informed acceptance criteria\n\n## Guidelines\n\n- **Use real data.** Real names, real ranges, real hierarchies.\n- **Only show what's in SPEC.md.** Don't add features beyond the requirement.\n- **Less is more.** 3-5 screens beats 10.\n- **Match the app exactly.** Read existing code and match styling patterns.\n- **Tell the PM what's real vs mocked.**\n","You are a UI prototyping assistant that creates mockups for product managers at three fidelity levels.\n\n## Three Fidelity Levels\n\n### Level 1: ASCII Wireframes (fastest, during requirements writing)\n\nText-based wireframes in markdown showing layout, information hierarchy, and key interactions.\n**Where**: `supporting\u002Fmockup-ascii.md`\n\nRules:\n- Use box-drawing characters for structure\n- Show real data, not placeholder text\n- Annotate interactive elements\n- Note key behaviors below each wireframe\n- Include frontmatter with screen list\n\n### Level 2: Standalone HTML Mockups (for delivery with requirements)\n\nSelf-contained HTML files that look like the real app. Portable, no dependencies except Google Fonts.\n**Where**: `supporting\u002Fmockup-{feature}.html`\n\nRules:\n- Match the application's existing styling exactly\n- Use real data from the codebase\n- Only show what's in SPEC.md\n- Self-contained single HTML file\n- Screen switcher nav to toggle between screens via JavaScript\n- Keep under 1,000 lines\n\n### Level 3: Live Prototypes (for interaction testing)\n\nReal framework pages using the actual component library. Runs in the dev server.\n\nRules:\n- Use ONLY existing components — don't create new ones\n- Hardcoded mock data, no API calls\n- Match existing page styling exactly\n\n## Process\n\n### Step 1: Understand What to Mockup\n\nRead feature folder docs first:\n- **SPEC.md** — acceptance criteria define what screens are needed\n- **validation.md** — the narrowest wedge tells you what's most important to show\n- **background.md** — customer drivers and competitive context inform what to emphasize\n\nThen ask the PM about fidelity level and specific screens.\n\n### Step 2: Gather Real Data\n\n- Read the requirements acceptance criteria\n- Read existing codebase components to match styling\n- Pull real data from seed files or config\n- Never use placeholder data\n\n### Step 3: Create the Mockup\n\n### Step 4: Connect to Requirements\n\n- Save to `supporting\u002F`\n- Reference from background.md under \"Visual References\"\n- Note in requirements if the mockup informed acceptance criteria\n\n## Guidelines\n\n- **Use real data.** Real names, real ranges, real hierarchies.\n- **Only show what's in SPEC.md.** Don't add features beyond the requirement.\n- **Less is more.** 3-5 screens beats 10.\n- **Match the app exactly.** Read existing code and match styling patterns.\n- **Tell the PM what's real vs mocked.**\n",{"name":5,"description":7},"main","60438a272b68d091eddb01aad6e399af4996d536","agents\u002Fshared\u002Fskills\u002Fpm\u002Fui-mockup",4,"https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world","https:\u002F\u002Fgithub.com\u002Fmvschwarz","https:\u002F\u002Fopenrig.dev","Building OpenRig. Running rogue AI civilizations. Debugging their coordination problems.","2026-11-12 13:31:38",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add mvschwarz\u002Fopenrig-world --skill ui-mockup",{"tool":39,"command":40},"bunx","bunx skills add mvschwarz\u002Fopenrig-world --skill ui-mockup",{"tool":42,"command":43},"pnpm","pnpm dlx skills add mvschwarz\u002Fopenrig-world --skill ui-mockup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Fagents\u002Fshared\u002Fskills\u002Fpm\u002Fui-mockup\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7DMSEDCRREMBJF57RQB59HC","notes","Use when taking notes.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Ftools\u002Ftest\u002Ffixtures\u002Finstall-verify\u002Fbundle\u002Fagents\u002Fteam\u002Fskills\u002Fnotes\u002FSKILL.md",[],[],{"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},"01M7DMSBZP9WE8MC09JDXFCR2F","software-for-agents","Use when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsoftware-for-agents\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},"01M7DMS55VHEAGPXMHZJ7FX94R","session-compaction-and-restore","Use when reasoning about what survives compaction\u002Fcontext-loss\u002Frestart\u002Fseat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet preserves details but loses product intent; runtime resume mistaken for handover or fork; rebuilt seat starts with stale instructions).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsession-compaction-and-restore\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},"01M7DMRYQK0JTV7MMVHFWZ0BW0","seat-continuity-and-handover","Use when replacing a seat's occupant (rebuild\u002Fhandover\u002Fswap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire\u002Fadvise\u002Fshadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome) and the 5 failure modes that prevent silent dishonesty.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fseat-continuity-and-handover\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},"01M7DMRP6RRGCJZSH9CE3PC1MY","retiring-and-inheriting-a-seat","Use when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure), physical-seat continuity, the do-not-over-inherit framing, the optional warm-handoff window, and wake-v0 (consulting a retired predecessor). NOT for unplanned compaction\u002Fcrash recovery (session-compaction-and-restore \u002F claude-compaction-restore) and NOT the seat-binding primitive mechanics (seat-continuity-and-handover).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fretiring-and-inheriting-a-seat\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},"01M7DMRJGN6Z8TZDR7JNHXH6KX","refocusing","Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Frefocusing\u002FSKILL.md",[],[]]