[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RC9KPYWMAP14ZQGBWWB8QS":3,"skill-same:01M6RC9KPYWMAP14ZQGBWWB8QS":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":13,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6RC9KPYWMAP14ZQGBWWB8QS","ideation",null,"Generate project ideas through creative constraints. Use when the user says 'I want to build something', 'give me a project idea', 'I'm bored', 'what should I make', 'inspire me', or any variant of 'I have tools but no direction'. Works for code, art, hardware, writing, tools, and anything that can be made.","cryptopafi\u002Fnexusos-skills","cryptopafi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F177822724?v=4","01M6RBPGFV10VSR55V7A819TGZ","01M6RBPGKCQAZH5QFGX99QW128",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fcreative\u002Fcreative-ideation\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"ideas","when","constraint","variant","for","creative ideation","can","direction","generation","project","writing","me","build","Art","use","projects","code","generate","brainstorming","2026-11-10 10:12:30",false,"---\nname: ideation\ntitle: Creative Ideation — Constraint-Driven Project Generation\ndescription: \"Generate project ideas through creative constraints. Use when the user says 'I want to build something', 'give me a project idea', 'I'm bored', 'what should I make', 'inspire me', or any variant of 'I have tools but no direction'. Works for code, art, hardware, writing, tools, and anything that can be made.\"\nversion: 1.0.0\nauthor: SHL0MS\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [Creative, Ideation, Projects, Brainstorming, Inspiration]\n    category: creative\n    requires_toolsets: []\n---\n\n# Creative Ideation\n\nGenerate project ideas through creative constraints. Constraint + direction = creativity.\n\n## How It Works\n\n1. **Pick a constraint** from the library below — random, or matched to the user's domain\u002Fmood\n2. **Interpret it broadly** — a coding prompt can become a hardware project, an art prompt can become a CLI tool\n3. **Generate 3 concrete project ideas** that satisfy the constraint\n4. **If they pick one, build it** — create the project, write the code, ship it\n\n## The Rule\n\nEvery prompt is interpreted as broadly as possible. \"Does this include X?\" → Yes. The prompts provide direction and mild constraint. Without either, there is no creativity.\n\n## Constraint Library\n\n### For Developers\n\n**Solve your own itch:**\nBuild the tool you wished existed this week. Under 50 lines. Ship it today.\n\n**Automate the annoying thing:**\nWhat's the most tedious part of your workflow? Script it away. Two hours to fix a problem that costs you five minutes a day.\n\n**The CLI tool that should exist:**\nThink of a command you've wished you could type. `git undo-that-thing-i-just-did`. `docker why-is-this-broken`. `npm explain-yourself`. Now build it.\n\n**Nothing new except glue:**\nMake something entirely from existing APIs, libraries, and datasets. The only original contribution is how you connect them.\n\n**Frankenstein week:**\nTake something that does X and make it do Y. A git repo that plays music. A Dockerfile that generates poetry. A cron job that sends compliments.\n\n**Subtract:**\nHow much can you remove from a codebase before it breaks? Strip a tool to its minimum viable function. Delete until only the essence remains.\n\n**High concept, low effort:**\nA deep idea, lazily executed. The concept should be brilliant. The implementation should take an afternoon. If it takes longer, you're overthinking it.\n\n### For Makers & Artists\n\n**Blatantly copy something:**\nPick something you admire — a tool, an artwork, an interface. Recreate it from scratch. The learning is in the gap between your version and theirs.\n\n**One million of something:**\nOne million is both a lot and not that much. One million pixels is a 1MB photo. One million API calls is a Tuesday. One million of anything becomes interesting at scale.\n\n**Make something that dies:**\nA website that loses a feature every day. A chatbot that forgets. A countdown to nothing. An exercise in rot, killing, or letting go.\n\n**Do a lot of math:**\nGenerative geometry, shader golf, mathematical art, computational origami. Time to re-learn what an arcsin is.\n\n### For Anyone\n\n**Text is the universal interface:**\nBuild something where text is the only interface. No buttons, no graphics, just words in and words out. Text can go in and out of almost anything.\n\n**Start at the punchline:**\nThink of something that would be a funny sentence. Work backwards to make it real. \"I taught my thermostat to gaslight me\" → now build it.\n\n**Hostile UI:**\nMake something intentionally painful to use. A password field that requires 47 conditions. A form where every label lies. A CLI that judges your commands.\n\n**Take two:**\nRemember an old project. Do it again from scratch. No looking at the original. See what changed about how you think.\n\nSee `references\u002Ffull-prompt-library.md` for 30+ additional constraints across communication, scale, philosophy, transformation, and more.\n\n## Matching Constraints to Users\n\n| User says | Pick from |\n|-----------|-----------|\n| \"I want to build something\" (no direction) | Random — any constraint |\n| \"I'm learning [language]\" | Blatantly copy something, Automate the annoying thing |\n| \"I want something weird\" | Hostile UI, Frankenstein week, Start at the punchline |\n| \"I want something useful\" | Solve your own itch, The CLI that should exist, Automate the annoying thing |\n| \"I want something beautiful\" | Do a lot of math, One million of something |\n| \"I'm burned out\" | High concept low effort, Make something that dies |\n| \"Weekend project\" | Nothing new except glue, Start at the punchline |\n| \"I want a challenge\" | One million of something, Subtract, Take two |\n\n## Output Format\n\n```\n## Constraint: [Name]\n> [The constraint, one sentence]\n\n### Ideas\n\n1. **[One-line pitch]**\n   [2-3 sentences: what you'd build and why it's interesting]\n   ⏱ [weekend \u002F week \u002F month] • ? [stack]\n\n2. **[One-line pitch]**\n   [2-3 sentences]\n   ⏱ ... • ? ...\n\n3. **[One-line pitch]**\n   [2-3 sentences]\n   ⏱ ... • ? ...\n```\n\n## Example\n\n```\n## Constraint: The CLI tool that should exist\n> Think of a command you've wished you could type. Now build it.\n\n### Ideas\n\n1. **`git whatsup` — show what happened while you were away**\n   Compares your last active commit to HEAD and summarizes what changed,\n   who committed, and what PRs merged. Like a morning standup from your repo.\n   ⏱ weekend • ? Python, GitPython, click\n\n2. **`explain 503` — HTTP status codes for humans**\n   Pipe any status code or error message and get a plain-English explanation\n   with common causes and fixes. Pulls from a curated database, not an LLM.\n   ⏱ weekend • ? Rust or Go, static dataset\n\n3. **`deps why \u003Cpackage>` — why is this in my dependency tree**\n   Traces a transitive dependency back to the direct dependency that pulled\n   it in. Answers \"why do I have 47 copies of lodash\" in one command.\n   ⏱ weekend • ? Node.js, npm\u002Fyarn lockfile parsing\n```\n\nAfter the user picks one, start building — create the project, write the code, iterate.\n\n## Attribution\n\nConstraint approach inspired by [wttdotm.com\u002Fprompts.html](https:\u002F\u002Fwttdotm.com\u002Fprompts.html). Adapted and expanded for software development and general-purpose ideation.\n","# Creative Ideation\n\nGenerate project ideas through creative constraints. Constraint + direction = creativity.\n\n## How It Works\n\n1. **Pick a constraint** from the library below — random, or matched to the user's domain\u002Fmood\n2. **Interpret it broadly** — a coding prompt can become a hardware project, an art prompt can become a CLI tool\n3. **Generate 3 concrete project ideas** that satisfy the constraint\n4. **If they pick one, build it** — create the project, write the code, ship it\n\n## The Rule\n\nEvery prompt is interpreted as broadly as possible. \"Does this include X?\" → Yes. The prompts provide direction and mild constraint. Without either, there is no creativity.\n\n## Constraint Library\n\n### For Developers\n\n**Solve your own itch:**\nBuild the tool you wished existed this week. Under 50 lines. Ship it today.\n\n**Automate the annoying thing:**\nWhat's the most tedious part of your workflow? Script it away. Two hours to fix a problem that costs you five minutes a day.\n\n**The CLI tool that should exist:**\nThink of a command you've wished you could type. `git undo-that-thing-i-just-did`. `docker why-is-this-broken`. `npm explain-yourself`. Now build it.\n\n**Nothing new except glue:**\nMake something entirely from existing APIs, libraries, and datasets. The only original contribution is how you connect them.\n\n**Frankenstein week:**\nTake something that does X and make it do Y. A git repo that plays music. A Dockerfile that generates poetry. A cron job that sends compliments.\n\n**Subtract:**\nHow much can you remove from a codebase before it breaks? Strip a tool to its minimum viable function. Delete until only the essence remains.\n\n**High concept, low effort:**\nA deep idea, lazily executed. The concept should be brilliant. The implementation should take an afternoon. If it takes longer, you're overthinking it.\n\n### For Makers & Artists\n\n**Blatantly copy something:**\nPick something you admire — a tool, an artwork, an interface. Recreate it from scratch. The learning is in the gap between your version and theirs.\n\n**One million of something:**\nOne million is both a lot and not that much. One million pixels is a 1MB photo. One million API calls is a Tuesday. One million of anything becomes interesting at scale.\n\n**Make something that dies:**\nA website that loses a feature every day. A chatbot that forgets. A countdown to nothing. An exercise in rot, killing, or letting go.\n\n**Do a lot of math:**\nGenerative geometry, shader golf, mathematical art, computational origami. Time to re-learn what an arcsin is.\n\n### For Anyone\n\n**Text is the universal interface:**\nBuild something where text is the only interface. No buttons, no graphics, just words in and words out. Text can go in and out of almost anything.\n\n**Start at the punchline:**\nThink of something that would be a funny sentence. Work backwards to make it real. \"I taught my thermostat to gaslight me\" → now build it.\n\n**Hostile UI:**\nMake something intentionally painful to use. A password field that requires 47 conditions. A form where every label lies. A CLI that judges your commands.\n\n**Take two:**\nRemember an old project. Do it again from scratch. No looking at the original. See what changed about how you think.\n\nSee `references\u002Ffull-prompt-library.md` for 30+ additional constraints across communication, scale, philosophy, transformation, and more.\n\n## Matching Constraints to Users\n\n| User says | Pick from |\n|-----------|-----------|\n| \"I want to build something\" (no direction) | Random — any constraint |\n| \"I'm learning [language]\" | Blatantly copy something, Automate the annoying thing |\n| \"I want something weird\" | Hostile UI, Frankenstein week, Start at the punchline |\n| \"I want something useful\" | Solve your own itch, The CLI that should exist, Automate the annoying thing |\n| \"I want something beautiful\" | Do a lot of math, One million of something |\n| \"I'm burned out\" | High concept low effort, Make something that dies |\n| \"Weekend project\" | Nothing new except glue, Start at the punchline |\n| \"I want a challenge\" | One million of something, Subtract, Take two |\n\n## Output Format\n\n```\n## Constraint: [Name]\n> [The constraint, one sentence]\n\n### Ideas\n\n1. **[One-line pitch]**\n   [2-3 sentences: what you'd build and why it's interesting]\n   ⏱ [weekend \u002F week \u002F month] • ? [stack]\n\n2. **[One-line pitch]**\n   [2-3 sentences]\n   ⏱ ... • ? ...\n\n3. **[One-line pitch]**\n   [2-3 sentences]\n   ⏱ ... • ? ...\n```\n\n## Example\n\n```\n## Constraint: The CLI tool that should exist\n> Think of a command you've wished you could type. Now build it.\n\n### Ideas\n\n1. **`git whatsup` — show what happened while you were away**\n   Compares your last active commit to HEAD and summarizes what changed,\n   who committed, and what PRs merged. Like a morning standup from your repo.\n   ⏱ weekend • ? Python, GitPython, click\n\n2. **`explain 503` — HTTP status codes for humans**\n   Pipe any status code or error message and get a plain-English explanation\n   with common causes and fixes. Pulls from a curated database, not an LLM.\n   ⏱ weekend • ? Rust or Go, static dataset\n\n3. **`deps why \u003Cpackage>` — why is this in my dependency tree**\n   Traces a transitive dependency back to the direct dependency that pulled\n   it in. Answers \"why do I have 47 copies of lodash\" in one command.\n   ⏱ weekend • ? Node.js, npm\u002Fyarn lockfile parsing\n```\n\nAfter the user picks one, start building — create the project, write the code, iterate.\n\n## Attribution\n\nConstraint approach inspired by [wttdotm.com\u002Fprompts.html](https:\u002F\u002Fwttdotm.com\u002Fprompts.html). Adapted and expanded for software development and general-purpose ideation.\n",{"name":5,"title":42,"author":43,"license":14,"version":44,"metadata":45,"description":7},"Creative Ideation — Constraint-Driven Project Generation","SHL0MS","1.0.0",{"hermes":46},{"tags":47,"category":53,"requires_toolsets":54},[48,49,50,51,52],"Creative","Ideation","Projects","Brainstorming","Inspiration","creative",[],"main","5c34213899a7e6ba7597a65f60c542d4b7cb9521","creative\u002Fcreative-ideation","https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills","https:\u002F\u002Fgithub.com\u002Fcryptopafi","2026-08-24 14:21:06",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add cryptopafi\u002Fnexusos-skills --skill ideation",{"tool":67,"command":68},"bunx","bunx skills add cryptopafi\u002Fnexusos-skills --skill ideation",{"tool":70,"command":71},"pnpm","pnpm dlx skills add cryptopafi\u002Fnexusos-skills --skill ideation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fcreative\u002Fcreative-ideation\u002FSKILL.md",true,[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Ffull-prompt-library.md","REFERENCE","参考文档",4215,"https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fcreative\u002Fcreative-ideation\u002Freferences\u002Ffull-prompt-library.md",[82,121,149,164,186,207],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":104,"publishedAt":37},"01M6WYTX72QQN7J0ZKSES38NEN","writing-plans","Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.","https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[88,93,96,101],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":94,"categoryName":95,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000036","内容创作者",[28,105,106,107,108,109,110,111,112,34,113,114,115,116,117,118,119,22,120,19],"writing plans","plans","design","review","workflow","documentation","tasks","development","planning","code-review","subagent","superpowers","paths","test-driven-development","you","test-driven",{"skillNo":122,"name":118,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":134,"publishedAt":37},"01M6WYTN5C9XC8EYWGPXPWKGGX","Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.","https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[126,129,132,133],{"categoryNo":127,"categoryName":128,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":130,"categoryName":131,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":94,"categoryName":95,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},[135,136,112,137,138,28,139,34,140,115,116,141,142,143,144,145,146,147,148,19],"test","test driven development","driven","testing","debugging","refactor","red-green-refactor","cycle","green","systematic","bugfix","implementing","systematic-debugging","test-first",{"skillNo":150,"name":147,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":37},"01M6WYTDP76WP7Y5QVSWT2303F","Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.","https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[154],{"categoryNo":130,"categoryName":131,"taxonomyType":91,"taxonomyTypeDesc":92},[156,139,144,28,135,112,115,32,116,157,158,159,106,160,118,161,120,162,163,19],"systematic debugging","bug","root-cause","problem-solving","problem","fixes","phase","root cause",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":179,"publishedAt":37},"01M6WYT5P36B4M01BASQB9F0AY","subagent-driven-development","Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).","https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[170,171,174,175,176],{"categoryNo":94,"categoryName":95,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":172,"categoryName":173,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":177,"categoryName":178,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000037","律师与法务",[112,180,115,137,28,108,109,181,111,34,182,114,183,184,116,106,185,118,120,19],"subagent driven development","code quality","delegation","parallel","delegate","fresh",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":194,"publishedAt":37},"01M6WYSXD1J366HVZRMRE7ENDA","requesting-code-review","Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.","https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[192,193],{"categoryNo":127,"categoryName":128,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[195,108,34,196,28,197,114,198,199,200,201,115,202,203,204,116,118,205,206,120],"code review","requesting code review","commit","verification","security scan","pipeline","loop","reviewer","fix","auto","static","auto-fix",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":213,"publishedAt":37},"01M6WYSNEBG74A5FCMCDGQ7QP4","plan","Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes\u002Fplans\u002F` directory, and do not execute the work.","https:\u002F\u002Fgithub.com\u002Fcryptopafi\u002Fnexusos-skills\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[209,28,214,109,112,113,215,115,216,217,218,219,220,221,106,222,223,224,22,225],"directory","markdown","workspace","work","write","implementation","do","active","plan mode","inspect","mode","plan-mode"]