[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DM456FDB1RXYTZ9DAPNWV5":3,"skill-same:01M7DM456FDB1RXYTZ9DAPNWV5":66},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7DM456FDB1RXYTZ9DAPNWV5","idea-os",null,"Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with mermaid user journey and kill criteria.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fidea-os\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: idea-os\ndescription: \"Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with mermaid user journey and kill criteria.\"\ncategory: product-management\nrisk: safe\nsource: community\nsource_repo: Slashworks-biz\u002Fidea-os\nsource_type: community\ndate_added: \"2026-04-18\"\nauthor: Slashworks-biz\ntags: [product-management, prd, market-research, mvp, idea-validation, jtbd, swot, competitor-analysis, founder, non-technical]\ntools: [claude, cursor, gemini]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# idea-os\n\nAn operating system for turning a raw idea into a build-ready plan. Takes a rough problem statement and produces four files: clarifying questions, deep research, a PRD, and a phased execution plan with platform\u002Fstack picks, a user-journey diagram, and kill criteria.\n\n## Overview\n\nidea-os is a 5-phase sequential pipeline where each phase's output feeds the next — research shapes the PRD, PRD shapes the plan, plan's kill criteria tie back to research insights. Unlike single-command PRD generators, idea-os refuses to write a PRD until research is done, and refuses to write a plan until the PRD is stable. Depth and vocabulary adapt to a two-axis classification (complexity × builder sophistication) so a first-time builder isn't drowning in jargon and a founder gets full rigor.\n\nSource: https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os — full skill, 11 reference files, 4 asset templates, and a 590-line worked example.\n\n## When to Use\n\n- Use when a user shares a raw product idea or problem statement and wants a structured pipeline from clarifying questions through deep research, PRD, and a phased execution plan.\n- Use when the user says \"I have an idea for…\", \"help me build X\", \"validate and plan this concept\", or \"what should I build?\" — and wants files they can take forward, not a one-shot answer.\n- Use when a non-technical founder, PM, or hobbyist needs structure to bridge the gap between \"idea\" and \"Monday morning's build queue\".\n- Do **not** use for quick sanity-check feedback on a half-formed idea (use `idea-refine` instead) or for editing an existing PRD (use `product-management` instead).\n\n## How It Works\n\n### Phase 1 — Triage\n\nClassify the idea on two axes before anything else. Depth of research\u002FPRD\u002Fplan and question count scale with complexity; vocabulary scales with sophistication.\n\n- **Idea tier (T1\u002FT2\u002FT3)** — T1 = weekend utility, T2 = SaaS MVP or AI wrapper, T3 = marketplace \u002F B2B SaaS \u002F regulated.\n- **Sophistication (S1\u002FS2\u002FS3)** — S1 = non-technical, no framework names; S2 = hobbyist, introduce frameworks with definitions; S3 = founder\u002Fsenior PM, full vocabulary.\n\nState the classification in one line (e.g. \"T2 · S2 — moderate SaaS, builder has shipped before\") before proceeding.\n\n### Phase 2 — Clarify\n\nWrite `questions.md` with 4–18 questions (count scales with complexity), grouped: Who and Pain · Scope and Wedge · Constraints and Goals. Every question must be actionable — the answer has to change what you build. Generic questions are rejected.\n\nAfter writing, stop and wait for answers. Do not proceed to research until answered or autonomous-mode assumptions are declared.\n\n### Phase 3 — Research\n\nWrite `research.md` using WebSearch + WebFetch. Minimum: 5 WebSearches, 2 WebFetches on named competitors, 1 source per TAM number, date on every source. Anything unsourced gets flagged `[assumption]`.\n\nRequired sections: problem validation, JTBD, market (TAM\u002FSAM\u002FSOM top-down + bottom-up), competitors (direct\u002Findirect\u002Fsubstitutes + positioning map), SWOT, distribution (first-100-users channel fit), risks, and 3–7 non-obvious insights.\n\n### Phase 4 — PRD\n\nWrite `PRD.md` with: falsifiable problem statement, named personas, ranked JTBD, non-goals (mandatory — it's where bad PRDs die), leading and lagging metrics.\n\n### Phase 5 — Plan\n\nWrite `plan.md` with: user journey (text + mermaid), platform recommendation tied to research findings, stack in conservative\u002Fmodern\u002Fcutting-edge matrix, phased build (MVP → v1 → target) with kill criteria per phase and first-100-users distribution per phase, metrics per phase, and 3–5 immediate next actions.\n\n## Limitations\n\n- Requires user input between phases for best results; if answers are missing, outputs depend on explicit assumptions.\n- Produces planning artifacts (`questions.md`, `research.md`, `PRD.md`, `plan.md`) but does not execute build or deployment work.\n- Source quality determines output quality; weak or outdated references can reduce recommendation accuracy.\n- Better suited to new-idea validation and early planning than late-stage optimization of an existing shipped product.\n\n## Examples\n\n### Example 1: Non-technical founder with a consumer-app idea\n\nUser: \"I want to build a habit tracker for people with ADHD.\"\n\nidea-os classifies T2 · S1, writes 8 plain-language clarifying questions, runs research with sourced competitor pricing and community signal from ADHD subreddits, produces a PRD with ADHD-specific non-goals (no streaks, no punishment mechanics), and a plan with a single-screen MVP and a kill criterion tied to 14-day retention.\n\n### Example 2: Founder with a B2B SaaS idea\n\nUser: \"I'm thinking about procurement software for mid-market manufacturers.\"\n\nidea-os classifies T3 · S3, writes 18 questions including procurement-cycle specifics, runs research with Wardley-map option and Porter 5 forces, produces a PRD with tiered personas (buyer\u002Fapprover\u002FIT), and a plan with a phase-1 kill criterion tied to paid-pilot close rate.\n\n## Full source\n\nFull 11-reference skill, 4 asset templates, worked example, and MIT license at https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os. This antigravity entry is a reference copy — the upstream repo is where ongoing development lives.\n","# idea-os\n\nAn operating system for turning a raw idea into a build-ready plan. Takes a rough problem statement and produces four files: clarifying questions, deep research, a PRD, and a phased execution plan with platform\u002Fstack picks, a user-journey diagram, and kill criteria.\n\n## Overview\n\nidea-os is a 5-phase sequential pipeline where each phase's output feeds the next — research shapes the PRD, PRD shapes the plan, plan's kill criteria tie back to research insights. Unlike single-command PRD generators, idea-os refuses to write a PRD until research is done, and refuses to write a plan until the PRD is stable. Depth and vocabulary adapt to a two-axis classification (complexity × builder sophistication) so a first-time builder isn't drowning in jargon and a founder gets full rigor.\n\nSource: https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os — full skill, 11 reference files, 4 asset templates, and a 590-line worked example.\n\n## When to Use\n\n- Use when a user shares a raw product idea or problem statement and wants a structured pipeline from clarifying questions through deep research, PRD, and a phased execution plan.\n- Use when the user says \"I have an idea for…\", \"help me build X\", \"validate and plan this concept\", or \"what should I build?\" — and wants files they can take forward, not a one-shot answer.\n- Use when a non-technical founder, PM, or hobbyist needs structure to bridge the gap between \"idea\" and \"Monday morning's build queue\".\n- Do **not** use for quick sanity-check feedback on a half-formed idea (use `idea-refine` instead) or for editing an existing PRD (use `product-management` instead).\n\n## How It Works\n\n### Phase 1 — Triage\n\nClassify the idea on two axes before anything else. Depth of research\u002FPRD\u002Fplan and question count scale with complexity; vocabulary scales with sophistication.\n\n- **Idea tier (T1\u002FT2\u002FT3)** — T1 = weekend utility, T2 = SaaS MVP or AI wrapper, T3 = marketplace \u002F B2B SaaS \u002F regulated.\n- **Sophistication (S1\u002FS2\u002FS3)** — S1 = non-technical, no framework names; S2 = hobbyist, introduce frameworks with definitions; S3 = founder\u002Fsenior PM, full vocabulary.\n\nState the classification in one line (e.g. \"T2 · S2 — moderate SaaS, builder has shipped before\") before proceeding.\n\n### Phase 2 — Clarify\n\nWrite `questions.md` with 4–18 questions (count scales with complexity), grouped: Who and Pain · Scope and Wedge · Constraints and Goals. Every question must be actionable — the answer has to change what you build. Generic questions are rejected.\n\nAfter writing, stop and wait for answers. Do not proceed to research until answered or autonomous-mode assumptions are declared.\n\n### Phase 3 — Research\n\nWrite `research.md` using WebSearch + WebFetch. Minimum: 5 WebSearches, 2 WebFetches on named competitors, 1 source per TAM number, date on every source. Anything unsourced gets flagged `[assumption]`.\n\nRequired sections: problem validation, JTBD, market (TAM\u002FSAM\u002FSOM top-down + bottom-up), competitors (direct\u002Findirect\u002Fsubstitutes + positioning map), SWOT, distribution (first-100-users channel fit), risks, and 3–7 non-obvious insights.\n\n### Phase 4 — PRD\n\nWrite `PRD.md` with: falsifiable problem statement, named personas, ranked JTBD, non-goals (mandatory — it's where bad PRDs die), leading and lagging metrics.\n\n### Phase 5 — Plan\n\nWrite `plan.md` with: user journey (text + mermaid), platform recommendation tied to research findings, stack in conservative\u002Fmodern\u002Fcutting-edge matrix, phased build (MVP → v1 → target) with kill criteria per phase and first-100-users distribution per phase, metrics per phase, and 3–5 immediate next actions.\n\n## Limitations\n\n- Requires user input between phases for best results; if answers are missing, outputs depend on explicit assumptions.\n- Produces planning artifacts (`questions.md`, `research.md`, `PRD.md`, `plan.md`) but does not execute build or deployment work.\n- Source quality determines output quality; weak or outdated references can reduce recommendation accuracy.\n- Better suited to new-idea validation and early planning than late-stage optimization of an existing shipped product.\n\n## Examples\n\n### Example 1: Non-technical founder with a consumer-app idea\n\nUser: \"I want to build a habit tracker for people with ADHD.\"\n\nidea-os classifies T2 · S1, writes 8 plain-language clarifying questions, runs research with sourced competitor pricing and community signal from ADHD subreddits, produces a PRD with ADHD-specific non-goals (no streaks, no punishment mechanics), and a plan with a single-screen MVP and a kill criterion tied to 14-day retention.\n\n### Example 2: Founder with a B2B SaaS idea\n\nUser: \"I'm thinking about procurement software for mid-market manufacturers.\"\n\nidea-os classifies T3 · S3, writes 18 questions including procurement-cycle specifics, runs research with Wardley-map option and Porter 5 forces, produces a PRD with tiered personas (buyer\u002Fapprover\u002FIT), and a plan with a phase-1 kill criterion tied to paid-pilot close rate.\n\n## Full source\n\nFull 11-reference skill, 4 asset templates, worked example, and MIT license at https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os. This antigravity entry is a reference copy — the upstream repo is where ongoing development lives.\n",{"name":5,"risk":24,"tags":25,"tools":36,"author":40,"source":41,"license":15,"category":26,"date_added":42,"description":7,"source_repo":43,"source_type":41,"license_source":44},"safe",[26,27,28,29,30,31,32,33,34,35],"product-management","prd","market-research","mvp","idea-validation","jtbd","swot","competitor-analysis","founder","non-technical",[37,38,39],"claude","cursor","gemini","Slashworks-biz","community","2026-04-18","Slashworks-biz\u002Fidea-os","https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fidea-os",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill idea-os",{"tool":58,"command":59},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill idea-os",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill idea-os","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fidea-os\u002FSKILL.md",true,[],[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]