[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JCPRTVFQK0DT09NAFW07DZ":3,"skill-same:01M6JCPRTVFQK0DT09NAFW07DZ":88},{"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":33,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6JCPRTVFQK0DT09NAFW07DZ","brand-voice",null,"Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fbrand-voice\u002FSKILL.md",[17,22,25,30],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":31,"categoryName":32,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"voice","brand","brand voice","social","source","consistency","posts","essays","reuse","style","outreach","across","writing style","writing","build","use","site","notes","workflows","launch","2026-11-10 10:12:30",false,"---\nname: brand-voice\ndescription: Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.\norigin: ECC\n---\n\n# Brand Voice\n\nBuild a durable voice profile from real source material, then use that profile everywhere instead of re-deriving style from scratch or defaulting to generic AI copy.\n\n## When to Activate\n\n- the user wants content or outreach in a specific voice\n- writing for X, LinkedIn, email, launch posts, threads, or product updates\n- adapting a known author's tone across channels\n- the existing content lane needs a reusable style system instead of one-off mimicry\n\n## Source Priority\n\nUse the strongest real source set available, in this order:\n\n1. recent original X posts and threads\n2. articles, essays, memos, launch notes, or newsletters\n3. real outbound emails or DMs that worked\n4. product docs, changelogs, README framing, and site copy\n\nDo not use generic platform exemplars as source material.\n\n## Collection Workflow\n\n1. Gather 5 to 20 representative samples when available.\n2. Prefer recent material over old material unless the user says the older writing is more canonical.\n3. Separate \"public launch voice\" from \"private working voice\" if the source set clearly splits.\n4. If live X access is available, use `x-api` to pull recent original posts before drafting.\n5. If site copy matters, include the current ECC landing page and repo\u002Fplugin framing.\n\n## What to Extract\n\n- rhythm and sentence length\n- compression vs explanation\n- capitalization norms\n- parenthetical use\n- question frequency and purpose\n- how sharply claims are made\n- how often numbers, mechanisms, or receipts show up\n- how transitions work\n- what the author never does\n\n## Output Contract\n\nProduce a reusable `VOICE PROFILE` block that downstream skills can consume directly. Use the schema in [references\u002Fvoice-profile-schema.md](references\u002Fvoice-profile-schema.md).\n\nKeep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.\n\n## Affaan \u002F ECC Defaults\n\nIf the user wants Affaan \u002F ECC voice and live sources are thin, start here unless newer source material overrides it:\n\n- direct, compressed, concrete\n- specifics, mechanisms, receipts, and numbers beat adjectives\n- parentheticals are for qualification, narrowing, or over-clarification\n- capitalization is conventional unless there is a real reason to break it\n- questions are rare and should not be used as bait\n- tone can be sharp, blunt, skeptical, or dry\n- transitions should feel earned, not smoothed over\n\n## Hard Bans\n\nDelete and rewrite any of these:\n\n- fake curiosity hooks\n- \"not X, just Y\"\n- \"no fluff\"\n- forced lowercase\n- LinkedIn thought-leader cadence\n- bait questions\n- \"Excited to share\"\n- generic founder-journey filler\n- corny parentheticals\n\n## Persistence Rules\n\n- Reuse the latest confirmed `VOICE PROFILE` across related tasks in the same session.\n- If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface.\n- Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.\n\n## Downstream Use\n\nUse this skill before or inside:\n\n- `content-engine`\n- `crosspost`\n- `lead-intelligence`\n- article or launch writing\n- cold or warm outbound across X, LinkedIn, and email\n\nIf another skill already has a partial voice capture section, this skill is the canonical source of truth.\n","# Brand Voice\n\nBuild a durable voice profile from real source material, then use that profile everywhere instead of re-deriving style from scratch or defaulting to generic AI copy.\n\n## When to Activate\n\n- the user wants content or outreach in a specific voice\n- writing for X, LinkedIn, email, launch posts, threads, or product updates\n- adapting a known author's tone across channels\n- the existing content lane needs a reusable style system instead of one-off mimicry\n\n## Source Priority\n\nUse the strongest real source set available, in this order:\n\n1. recent original X posts and threads\n2. articles, essays, memos, launch notes, or newsletters\n3. real outbound emails or DMs that worked\n4. product docs, changelogs, README framing, and site copy\n\nDo not use generic platform exemplars as source material.\n\n## Collection Workflow\n\n1. Gather 5 to 20 representative samples when available.\n2. Prefer recent material over old material unless the user says the older writing is more canonical.\n3. Separate \"public launch voice\" from \"private working voice\" if the source set clearly splits.\n4. If live X access is available, use `x-api` to pull recent original posts before drafting.\n5. If site copy matters, include the current ECC landing page and repo\u002Fplugin framing.\n\n## What to Extract\n\n- rhythm and sentence length\n- compression vs explanation\n- capitalization norms\n- parenthetical use\n- question frequency and purpose\n- how sharply claims are made\n- how often numbers, mechanisms, or receipts show up\n- how transitions work\n- what the author never does\n\n## Output Contract\n\nProduce a reusable `VOICE PROFILE` block that downstream skills can consume directly. Use the schema in [references\u002Fvoice-profile-schema.md](references\u002Fvoice-profile-schema.md).\n\nKeep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.\n\n## Affaan \u002F ECC Defaults\n\nIf the user wants Affaan \u002F ECC voice and live sources are thin, start here unless newer source material overrides it:\n\n- direct, compressed, concrete\n- specifics, mechanisms, receipts, and numbers beat adjectives\n- parentheticals are for qualification, narrowing, or over-clarification\n- capitalization is conventional unless there is a real reason to break it\n- questions are rare and should not be used as bait\n- tone can be sharp, blunt, skeptical, or dry\n- transitions should feel earned, not smoothed over\n\n## Hard Bans\n\nDelete and rewrite any of these:\n\n- fake curiosity hooks\n- \"not X, just Y\"\n- \"no fluff\"\n- forced lowercase\n- LinkedIn thought-leader cadence\n- bait questions\n- \"Excited to share\"\n- generic founder-journey filler\n- corny parentheticals\n\n## Persistence Rules\n\n- Reuse the latest confirmed `VOICE PROFILE` across related tasks in the same session.\n- If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface.\n- Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.\n\n## Downstream Use\n\nUse this skill before or inside:\n\n- `content-engine`\n- `crosspost`\n- `lead-intelligence`\n- article or launch writing\n- cold or warm outbound across X, LinkedIn, and email\n\nIf another skill already has a partial voice capture section, this skill is the canonical source of truth.\n",{"name":5,"origin":59,"description":7},"ECC","master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fecc\u002Fbrand-voice",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add S3YED\u002Fappie-kit --skill brand-voice",{"tool":74,"command":75},"bunx","bunx skills add S3YED\u002Fappie-kit --skill brand-voice",{"tool":77,"command":78},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill brand-voice","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fbrand-voice\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fvoice-profile-schema.md","REFERENCE","参考文档",1063,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fbrand-voice\u002Freferences\u002Fvoice-profile-schema.md",[89,121,150,175,205,229],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":102,"publishedAt":54},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[95,98,101],{"categoryNo":96,"categoryName":97,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":99,"categoryName":100,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":129,"publishedAt":54},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[127,128],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":158,"publishedAt":54},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[156,157],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},[131,159,135,160,161,162,137,163,164,165,166,167,168,169,170,171,172,173,174,38],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":185,"publishedAt":54},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[181,184],{"categoryNo":182,"categoryName":183,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[186,187,188,189,190,191,192,193,194,195,196,50,197,198,199,200,201,202,203,204],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":54},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[211],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[52,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228],"quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification","for",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":242,"publishedAt":54},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[235,238,241],{"categoryNo":236,"categoryName":237,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":239,"categoryName":240,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[243,244,245,246,247,248,249,47,189,250,251,137,252,192,253,221,254,255,256,257],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]