[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-80915":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":15,"stars7d":15,"stars30d":16,"stars90d":14,"forks30d":14,"starsTrendScore":16,"compositeScore":17,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":18,"fork":18,"defaultBranch":19,"hasWiki":20,"hasPages":18,"topics":21,"createdAt":9,"pushedAt":9,"updatedAt":22,"readmeContent":23,"aiSummary":24,"trendingCount":14,"starSnapshotCount":14,"syncStatus":25,"lastSyncTime":26,"discoverSource":27},80915,"six-hats-skill","juanallo\u002Fsix-hats-skill","juanallo","A structured decision-debate skill for running Edward de Bono-style six hats sessions with an AI agent. It walks a topic through facts, intuition, upside, risk, alternatives, and final moderation so you get a practical recommendation instead of a loose brainstorm.",null,"Python",36,10,33,0,1,3,42.92,false,"main",true,[],"2026-06-12 04:01:31","# Six Hats Skill\n\nA structured decision-debate skill for running Edward de Bono-style six hats sessions with an AI agent. It walks a topic through facts, intuition, upside, risk, alternatives, and final moderation so you get a practical recommendation instead of a loose brainstorm.\n\n## What It Does\n\nThe skill runs three sequential rounds using these roles:\n\n- **White Hat**: facts, known information, and unknowns\n- **Red Hat**: intuition, emotional reactions, and gut checks\n- **Yellow Hat**: benefits, upside, and reasons the idea could work\n- **Black Hat**: risks, objections, failure modes, and downsides\n- **Green Hat**: alternatives, reframes, and creative options\n- **Blue Hat**: moderation, synthesis, final recommendation, agreements, tensions, and next steps\n\nThe hats run in order so each perspective can build on the previous ones. Blue Hat moderates and synthesizes rather than contributing a normal debate statement during each round.\n\n## When To Use It\n\nUse this skill when you want to pressure-test a decision, strategy, plan, architecture choice, product direction, or career move. It works best when the prompt is framed as a concrete decision or question.\n\nExample prompts:\n\n```text\nRun a six hats debate on whether we should migrate this app from REST to GraphQL.\nWrite the output to .\u002Fdecisions.\n```\n\n```text\nUse six hats to evaluate whether I should keep working on frontend tooling or move to an AI company.\nSave it in .\u002Fexamples.\n```\n\n## Examples\n\nBelow are completed debates plus screenshots of typical agent conversations when using this skill.\n\n### Career decision — frontend tooling vs. AI companies\n\nPressure-tests staying in frontend tooling versus moving toward an AI company: tradeoffs, risks, and synthesis.\n\n**Summary:** A principal frontend engineer debates staying deep in Sass and CSS tooling versus joining the AI boom. White and Yellow underline strong demand for senior UI talent and upside in AI interfaces; Black warns about hype, startup churn, narrower “dashboard + chat” work, and interview pressure to prove AI literacy. Green breaks the binary (AI + frontend infra vendors, internal AI projects, positioning at the intersection). Red names fatigue with the old lane versus fear of chasing shiny objects. Across three rounds, Blue Hat lands on phased optionality—not an immediate pivot: ship a small AI-powered UI experiment to see how it feels, run a few exploratory interviews for real compensation and role data, talk openly with your current employer about AI-adjacent growth, then judge any offer on team, product, and day-to-day frontend work rather than the “AI company” label alone.\n\n[![Conversation excerpt: career advice six hats session](examples\u002Fsix-hats-career-advice.png)](examples\u002Fsix-hats-career-advice.md)\n\n**Full markdown debate:** [`examples\u002Fsix-hats-career-advice.md`](examples\u002Fsix-hats-career-advice.md)\n\n### Technology direction — React in 2026\n\nExplores React’s role, ecosystem tradeoffs, and strategic framing for frontend work in 2026.\n\n**Summary:** The debate weighs React’s institutional advantages—talent pool, npm ecosystem, React 19, compiler maturity, RSC-driven bundle wins in content-heavy apps—against shared unease: a harder mental model, Next.js\u002FVercel coupling and roadmap risk, perceived migration churn, and how much benchmark gaps vs. fine-grained frameworks translate to users. Green repeatedly widens the frame (Rust compile-to-native options, server-first\u002Flive views, AI-written UI changing cost and mental models). Blue Hat’s recommendation is defensive maturity: React is still a reasonable default for many teams, but treat the stack as leverage you manage, not dogma—keep server\u002Fclient boundaries explicit, avoid unnecessary vendor lock-in, instrument real performance, and stay mobile enough that ecosystem shifts do not trap you.\n\n[![Conversation excerpt: React 2026 six hats session](examples\u002Fsix-hats-react-2026.png)](examples\u002Fsix-hats-react-2026.md)\n\n**Full markdown debate:** [`examples\u002Fsix-hats-react-2026.md`](examples\u002Fsix-hats-react-2026.md)\n\n## Installation\n\nClone this repository into the skills directory used by your agent runtime.\n\nFor Claude-style skills:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fjuanallo\u002Fsix-hats-skill ~\u002F.claude\u002Fskills\u002Fsix-hats\n```\n\nFor agent skills loaded from `~\u002F.agents\u002Fskills`:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fjuanallo\u002Fsix-hats-skill ~\u002F.agents\u002Fskills\u002Fsix-hats\n```\n\nFor Cursor personal skills, use Cursor's personal skill directory:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fjuanallo\u002Fsix-hats-skill ~\u002F.cursor\u002Fskills\u002Fsix-hats\n```\n\nIf you already cloned the repository somewhere else, copy or symlink the whole directory so `SKILL.md` lives directly inside the final `six-hats` folder:\n\n```bash\nln -s \u002Fpath\u002Fto\u002Fsix-hats-skill ~\u002F.claude\u002Fskills\u002Fsix-hats\n```\n\nThe important directory shape is:\n\n```text\nsix-hats\u002F\n|-- SKILL.md\n|-- README.md\n|-- examples\u002F\n`-- scripts\u002F\n```\n\n## Usage\n\nAfter installation, ask your agent for a \"six hats\" or \"six hats debate\" session. Include:\n\n1. The decision, plan, or question to debate.\n2. The output directory where the generated debate should be written.\n\nThe skill writes a markdown file named like:\n\n```text\ndebate-YYYYMMDD_HHMMSS.md\n```\n\nThe generated file contains:\n\n- Final recommendation from Blue Hat\n- Key agreements across hats\n- Unresolved tensions\n- Suggested next steps\n- Three rounds of hat-by-hat debate\n- Raw debate data\n\n## Optional Script\n\n[`scripts\u002Fsix_hats_debate.py`](scripts\u002Fsix_hats_debate.py) is reference scaffolding for expected inputs, output naming, and batch-oriented usage:\n\n```bash\npython3 scripts\u002Fsix_hats_debate.py \"Should we launch v2?\" \".\u002Fdecisions\"\n```\n\nThe script does not run the full conversational debate by itself; it writes a timestamped markdown **stub** you can overwrite after running the skill. The main workflow lives in [`SKILL.md`](SKILL.md).\n","juanallo\u002Fsix-hats-skill 是一个用于与AI代理进行爱德华·德·波诺风格的六顶思考帽会议的结构化决策辩论工具。该项目通过事实、直觉、优点、风险、替代方案和最终调解六个角色，对议题进行全面分析，从而提供实用建议而非松散的头脑风暴。核心功能包括按照白帽（事实）、红帽（直觉）、黄帽（优点）、黑帽（风险）、绿帽（替代方案）和蓝帽（调解）的顺序进行三轮讨论，确保每种视角都能基于前一轮的结果逐步构建。该技能适用于需要对决策、策略、计划、架构选择、产品方向或职业变动等进行压力测试的场景，尤其当问题被具体化为某个决定或问题时效果最佳。",2,"2026-06-11 04:02:50","CREATED_QUERY"]