[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77G7GADADW422C8W4WTCT2P":3,"skill-same:01M77G7GADADW422C8W4WTCT2P":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M77G7GADADW422C8W4WTCT2P","brand-discovery",null,"Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).","viseshrp\u002Fai-skills-archive","viseshrp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11642379?v=4","01M77FS5SES3C3PAVNXVRH1WVJ","Visesh Rajendraprasad","01M77FS5T6KA31CXA6K10TYFDC",0,"MIT","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Faffaan-m__ECC\u002Fsnapshot\u002F.agents\u002Fskills\u002Fbrand-discovery\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: brand-discovery\ndescription: >-\n  Use when a brand needs to discover or articulate its identity through\n  structured multi-session interviews. Covers purpose, positioning, audience,\n  personality, voice, narrative, and founder-brand tension across 8 modules\n  using laddering, 5 Whys, and projective techniques. Produces a resumable\n  session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).\nlicense: MIT\n---\n\n# Brand Discovery\n\nUse this skill to conduct a structured, adaptive brand identity interview.\nThe goal is a complete `90_SYNTHESIS.md` — a master brandbook the\norganization can use to brief designers, writers, and external\ncollaborators.\n\nThe interview runs across multiple sessions. Capture answers to disk as you\ngo so that no elicited knowledge is lost when a conversation ends, and so a\nlater session can resume from where the last one stopped.\n\n## When to Activate\n\n- A brand is being created, repositioned, or needs a written identity reference to brief collaborators.\n- Multiple sessions are expected — the conversation will span days or weeks.\n- Multiple founders or stakeholders need individual interviews before a reconciliation pass.\n- The user wants a structured, repeatable method rather than an ad-hoc chat.\n- Existing brand documentation is scattered, implicit, or founder-dependent and needs to be made explicit.\n\n## Session start protocol\n\nOn every activation, perform these steps **before** asking any interview\nquestion:\n\n1. **Check for prior progress.** Look for an existing set of module files\n   and a `state.json` checkpoint in the project's brand-identity directory.\n   If none exists, this is a fresh start — confirm the brand name,\n   participants, and where to save the brand-identity files, then begin at\n   the first module.\n2. **Read the current module file** if one is in progress, and scan its Raw\n   section for previously captured answers.\n3. **Report to the user** in two or three sentences: which module we are\n   in, its status, and what remains. Then ask: \"Continue here, or switch\n   module?\"\n\n## Interview discipline\n\nApply these rules throughout every module:\n\n1. **One question at a time.** Never present a list of questions.\n2. **After each answer:** short paraphrase → one deepening probe OR close\n   the thread if the topic is saturated. Never move on silently.\n3. **Laddering:** for every \"what\" answer, follow with \"Why does that\n   matter to you?\" until a core value surfaces (typically two to four\n   iterations).\n4. **5 Whys:** for beliefs or positioning claims — push until the root\n   reason, not the surface declaration, is on the table.\n5. **Detect thin answers:** if generic, jargon-heavy, or vague, ask for\n   one concrete example, a client story, or a number.\n6. **Projective techniques** (use once per module to break a plateau):\n   - \"If the brand were a person, how would they walk into a room?\"\n   - Brand obituary: \"If the organization closed in five years, what would\n     customers miss? What would you regret not having said?\"\n   - Competitive contrast: \"Name one peer you admire but would never want\n     to become. What specifically makes them the wrong model?\"\n7. **Saturation signal:** when two consecutive probes produce no new\n   information, summarise and close the module.\n8. **End of module:** write a structured module file with two sections:\n   - `## Raw` — verbatim quotes and examples.\n   - `## Synthesis` — your interpretation, three candidate formulations,\n     open questions, contradictions between participants.\n   Then update the `state.json` checkpoint (see State protocol below).\n\n## Module sequence\n\n| File | Label | Frameworks used |\n|------|-------|-----------------|\n| `10_purpose-why.md` | Purpose \u002F Why | Sinek Golden Circle, Lencioni |\n| `20_positioning.md` | Positioning | Dunford \"Obviously Awesome\", Moore template |\n| `30_audience-niche.md` | Audience & Niche | Baker \"Business of Expertise\", ICP |\n| `40_personality-archetype.md` | Personality & Archetype | Mark & Pearson 12 archetypes, J. Aaker 5 dims |\n| `50_voice-tone.md` | Voice & Tone | Brand voice guidelines |\n| `60_narrative-story.md` | Narrative \u002F Story | Neumeier trueline, brand story arc |\n| `70_founder-tension.md` | Founder Brands vs Studio Brand | Enns \"Win Without Pitching\" |\n| `90_SYNTHESIS.md` | Master Brandbook | Kapferer prism, Aaker brand system |\n\nComplete modules in order. Honour a user request to jump modules and note\nthe skip in `state.json`.\n\n## State write protocol\n\nAfter each module reaches saturation or done status, write two files:\n\n**Module file** at `modules\u002F{moduleFile}` — full Raw and Synthesis content.\n\n**`state.json`** — a lightweight checkpoint so a later session can resume.\nUpdate `completedModules`, `inProgressModule`, `nextModule`, `lastUpdated`.\nSchema:\n\n```json\n{\n  \"session\": \"{brand_name}-brand-{YYYY-MM}\",\n  \"outputPath\": \"{path_to_brand_identity_directory}\",\n  \"completedModules\": [],\n  \"inProgressModule\": \"10_purpose-why.md\",\n  \"nextModule\": \"20_positioning.md\",\n  \"participants\": [\"founder-A\"],\n  \"lastUpdated\": \"{ISO-8601}\"\n}\n```\n\nAfter writing, confirm: \"Module X saved. State updated. Next: Y.\"\n\n**Terminal module (90_SYNTHESIS.md):** when writing the final synthesis,\nset `inProgressModule` to `\"90_SYNTHESIS.md\"` and `nextModule` to `null`\nin `state.json`. After writing, set `completedModules` to include\n`\"90_SYNTHESIS.md\"`, then set `inProgressModule` to `null` — leaving it\npopulated would cause a future resumption to treat the completed brandbook\nas still in progress. Confirm: \"Brandbook complete. All modules saved.\"\n\n## Multi-founder mode\n\nWhen more than one founder participates, write each founder's answers to\n`founders\u002F{participant}.md` instead of the main module files. Validate the\n`participant` name before writing: accept only alphanumeric characters and\nhyphens (e.g. `founder-a`, `anna`); reject names containing path separators\n(`\u002F`, `\\`, `..`) or special characters. Validate `moduleFile` against the\nenumerated module sequence (10 through 90 only). Validate `outputPath` to\nensure it is an absolute path within the project directory — reject relative\npaths and paths that escape via `..` segments. After all founders complete a\nmodule, run a reconciliation pass: summarise convergences and divergences in\nthe module file, flag \"productive tensions\" for the group alignment workshop.\n\n## Anti-Patterns\n\n- **Starting without reading state first.** Every session must open by checking for existing module files and `state.json`. Skipping this loses all continuity from prior sessions.\n- **Asking multiple questions at once.** One question at a time is not optional — lists produce checklist answers, not real insight.\n- **Moving to Synthesis before saturation.** If the last two probes produced no new information, the module is done. If they did — it isn't.\n- **Skipping multi-founder reconciliation.** When multiple stakeholders are involved, individual interviews must complete before reconciliation. Discussing the brand collectively first introduces anchoring bias.\n- **Treating this as a one-shot session.** This skill is designed for multiple sessions. Rushing to `90_SYNTHESIS.md` in one conversation produces shallow output.\n\n## Related Skills\n\n- `competitive-platform-analysis` — after brand-discovery establishes the positioning brief, use this to scope and categorise the competitor set.\n- `brand-voice` (ECC) — if the brand-discovery voice-and-tone module needs a separate, source-derived writing-style profile.\n","# Brand Discovery\n\nUse this skill to conduct a structured, adaptive brand identity interview.\nThe goal is a complete `90_SYNTHESIS.md` — a master brandbook the\norganization can use to brief designers, writers, and external\ncollaborators.\n\nThe interview runs across multiple sessions. Capture answers to disk as you\ngo so that no elicited knowledge is lost when a conversation ends, and so a\nlater session can resume from where the last one stopped.\n\n## When to Activate\n\n- A brand is being created, repositioned, or needs a written identity reference to brief collaborators.\n- Multiple sessions are expected — the conversation will span days or weeks.\n- Multiple founders or stakeholders need individual interviews before a reconciliation pass.\n- The user wants a structured, repeatable method rather than an ad-hoc chat.\n- Existing brand documentation is scattered, implicit, or founder-dependent and needs to be made explicit.\n\n## Session start protocol\n\nOn every activation, perform these steps **before** asking any interview\nquestion:\n\n1. **Check for prior progress.** Look for an existing set of module files\n   and a `state.json` checkpoint in the project's brand-identity directory.\n   If none exists, this is a fresh start — confirm the brand name,\n   participants, and where to save the brand-identity files, then begin at\n   the first module.\n2. **Read the current module file** if one is in progress, and scan its Raw\n   section for previously captured answers.\n3. **Report to the user** in two or three sentences: which module we are\n   in, its status, and what remains. Then ask: \"Continue here, or switch\n   module?\"\n\n## Interview discipline\n\nApply these rules throughout every module:\n\n1. **One question at a time.** Never present a list of questions.\n2. **After each answer:** short paraphrase → one deepening probe OR close\n   the thread if the topic is saturated. Never move on silently.\n3. **Laddering:** for every \"what\" answer, follow with \"Why does that\n   matter to you?\" until a core value surfaces (typically two to four\n   iterations).\n4. **5 Whys:** for beliefs or positioning claims — push until the root\n   reason, not the surface declaration, is on the table.\n5. **Detect thin answers:** if generic, jargon-heavy, or vague, ask for\n   one concrete example, a client story, or a number.\n6. **Projective techniques** (use once per module to break a plateau):\n   - \"If the brand were a person, how would they walk into a room?\"\n   - Brand obituary: \"If the organization closed in five years, what would\n     customers miss? What would you regret not having said?\"\n   - Competitive contrast: \"Name one peer you admire but would never want\n     to become. What specifically makes them the wrong model?\"\n7. **Saturation signal:** when two consecutive probes produce no new\n   information, summarise and close the module.\n8. **End of module:** write a structured module file with two sections:\n   - `## Raw` — verbatim quotes and examples.\n   - `## Synthesis` — your interpretation, three candidate formulations,\n     open questions, contradictions between participants.\n   Then update the `state.json` checkpoint (see State protocol below).\n\n## Module sequence\n\n| File | Label | Frameworks used |\n|------|-------|-----------------|\n| `10_purpose-why.md` | Purpose \u002F Why | Sinek Golden Circle, Lencioni |\n| `20_positioning.md` | Positioning | Dunford \"Obviously Awesome\", Moore template |\n| `30_audience-niche.md` | Audience & Niche | Baker \"Business of Expertise\", ICP |\n| `40_personality-archetype.md` | Personality & Archetype | Mark & Pearson 12 archetypes, J. Aaker 5 dims |\n| `50_voice-tone.md` | Voice & Tone | Brand voice guidelines |\n| `60_narrative-story.md` | Narrative \u002F Story | Neumeier trueline, brand story arc |\n| `70_founder-tension.md` | Founder Brands vs Studio Brand | Enns \"Win Without Pitching\" |\n| `90_SYNTHESIS.md` | Master Brandbook | Kapferer prism, Aaker brand system |\n\nComplete modules in order. Honour a user request to jump modules and note\nthe skip in `state.json`.\n\n## State write protocol\n\nAfter each module reaches saturation or done status, write two files:\n\n**Module file** at `modules\u002F{moduleFile}` — full Raw and Synthesis content.\n\n**`state.json`** — a lightweight checkpoint so a later session can resume.\nUpdate `completedModules`, `inProgressModule`, `nextModule`, `lastUpdated`.\nSchema:\n\n```json\n{\n  \"session\": \"{brand_name}-brand-{YYYY-MM}\",\n  \"outputPath\": \"{path_to_brand_identity_directory}\",\n  \"completedModules\": [],\n  \"inProgressModule\": \"10_purpose-why.md\",\n  \"nextModule\": \"20_positioning.md\",\n  \"participants\": [\"founder-A\"],\n  \"lastUpdated\": \"{ISO-8601}\"\n}\n```\n\nAfter writing, confirm: \"Module X saved. State updated. Next: Y.\"\n\n**Terminal module (90_SYNTHESIS.md):** when writing the final synthesis,\nset `inProgressModule` to `\"90_SYNTHESIS.md\"` and `nextModule` to `null`\nin `state.json`. After writing, set `completedModules` to include\n`\"90_SYNTHESIS.md\"`, then set `inProgressModule` to `null` — leaving it\npopulated would cause a future resumption to treat the completed brandbook\nas still in progress. Confirm: \"Brandbook complete. All modules saved.\"\n\n## Multi-founder mode\n\nWhen more than one founder participates, write each founder's answers to\n`founders\u002F{participant}.md` instead of the main module files. Validate the\n`participant` name before writing: accept only alphanumeric characters and\nhyphens (e.g. `founder-a`, `anna`); reject names containing path separators\n(`\u002F`, `\\`, `..`) or special characters. Validate `moduleFile` against the\nenumerated module sequence (10 through 90 only). Validate `outputPath` to\nensure it is an absolute path within the project directory — reject relative\npaths and paths that escape via `..` segments. After all founders complete a\nmodule, run a reconciliation pass: summarise convergences and divergences in\nthe module file, flag \"productive tensions\" for the group alignment workshop.\n\n## Anti-Patterns\n\n- **Starting without reading state first.** Every session must open by checking for existing module files and `state.json`. Skipping this loses all continuity from prior sessions.\n- **Asking multiple questions at once.** One question at a time is not optional — lists produce checklist answers, not real insight.\n- **Moving to Synthesis before saturation.** If the last two probes produced no new information, the module is done. If they did — it isn't.\n- **Skipping multi-founder reconciliation.** When multiple stakeholders are involved, individual interviews must complete before reconciliation. Discussing the brand collectively first introduces anchoring bias.\n- **Treating this as a one-shot session.** This skill is designed for multiple sessions. Rushing to `90_SYNTHESIS.md` in one conversation produces shallow output.\n\n## Related Skills\n\n- `competitive-platform-analysis` — after brand-discovery establishes the positioning brief, use this to scope and categorise the competitor set.\n- `brand-voice` (ECC) — if the brand-discovery voice-and-tone module needs a separate, source-derived writing-style profile.\n",{"name":5,"license":15,"description":7},"main","2550866e372116f9d9b44ba2cd5c66a6860f3040","archives\u002Faffaan-m__ECC\u002Fsnapshot\u002F.agents\u002Fskills\u002Fbrand-discovery","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive","https:\u002F\u002Fgithub.com\u002Fviseshrp","Full-stack engineer by day, building apps and CLI tools.\r\nSelf-hoster by night, running a tiny Raspberry Pi datacenter.","2026-11-10 11:20:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add viseshrp\u002Fai-skills-archive --skill brand-discovery",{"tool":37,"command":38},"bunx","bunx skills add viseshrp\u002Fai-skills-archive --skill brand-discovery",{"tool":40,"command":41},"pnpm","pnpm dlx skills add viseshrp\u002Fai-skills-archive --skill brand-discovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Faffaan-m__ECC\u002Fsnapshot\u002F.agents\u002Fskills\u002Fbrand-discovery\u002FSKILL.md",true,[],[46,54,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":50,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77MKJBE97JWGCWFH915STTG","test-audit","Audit new or existing tests for behavioral value, duplication, implementation coupling, brittleness, and test-only production seams. Use when writing, changing, reviewing, or pruning tests, including an independent final review of a test diff.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Fskills\u002Ftest-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Fskills\u002Ftest-audit\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77MJ0851ZFCXSBX5YX0CEZ2","last30days","Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fmvanhorn__last30days-skill\u002Fsnapshot\u002Fskills\u002Flast30days\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77MHW9RACV0XNY75ZSJJD56","karpathy-guidelines","Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fmultica-ai__andrej-karpathy-skills\u002Fsnapshot\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77M349AKHE5GDY8ATT5PP5W","port-github-app-to-origin","Plans the port of an existing GitHub App to a Cursor Origin App. Use when the task is to bring a GitHub App to Origin or compare what it uses against the Origin API. Reads the app's needs out of its code, maps them onto the live Origin spec, and writes a porting brief with feedback for Cursor. Planning only.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fcursor__plugins\u002Fsnapshot\u002Forigin-apps\u002Fskills\u002Fport-github-app-to-origin\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77M30DPGNPY4BDMB1SEHJSK","origin-api","Routes questions about the Cursor Origin API to the right section of the Origin docs and names the few rules to check first. Use when a task mentions Origin, the Origin API, Origin Apps, or Origin webhooks, including creating an Origin App, authenticating as one, calling Origin endpoints, or handling Origin webhook deliveries.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fcursor__plugins\u002Fsnapshot\u002Forigin-apps\u002Fskills\u002Forigin-api\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77KTXW5T1KVMHX71FMBT7BR","i-have-adhd","Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with \u002Fi-have-adhd; stays on until \"stop adhd mode\".","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fayghri__i-have-adhd\u002Fsnapshot\u002Fskills\u002Fi-have-adhd\u002FSKILL.md",[],[]]