[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFZFN3Z5730QS6HB8Z4P76":3,"skill-same:01M6AFZFN3Z5730QS6HB8Z4P76":95},{"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":31,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6AFZFN3Z5730QS6HB8Z4P76","building-blog",null,"Use when adding a blog to a Next.js + Sanity site, building a blog section from scratch, integrating Sanity CMS for editorial content, or setting up an SEO-optimized article surface. Triggers on phrases like 'add a blog', 'build the blog', 'create blog section', 'set up blog with Sanity', 'integrate Sanity CMS', 'blog architecture', or any new-blog scoping conversation on a Next.js project.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-development\u002Fbuilding-blog\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"building blog","blog","up","new","2026","when","sanity","add","article","project","next","conversation","community","safe","integrate","scoping","seo","SET","cms","content","create","architecture","2026-11-10 10:12:30",false,"---\nname: building-blog\ndescription: \"Use when adding a blog to a Next.js + Sanity site, building a blog section from scratch, integrating Sanity CMS for editorial content, or setting up an SEO-optimized article surface. Triggers on phrases like 'add a blog', 'build the blog', 'create blog section', 'set up blog with Sanity', 'integrate Sanity CMS', 'blog architecture', or any new-blog scoping conversation on a Next.js project.\"\nmetadata:\n  risk: safe\n  source: community\n  date_added: \"2026-05-21\"\n---\n\n# Building a Blog (Next.js + Sanity)\n\n## Overview\n\nUniversal workflow for adding a blog to a Next.js site backed by Sanity CMS. Targets a corporate blog: SEO-first, i18n-ready, performance-budgeted, accessibility-compliant.\n\n**SKILL.md is the orchestrator. The spec lives in the two reference files.**\n\n## Files\n\n- `blog-technical-requirements.md` — §0 intake questionnaire (30+ questions) → §1 Project Profile → §2–§20 universal spec → checklist. Edit only §0 answers and §1 per project.\n- `blog-image-style-guide.md` — universal template for AI-generated hero imagery via Gemini 3 Pro Image (Nano Banana Pro). Intake questions on top, aesthetic skeleton in the middle, three example slots at the bottom.\n\n## Workflow\n\n### Step 1 — Scan the host project (before asking anything)\n\nRead what's already there. Pre-filling answers from detected values is much better than asking the user. Look for:\n\n- `package.json` — Next.js version, `next-intl`, Sanity packages, Tailwind, `framer-motion`\n- `next.config.{ts,js,mjs}` — existing `images.formats`, i18n config\n- `src\u002Fmessages\u002F**`, `src\u002Fi18n\u002F**`, `messages\u002F**` — current locale set\n- `src\u002Fapp\u002F[locale]\u002F**` or `app\u002F[locale]\u002F**` — routing pattern\n- `tailwind.config.*`, `globals.css`, design-system files — tokens, fonts\n- `CLAUDE.md`, `AGENTS.md`, `GEMINI.md` — project conventions and approved overrides\n- Existing `sanity-studio\u002F` or `studio\u002F` folder\n- `app\u002Flayout.{tsx,jsx}` — fonts, analytics, motion config\n- `public\u002Fbrand\u002F**`, `public\u002Flogo*` — publisher logo\n- `sitemap.ts`, `robots.ts` — existing routes\n- `.env*` files — names of already-set env vars (do not log secret values)\n\nRecord findings as a brief \"Detected\" list before the questionnaire.\n\n### Step 2 — Run the intake questionnaire\n\nOpen `blog-technical-requirements.md` and walk through §0.\n\n- **Claude Code:** use `AskUserQuestion`. Group related questions into single calls (max 4 per call). Pre-fill recommended answers from the scan.\n- **Codex \u002F CLIs without an interactive picker:** list questions numerically in plain text, ask the user to answer in batches of 5–10. Show recommended answers from the scan.\n- **Headless \u002F non-interactive:** apply universal defaults to whatever the prompt did not explicitly cover; list every assumption.\n\nWrite the answers into §1 \"Project Profile\" (in a project-local copy under `docs\u002Fblog\u002F`, not in the universal source).\n\n### Step 3 — Produce the high-level plan\n\nUse the plan template at the end of §0. One page. Phases, locked-in scope, out-of-scope items, open decisions. **Wait for explicit user approval. Do not start coding.**\n\n### Step 4 — Implement against the spec\n\nFollow §2–§20 in order. §19 (Pass\u002FFail Checklist) is the definition of done. The image style guide drives §20 if AI-generated hero images are in scope.\n\n## When NOT to use this skill\n\n- Static \u002F MDX-only blogs (no CMS) — different stack, different patterns\n- High-velocity news publishers — sitemap chunking and editor tooling become primary concerns\n- Documentation sites — use a docs framework instead\n- Marketing landing pages that aren't really a blog\n\n## Source\n\nMaintained at [BuildShipGrowRepeat\u002Fnextjs-sanity-blog-skill](https:\u002F\u002Fgithub.com\u002FBuildShipGrowRepeat\u002Fnextjs-sanity-blog-skill). MIT licensed.\n","# Building a Blog (Next.js + Sanity)\n\n## Overview\n\nUniversal workflow for adding a blog to a Next.js site backed by Sanity CMS. Targets a corporate blog: SEO-first, i18n-ready, performance-budgeted, accessibility-compliant.\n\n**SKILL.md is the orchestrator. The spec lives in the two reference files.**\n\n## Files\n\n- `blog-technical-requirements.md` — §0 intake questionnaire (30+ questions) → §1 Project Profile → §2–§20 universal spec → checklist. Edit only §0 answers and §1 per project.\n- `blog-image-style-guide.md` — universal template for AI-generated hero imagery via Gemini 3 Pro Image (Nano Banana Pro). Intake questions on top, aesthetic skeleton in the middle, three example slots at the bottom.\n\n## Workflow\n\n### Step 1 — Scan the host project (before asking anything)\n\nRead what's already there. Pre-filling answers from detected values is much better than asking the user. Look for:\n\n- `package.json` — Next.js version, `next-intl`, Sanity packages, Tailwind, `framer-motion`\n- `next.config.{ts,js,mjs}` — existing `images.formats`, i18n config\n- `src\u002Fmessages\u002F**`, `src\u002Fi18n\u002F**`, `messages\u002F**` — current locale set\n- `src\u002Fapp\u002F[locale]\u002F**` or `app\u002F[locale]\u002F**` — routing pattern\n- `tailwind.config.*`, `globals.css`, design-system files — tokens, fonts\n- `CLAUDE.md`, `AGENTS.md`, `GEMINI.md` — project conventions and approved overrides\n- Existing `sanity-studio\u002F` or `studio\u002F` folder\n- `app\u002Flayout.{tsx,jsx}` — fonts, analytics, motion config\n- `public\u002Fbrand\u002F**`, `public\u002Flogo*` — publisher logo\n- `sitemap.ts`, `robots.ts` — existing routes\n- `.env*` files — names of already-set env vars (do not log secret values)\n\nRecord findings as a brief \"Detected\" list before the questionnaire.\n\n### Step 2 — Run the intake questionnaire\n\nOpen `blog-technical-requirements.md` and walk through §0.\n\n- **Claude Code:** use `AskUserQuestion`. Group related questions into single calls (max 4 per call). Pre-fill recommended answers from the scan.\n- **Codex \u002F CLIs without an interactive picker:** list questions numerically in plain text, ask the user to answer in batches of 5–10. Show recommended answers from the scan.\n- **Headless \u002F non-interactive:** apply universal defaults to whatever the prompt did not explicitly cover; list every assumption.\n\nWrite the answers into §1 \"Project Profile\" (in a project-local copy under `docs\u002Fblog\u002F`, not in the universal source).\n\n### Step 3 — Produce the high-level plan\n\nUse the plan template at the end of §0. One page. Phases, locked-in scope, out-of-scope items, open decisions. **Wait for explicit user approval. Do not start coding.**\n\n### Step 4 — Implement against the spec\n\nFollow §2–§20 in order. §19 (Pass\u002FFail Checklist) is the definition of done. The image style guide drives §20 if AI-generated hero images are in scope.\n\n## When NOT to use this skill\n\n- Static \u002F MDX-only blogs (no CMS) — different stack, different patterns\n- High-velocity news publishers — sitemap chunking and editor tooling become primary concerns\n- Documentation sites — use a docs framework instead\n- Marketing landing pages that aren't really a blog\n\n## Source\n\nMaintained at [BuildShipGrowRepeat\u002Fnextjs-sanity-blog-skill](https:\u002F\u002Fgithub.com\u002FBuildShipGrowRepeat\u002Fnextjs-sanity-blog-skill). MIT licensed.\n",{"name":5,"metadata":59,"description":7},{"risk":45,"source":44,"date_added":60},"2026-05-21","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fweb-development\u002Fbuilding-blog",3911,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-11 21:38:31",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add davila7\u002Fclaude-code-templates --skill building-blog",{"tool":77,"command":78},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill building-blog",{"tool":80,"command":81},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill building-blog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-development\u002Fbuilding-blog\u002FSKILL.md",true,[85,91],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"blog-image-style-guide.md","REFERENCE","参考文档",12712,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-development\u002Fbuilding-blog\u002Fblog-image-style-guide.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"blog-technical-requirements.md",62439,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-development\u002Fbuilding-blog\u002Fblog-technical-requirements.md",[96,123,149,180,215,239],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":54},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[102],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[104,105,106,107,108,109,110,111,112,37,113,114,115,116,117,118,119,120,121,122],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":54},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[129],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[131,132,133,134,135,136,137,138,41,139,140,37,141,142,143,144,145,146,147,148],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":162,"publishedAt":54},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[155,158,159],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":160,"categoryName":161,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[163,164,165,166,167,168,169,109,170,171,172,173,174,175,176,112,177,178,37,179],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":184,"licenseFileUrl":185,"sourceHtmlUrl":186,"categories":187,"keywords":191,"publishedAt":54},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,109,214],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":184,"licenseFileUrl":219,"sourceHtmlUrl":220,"categories":221,"keywords":226,"publishedAt":54},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[222,225],{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},[227,228,229,230,231,193,232,202,203,233,234,235,236,109,237,114,238],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":184,"licenseFileUrl":243,"sourceHtmlUrl":244,"categories":245,"keywords":249,"publishedAt":54},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[246,247,248],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[250,251,252,253,254,255,256,257,195,258,205,141,51,259,43,260,34,175,261,37,262,263,264,265,266,120,267],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","review","short","invoke","you","analysis","claims","argument","assemble","recommendations"]