[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ENFE5981FWQDWD57MP4T30":3,"skill-same:01M7ENFE5981FWQDWD57MP4T30":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":47},"01M7ENFE5981FWQDWD57MP4T30","blog-brand",null,"Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do\u002Fdon't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says \"blog brand\", \"create brand context\", \"brand voice doc\", \"BRAND.md\", \"VOICE.md\", \"establish editorial brand\", \"brand guidelines for blog\".","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-blog-brand\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: blog-brand\ndescription: >\n  Establish durable brand and voice context for cross-skill consumption.\n  Generates BRAND.md (audience, positioning, do\u002Fdon't editorial rules, taboo\n  phrases, competitor differentiation) and VOICE.md (existing persona JSON\n  re-expressed as readable prose), both written to the project root. When\n  present, the blog orchestrator auto-loads these files for write, rewrite,\n  brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona\n  JSON. Use when user says \"blog brand\", \"create brand context\", \"brand\n  voice doc\", \"BRAND.md\", \"VOICE.md\", \"establish editorial brand\",\n  \"brand guidelines for blog\".\nuser-invokable: true\nargument-hint: \"[init|show|update]\"\nlicense: MIT\n---\n\n# Blog Brand: Durable Editorial Context\n\nGenerates two project-root files that the blog orchestrator auto-loads for supported writing and planning commands when present:\n\n- `BRAND.md`: who the audience is, what the brand stands for, what to never say\n- `VOICE.md`: how the brand sounds, structurally and lexically\n\nThese are the editorial equivalent of impeccable's PRODUCT.md \u002F DESIGN.md pattern: persistent context that survives across sessions and propagates to every command.\n\n## Why this exists\n\nToday, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives \"what is the brand\" from whatever context it has.\n\n`BRAND.md` and `VOICE.md` fix this: one canonical source, loaded by the `blog` orchestrator at the start of every command.\n\nWhen neither file exists, behavior is unchanged from v1.7.1. Backward compatible.\n\n## Commands\n\n| Command | Purpose |\n|---|---|\n| `\u002Fblog brand init` | Interactive interview, writes BRAND.md and VOICE.md to project root |\n| `\u002Fblog brand show` | Display current contents (or report missing) |\n| `\u002Fblog brand update` | Re-run the interview with current values as defaults |\n\n## Init Workflow\n\nRun the 5-step interactive interview. Ask each step, wait for response, then proceed. If `blog-persona` JSON already exists, pre-fill voice answers from it.\n\n### Step 1: Audience\n\nAsk:\n- **Primary audience role** (e.g. \"head of marketing at a 50-500 person B2B SaaS\")\n- **Secondary audience** (optional)\n- **Reader expertise level**: beginner \u002F intermediate \u002F advanced \u002F mixed\n- **Problems the reader is actively trying to solve** (3 to 5 bullets)\n- **Common misconceptions the audience holds** (used to anchor information gain)\n\n### Step 2: Positioning and Canonical Entity\n\nAsk:\n- **Official entity name** (legal or public brand name)\n- **Homepage URL** (canonical brand front door)\n- **Logo URL or file path** (preferred square or SVG asset)\n- **sameAs profiles** (LinkedIn, X, YouTube, Crunchbase, GitHub, or other official profiles)\n- **Wikidata Q-ID** if one exists; leave blank if not notable\n- **One-sentence brand mission** (what the brand helps people do)\n- **Distinctive point of view** (the contrarian or non-obvious belief that shapes content)\n- **What this brand is NOT** (anti-positioning, what to never be confused with)\n- **Top 3 direct competitors** with the one-line differentiator vs each\n\n### Step 3: Editorial rules\n\nAsk:\n- **Do list** (3 to 7 things the blog will always do; e.g. \"cite primary sources only,\" \"name the practitioner not the product\")\n- **Don't list** (3 to 7 things the blog will never do; e.g. \"no clickbait titles,\" \"no listicle filler\")\n- **Taboo phrases** (specific words or phrases this brand never uses; separate\n  from the repository's optional project style list)\n- **Required disclosures** (e.g. affiliate disclosure, AI-content disclosure, conflict-of-interest patterns)\n\n### Step 4: Topic boundaries\n\nAsk:\n- **Topics fully in scope** (core content pillars)\n- **Topics partially in scope** (adjacent; covered only with original angle)\n- **Topics out of scope** (will not cover; redirect to partner content)\n- **Recurring formats \u002F column names** if any (e.g. \"Monthly Field Notes,\" \"Reader Q&A\")\n\n### Step 5: Voice (auto-fill from blog-persona if present)\n\nAsk:\n- **Pronoun stance**: first-person (we \u002F I), second-person (you), third-person (the team), or mixed\n- **Acceptable contractions**: full \u002F partial \u002F none\n- **Sentence ceiling**: max words per sentence as a hard cap\n- **Paragraph ceiling**: max words per paragraph (default 150)\n- **Headline patterns to favor**: numbered \u002F question \u002F promise \u002F statement\n- **Headline patterns to avoid**: any patterns banned for this brand\n- **Summary box label**: from blog-persona, or pick one\n\n## Output Files\n\n### BRAND.md template\n\nWrite to project root as:\n\n```markdown\n# Brand Context\n\n> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.\n\n## Audience\n\n- **Primary**: [role + context]\n- **Secondary**: [if any]\n- **Expertise**: [level]\n- **Active problems**:\n  - [problem 1]\n  - [problem 2]\n  - [problem 3]\n- **Common misconceptions**:\n  - [misconception 1]\n  - [misconception 2]\n\n## Positioning\n\n- **Official entity name**: [brand\u002Fentity]\n- **Homepage**: [canonical URL]\n- **Logo**: [URL or file path]\n- **sameAs profiles**:\n  - [profile URL 1]\n  - [profile URL 2]\n- **Wikidata Q-ID**: [QID or none]\n- **Mission**: [one sentence]\n- **Distinctive POV**: [contrarian or non-obvious belief]\n- **What we are NOT**: [anti-positioning]\n- **Competitors**:\n  - [Competitor A]: [our one-line differentiator]\n  - [Competitor B]: [our one-line differentiator]\n  - [Competitor C]: [our one-line differentiator]\n\n## Editorial Rules\n\n### Always do\n- [rule 1]\n- [rule 2]\n- [rule 3]\n\n### Never do\n- [rule 1]\n- [rule 2]\n- [rule 3]\n\n### Taboo phrases\n- [phrase 1]\n- [phrase 2]\n\n### Required disclosures\n- [disclosure rule]\n\n## Topic Scope\n\n- **In scope**: [pillars]\n- **Partial scope**: [adjacent topics]\n- **Out of scope**: [topics to refuse]\n- **Recurring formats**: [if any]\n```\n\n### VOICE.md template\n\nWrite to project root as:\n\n```markdown\n# Voice Context\n\n> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.\n\n## Pronoun stance\n[first-person \u002F second-person \u002F third-person \u002F mixed]\n\n## Lexical rules\n- **Contractions**: [full \u002F partial \u002F none]\n- **Sentence ceiling**: [N words max]\n- **Paragraph ceiling**: [N words max, default 150]\n- **Summary label**: [Key Takeaways \u002F TL;DR \u002F etc.]\n\n## Headline patterns\n- **Favor**: [list]\n- **Avoid**: [list]\n\n## Voice fingerprint (from blog-persona)\n- Funny vs serious: [0.0 to 1.0]\n- Formal vs casual: [0.0 to 1.0]\n- Respectful vs irreverent: [0.0 to 1.0]\n- Enthusiastic vs matter-of-fact: [0.0 to 1.0]\n\n## Readability target\n- Audience tier: [consumer \u002F professional \u002F technical]\n- Flesch Grade: [range]\n- Flesch Ease: [range]\n\n## Reference samples\n- [URL 1] (extracted patterns: [summary])\n- [URL 2] (extracted patterns: [summary])\n```\n\n## Show Workflow\n\n1. Check for `BRAND.md` and `VOICE.md` at project root.\n2. If both exist, print a summary table (key sections only) and the file paths.\n3. If one or both are missing, print which are missing and suggest `\u002Fblog brand init`.\n\n## Update Workflow\n\nSame as Init, but pre-fills every answer with the current value. The user can press enter to accept or type a new value. After collecting all answers, overwrite both files with the new contents and update the `Last updated:` line.\n\n## Integration with the blog orchestrator\n\nWhen `\u002Fblog write`, `\u002Fblog rewrite`, `\u002Fblog brief`, `\u002Fblog outline`, `\u002Fblog calendar`, or `\u002Fblog strategy` runs, the orchestrator (`skills\u002Fblog\u002FSKILL.md`) checks for `BRAND.md` and `VOICE.md` at the project root. If present, the contents are injected into the system prompt for downstream agents (`blog-researcher`, `blog-writer`, `blog-seo`, `blog-reviewer`).\n\nIf absent, behavior is unchanged. The orchestrator does not prompt the user to create them; they are opt-in context.\n\n## Relationship to blog-persona\n\n| Concern | blog-persona | blog-brand |\n|---|---|---|\n| Structured persona JSON for programmatic use | Yes | No |\n| Readable brand context for cross-skill prompts | No | Yes |\n| Audience and positioning | No | Yes |\n| Taboo phrases and editorial don'ts | Partial (don't list) | Full (taboo + disclosures + scope) |\n| Competitor differentiation | No | Yes |\n| Topic boundaries | No | Yes |\n| Voice fingerprint (tone sliders) | Yes (canonical) | Mirror (read-only) |\n\n`blog-brand` does not replace `blog-persona`; it consumes it. The persona JSON remains the source of truth for tone dimensions, sentence-length distribution, and contraction frequency. `VOICE.md` mirrors the readable parts so prompts are self-contained.\n\nIf no persona exists when `\u002Fblog brand init` runs, the voice questions still produce a `VOICE.md`. Users who want programmatic enforcement can run `\u002Fblog persona create` after.\n\n## Error Handling\n\n- **Project root unclear**: ask the user where to write the files. Default is the current working directory.\n- **Files already exist on init**: ask whether to overwrite or run update instead.\n- **Persona referenced but missing**: ask whether to leave the persona reference blank or create one.\n- **Reader provides minimal answers**: prompt for at least 2 audience bullets and 3 editorial rules; refuse to write skeletons.\n","# Blog Brand: Durable Editorial Context\n\nGenerates two project-root files that the blog orchestrator auto-loads for supported writing and planning commands when present:\n\n- `BRAND.md`: who the audience is, what the brand stands for, what to never say\n- `VOICE.md`: how the brand sounds, structurally and lexically\n\nThese are the editorial equivalent of impeccable's PRODUCT.md \u002F DESIGN.md pattern: persistent context that survives across sessions and propagates to every command.\n\n## Why this exists\n\nToday, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives \"what is the brand\" from whatever context it has.\n\n`BRAND.md` and `VOICE.md` fix this: one canonical source, loaded by the `blog` orchestrator at the start of every command.\n\nWhen neither file exists, behavior is unchanged from v1.7.1. Backward compatible.\n\n## Commands\n\n| Command | Purpose |\n|---|---|\n| `\u002Fblog brand init` | Interactive interview, writes BRAND.md and VOICE.md to project root |\n| `\u002Fblog brand show` | Display current contents (or report missing) |\n| `\u002Fblog brand update` | Re-run the interview with current values as defaults |\n\n## Init Workflow\n\nRun the 5-step interactive interview. Ask each step, wait for response, then proceed. If `blog-persona` JSON already exists, pre-fill voice answers from it.\n\n### Step 1: Audience\n\nAsk:\n- **Primary audience role** (e.g. \"head of marketing at a 50-500 person B2B SaaS\")\n- **Secondary audience** (optional)\n- **Reader expertise level**: beginner \u002F intermediate \u002F advanced \u002F mixed\n- **Problems the reader is actively trying to solve** (3 to 5 bullets)\n- **Common misconceptions the audience holds** (used to anchor information gain)\n\n### Step 2: Positioning and Canonical Entity\n\nAsk:\n- **Official entity name** (legal or public brand name)\n- **Homepage URL** (canonical brand front door)\n- **Logo URL or file path** (preferred square or SVG asset)\n- **sameAs profiles** (LinkedIn, X, YouTube, Crunchbase, GitHub, or other official profiles)\n- **Wikidata Q-ID** if one exists; leave blank if not notable\n- **One-sentence brand mission** (what the brand helps people do)\n- **Distinctive point of view** (the contrarian or non-obvious belief that shapes content)\n- **What this brand is NOT** (anti-positioning, what to never be confused with)\n- **Top 3 direct competitors** with the one-line differentiator vs each\n\n### Step 3: Editorial rules\n\nAsk:\n- **Do list** (3 to 7 things the blog will always do; e.g. \"cite primary sources only,\" \"name the practitioner not the product\")\n- **Don't list** (3 to 7 things the blog will never do; e.g. \"no clickbait titles,\" \"no listicle filler\")\n- **Taboo phrases** (specific words or phrases this brand never uses; separate\n  from the repository's optional project style list)\n- **Required disclosures** (e.g. affiliate disclosure, AI-content disclosure, conflict-of-interest patterns)\n\n### Step 4: Topic boundaries\n\nAsk:\n- **Topics fully in scope** (core content pillars)\n- **Topics partially in scope** (adjacent; covered only with original angle)\n- **Topics out of scope** (will not cover; redirect to partner content)\n- **Recurring formats \u002F column names** if any (e.g. \"Monthly Field Notes,\" \"Reader Q&A\")\n\n### Step 5: Voice (auto-fill from blog-persona if present)\n\nAsk:\n- **Pronoun stance**: first-person (we \u002F I), second-person (you), third-person (the team), or mixed\n- **Acceptable contractions**: full \u002F partial \u002F none\n- **Sentence ceiling**: max words per sentence as a hard cap\n- **Paragraph ceiling**: max words per paragraph (default 150)\n- **Headline patterns to favor**: numbered \u002F question \u002F promise \u002F statement\n- **Headline patterns to avoid**: any patterns banned for this brand\n- **Summary box label**: from blog-persona, or pick one\n\n## Output Files\n\n### BRAND.md template\n\nWrite to project root as:\n\n```markdown\n# Brand Context\n\n> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.\n\n## Audience\n\n- **Primary**: [role + context]\n- **Secondary**: [if any]\n- **Expertise**: [level]\n- **Active problems**:\n  - [problem 1]\n  - [problem 2]\n  - [problem 3]\n- **Common misconceptions**:\n  - [misconception 1]\n  - [misconception 2]\n\n## Positioning\n\n- **Official entity name**: [brand\u002Fentity]\n- **Homepage**: [canonical URL]\n- **Logo**: [URL or file path]\n- **sameAs profiles**:\n  - [profile URL 1]\n  - [profile URL 2]\n- **Wikidata Q-ID**: [QID or none]\n- **Mission**: [one sentence]\n- **Distinctive POV**: [contrarian or non-obvious belief]\n- **What we are NOT**: [anti-positioning]\n- **Competitors**:\n  - [Competitor A]: [our one-line differentiator]\n  - [Competitor B]: [our one-line differentiator]\n  - [Competitor C]: [our one-line differentiator]\n\n## Editorial Rules\n\n### Always do\n- [rule 1]\n- [rule 2]\n- [rule 3]\n\n### Never do\n- [rule 1]\n- [rule 2]\n- [rule 3]\n\n### Taboo phrases\n- [phrase 1]\n- [phrase 2]\n\n### Required disclosures\n- [disclosure rule]\n\n## Topic Scope\n\n- **In scope**: [pillars]\n- **Partial scope**: [adjacent topics]\n- **Out of scope**: [topics to refuse]\n- **Recurring formats**: [if any]\n```\n\n### VOICE.md template\n\nWrite to project root as:\n\n```markdown\n# Voice Context\n\n> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.\n\n## Pronoun stance\n[first-person \u002F second-person \u002F third-person \u002F mixed]\n\n## Lexical rules\n- **Contractions**: [full \u002F partial \u002F none]\n- **Sentence ceiling**: [N words max]\n- **Paragraph ceiling**: [N words max, default 150]\n- **Summary label**: [Key Takeaways \u002F TL;DR \u002F etc.]\n\n## Headline patterns\n- **Favor**: [list]\n- **Avoid**: [list]\n\n## Voice fingerprint (from blog-persona)\n- Funny vs serious: [0.0 to 1.0]\n- Formal vs casual: [0.0 to 1.0]\n- Respectful vs irreverent: [0.0 to 1.0]\n- Enthusiastic vs matter-of-fact: [0.0 to 1.0]\n\n## Readability target\n- Audience tier: [consumer \u002F professional \u002F technical]\n- Flesch Grade: [range]\n- Flesch Ease: [range]\n\n## Reference samples\n- [URL 1] (extracted patterns: [summary])\n- [URL 2] (extracted patterns: [summary])\n```\n\n## Show Workflow\n\n1. Check for `BRAND.md` and `VOICE.md` at project root.\n2. If both exist, print a summary table (key sections only) and the file paths.\n3. If one or both are missing, print which are missing and suggest `\u002Fblog brand init`.\n\n## Update Workflow\n\nSame as Init, but pre-fills every answer with the current value. The user can press enter to accept or type a new value. After collecting all answers, overwrite both files with the new contents and update the `Last updated:` line.\n\n## Integration with the blog orchestrator\n\nWhen `\u002Fblog write`, `\u002Fblog rewrite`, `\u002Fblog brief`, `\u002Fblog outline`, `\u002Fblog calendar`, or `\u002Fblog strategy` runs, the orchestrator (`skills\u002Fblog\u002FSKILL.md`) checks for `BRAND.md` and `VOICE.md` at the project root. If present, the contents are injected into the system prompt for downstream agents (`blog-researcher`, `blog-writer`, `blog-seo`, `blog-reviewer`).\n\nIf absent, behavior is unchanged. The orchestrator does not prompt the user to create them; they are opt-in context.\n\n## Relationship to blog-persona\n\n| Concern | blog-persona | blog-brand |\n|---|---|---|\n| Structured persona JSON for programmatic use | Yes | No |\n| Readable brand context for cross-skill prompts | No | Yes |\n| Audience and positioning | No | Yes |\n| Taboo phrases and editorial don'ts | Partial (don't list) | Full (taboo + disclosures + scope) |\n| Competitor differentiation | No | Yes |\n| Topic boundaries | No | Yes |\n| Voice fingerprint (tone sliders) | Yes (canonical) | Mirror (read-only) |\n\n`blog-brand` does not replace `blog-persona`; it consumes it. The persona JSON remains the source of truth for tone dimensions, sentence-length distribution, and contraction frequency. `VOICE.md` mirrors the readable parts so prompts are self-contained.\n\nIf no persona exists when `\u002Fblog brand init` runs, the voice questions still produce a `VOICE.md`. Users who want programmatic enforcement can run `\u002Fblog persona create` after.\n\n## Error Handling\n\n- **Project root unclear**: ask the user where to write the files. Default is the current working directory.\n- **Files already exist on init**: ask whether to overwrite or run update instead.\n- **Persona referenced but missing**: ask whether to leave the persona reference blank or create one.\n- **Reader provides minimal answers**: prompt for at least 2 audience bullets and 3 editorial rules; refuse to write skeletons.\n",{"name":5,"license":15,"description":24,"argument-hint":25,"user-invokable":26},"Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do\u002Fdon't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says \"blog brand\", \"create brand context\", \"brand voice doc\", \"BRAND.md\", \"VOICE.md\", \"establish editorial brand\", \"brand guidelines for blog\".\n","[init|show|update]",true,"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-imp-blog-brand",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill blog-brand",{"tool":41,"command":42},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill blog-brand",{"tool":44,"command":45},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill blog-brand","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-blog-brand\u002FSKILL.md",[],[49,56,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]