[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A51SA06ASKRYD8RTKMD1A1":3,"skill-same:01M7A51SA06ASKRYD8RTKMD1A1":53},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A51SA06ASKRYD8RTKMD1A1","faf-context",null,"Get your project to 100% ✪ AI-readiness, fast — the AI auto-detects your stack and only asks for what it can't know (your goal and the human \"why\"). Least typing, maximum context. For time-conscious builders; feeds into faf-expert for depth.","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ffaf-context\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: faf-context\ndescription: Get your project to 100% ✪ AI-readiness, fast — the AI auto-detects your stack and only asks for what it can't know (your goal and the human \"why\"). Least typing, maximum context. For time-conscious builders; feeds into faf-expert for depth.\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Ftree\u002Fmain\u002Fskills\u002Ffaf-context\nsource_repo: Wolfe-Jam\u002Ffaf-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# FAF Context — Give the AI What It Needs\n## When to Use\n\nUse this skill when you need get your project to 100% ✪ AI-readiness, fast — the AI auto-detects your stack and only asks for what it can't know (your goal and the human \"why\"). Least typing, maximum context. For time-conscious builders; feeds into faf-expert for depth.\n\n\n**AI writes its best code when it has your project's context. This skill helps you hand it over — fast, and to 100%.**\n\n`.faf` is an **IANA-registered context format** (`application\u002Fvnd.faf+yaml`) — a typed, portable file *you own*, readable by any AI (no bespoke manifest, no vendor lock-in). The whole point is one number: **AI-readiness, 0–100%.** At **100% ✪** the AI starts every session already knowing your project — no re-explaining, no guessing. This skill is the *builder's* path to that number: minimum typing, maximum context.\n\n> For the done-for-you one-click path, use **faf-wizard**. To master the format, use **faf-expert**. This skill is the quickstart in between.\n\n## How it works: app-type → AI fills the max → you answer the gaps\n\n**faf-cli has 21 slots.** It works in three steps — and only the last one needs you:\n\n1. **Your app type sets which slots are *required*.** A CLI needs different slots than a full-stack web app — faf-cli right-sizes the set and `slotignored`s the rest (never counted against you).\n2. **The AI fills as many as it can.** `faf auto` detects your stack + language, and a sharp **goal sentence** seeds who\u002Fwhat\u002Fwhere. The better your goal, the more the AI fills for you.\n3. **Whatever's left empty, the AI asks you.** Those are the bits only you know — usually a couple of the 6 Ws (often *why* and *when*). Answer them → **100% ✪.**\n\nSo your job isn't \"fill 21 boxes.\" It's: **write one good goal, then answer the few questions the AI couldn't fill itself.**\n\n> *(Teams \u002F Enterprise tiers add more slots — monorepos, caching, versioning — but those aren't faf-cli. **faf-cli is the 21.**)*\n\n## You rarely type all 6 Ws — here's why\n\nThe 6 Ws are \"the underivable half\" — but you almost never write all six from scratch:\n\n- **who \u002F what \u002F where** → **seeded from your goal sentence** (the AI extracts the facts your goal literally states)\n- **how** → **sourced from your stack** (detection knows how it's built)\n- **why \u002F when** → **the only two that are purely yours**\n\n**So the fast path is: write one sharp goal, confirm the seeds, fill `why` + `when`. → 100%.**\n\n> **\"Sometimes 3 Ws is enough. Sometimes the goal alone is enough.\"** A great goal sentence + auto-detection can carry who\u002Fwhat\u002Fwhere\u002Fhow on their own — leaving you two small answers. The better your goal, the less you type.\n\n## The fastest path to 100% ✪\n\n```bash\nfaf auto      # 1. AI detects your whole stack + seeds context from your README\nfaf score     # 2. See the number + exactly which slots are still empty\nfaf go        # 3. Guided fill: confirm the seeded Ws, answer the 1–2 left\nfaf score     # 4. 100% ✪\nfaf sync      # 5. Push context into CLAUDE.md \u002F AGENTS.md (optional)\n```\n\nMost projects are 1 good goal sentence + 2 answers away from Trophy.\n\n## Write the ONE goal sentence (this does the heavy lifting)\n\nThe goal is the **generative input** — it seeds who\u002Fwhat\u002Fwhere automatically. Make it a real, specific sentence (it's also your *use-case*):\n\n- ✅ *\"A CLI that scores any repo's AI-readiness and syncs context to Claude, Cursor, and Gemini — for solo developers.\"*\n  → seeds **what** (a CLI that scores AI-readiness), **where** (Claude, Cursor, Gemini), **who** (solo developers). You'd only add **why** + **when**.\n- ❌ *\"A tool to improve development.\"* → generic; seeds nothing. (Generic phrases are *ignored* on purpose — empty beats wrong.)\n\n## The 6 Ws — terse labels, not prose\n\nEach W is a **3–4 word label** (hard cap \u003C 6) — a scannable spec card, not a paragraph:\n\n| W | Asks | Example |\n|---|------|---------|\n| Who | who is it for? | `solo developers` |\n| What | what are they building? | `AI-readiness scorer` |\n| Why | why does it exist? | `eliminate context re-explaining` |\n| Where | where does it run\u002Fship? | `npm, Homebrew` |\n| When | timeline \u002F stage? | `production, since 2025` |\n| How | how is it built\u002Fused? | `Bun CLI + WASM` |\n\n## Slots that don't apply → `slotignored`\n\nA CLI has no frontend; an API has no UI library. Mark those **`slotignored`** and they drop out of the denominator — you're scored only on slots that *matter for your app type*. **100% means \"everything that applies is filled,\"** not \"every box checked.\" (`faf auto` and `faf go` handle most of this for you.)\n\n## The honesty rule (why this works)\n\nThe AI **only seeds facts your goal\u002FREADME literally state** — never invents, never uses templates. What it can't source, it leaves empty for you. **Empty beats wrong.** That's why the resulting context is trustworthy: every slot is either detected, stated by you, or honestly blank.\n\n## When you're done here\n\n- Want it done **for** you, one click? → **faf-wizard**\n- Want to **master** the format (scoring internals, MCP config, bi-sync)? → **faf-expert**\n- Driving a repo all the way with an agent? → **`faf go`** \u002F **faf-loop**\n\n---\n\n**The goal:** the AI is only as good as the context you give it. Answer the few things only you know — the gaps it couldn't fill itself — and it's optimized to help you at **100% ✪**.\n\n*MIT · part of the FAF skill family (faf-context · faf-wizard · faf-expert)*\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# FAF Context — Give the AI What It Needs\n## When to Use\n\nUse this skill when you need get your project to 100% ✪ AI-readiness, fast — the AI auto-detects your stack and only asks for what it can't know (your goal and the human \"why\"). Least typing, maximum context. For time-conscious builders; feeds into faf-expert for depth.\n\n\n**AI writes its best code when it has your project's context. This skill helps you hand it over — fast, and to 100%.**\n\n`.faf` is an **IANA-registered context format** (`application\u002Fvnd.faf+yaml`) — a typed, portable file *you own*, readable by any AI (no bespoke manifest, no vendor lock-in). The whole point is one number: **AI-readiness, 0–100%.** At **100% ✪** the AI starts every session already knowing your project — no re-explaining, no guessing. This skill is the *builder's* path to that number: minimum typing, maximum context.\n\n> For the done-for-you one-click path, use **faf-wizard**. To master the format, use **faf-expert**. This skill is the quickstart in between.\n\n## How it works: app-type → AI fills the max → you answer the gaps\n\n**faf-cli has 21 slots.** It works in three steps — and only the last one needs you:\n\n1. **Your app type sets which slots are *required*.** A CLI needs different slots than a full-stack web app — faf-cli right-sizes the set and `slotignored`s the rest (never counted against you).\n2. **The AI fills as many as it can.** `faf auto` detects your stack + language, and a sharp **goal sentence** seeds who\u002Fwhat\u002Fwhere. The better your goal, the more the AI fills for you.\n3. **Whatever's left empty, the AI asks you.** Those are the bits only you know — usually a couple of the 6 Ws (often *why* and *when*). Answer them → **100% ✪.**\n\nSo your job isn't \"fill 21 boxes.\" It's: **write one good goal, then answer the few questions the AI couldn't fill itself.**\n\n> *(Teams \u002F Enterprise tiers add more slots — monorepos, caching, versioning — but those aren't faf-cli. **faf-cli is the 21.**)*\n\n## You rarely type all 6 Ws — here's why\n\nThe 6 Ws are \"the underivable half\" — but you almost never write all six from scratch:\n\n- **who \u002F what \u002F where** → **seeded from your goal sentence** (the AI extracts the facts your goal literally states)\n- **how** → **sourced from your stack** (detection knows how it's built)\n- **why \u002F when** → **the only two that are purely yours**\n\n**So the fast path is: write one sharp goal, confirm the seeds, fill `why` + `when`. → 100%.**\n\n> **\"Sometimes 3 Ws is enough. Sometimes the goal alone is enough.\"** A great goal sentence + auto-detection can carry who\u002Fwhat\u002Fwhere\u002Fhow on their own — leaving you two small answers. The better your goal, the less you type.\n\n## The fastest path to 100% ✪\n\n```bash\nfaf auto      # 1. AI detects your whole stack + seeds context from your README\nfaf score     # 2. See the number + exactly which slots are still empty\nfaf go        # 3. Guided fill: confirm the seeded Ws, answer the 1–2 left\nfaf score     # 4. 100% ✪\nfaf sync      # 5. Push context into CLAUDE.md \u002F AGENTS.md (optional)\n```\n\nMost projects are 1 good goal sentence + 2 answers away from Trophy.\n\n## Write the ONE goal sentence (this does the heavy lifting)\n\nThe goal is the **generative input** — it seeds who\u002Fwhat\u002Fwhere automatically. Make it a real, specific sentence (it's also your *use-case*):\n\n- ✅ *\"A CLI that scores any repo's AI-readiness and syncs context to Claude, Cursor, and Gemini — for solo developers.\"*\n  → seeds **what** (a CLI that scores AI-readiness), **where** (Claude, Cursor, Gemini), **who** (solo developers). You'd only add **why** + **when**.\n- ❌ *\"A tool to improve development.\"* → generic; seeds nothing. (Generic phrases are *ignored* on purpose — empty beats wrong.)\n\n## The 6 Ws — terse labels, not prose\n\nEach W is a **3–4 word label** (hard cap \u003C 6) — a scannable spec card, not a paragraph:\n\n| W | Asks | Example |\n|---|------|---------|\n| Who | who is it for? | `solo developers` |\n| What | what are they building? | `AI-readiness scorer` |\n| Why | why does it exist? | `eliminate context re-explaining` |\n| Where | where does it run\u002Fship? | `npm, Homebrew` |\n| When | timeline \u002F stage? | `production, since 2025` |\n| How | how is it built\u002Fused? | `Bun CLI + WASM` |\n\n## Slots that don't apply → `slotignored`\n\nA CLI has no frontend; an API has no UI library. Mark those **`slotignored`** and they drop out of the denominator — you're scored only on slots that *matter for your app type*. **100% means \"everything that applies is filled,\"** not \"every box checked.\" (`faf auto` and `faf go` handle most of this for you.)\n\n## The honesty rule (why this works)\n\nThe AI **only seeds facts your goal\u002FREADME literally state** — never invents, never uses templates. What it can't source, it leaves empty for you. **Empty beats wrong.** That's why the resulting context is trustworthy: every slot is either detected, stated by you, or honestly blank.\n\n## When you're done here\n\n- Want it done **for** you, one click? → **faf-wizard**\n- Want to **master** the format (scoring internals, MCP config, bi-sync)? → **faf-expert**\n- Driving a repo all the way with an agent? → **`faf go`** \u002F **faf-loop**\n\n---\n\n**The goal:** the AI is only as good as the context you give it. Answer the few things only you know — the gaps it couldn't fill itself — and it's optimized to help you at **100% ✪**.\n\n*MIT · part of the FAF skill family (faf-context · faf-wizard · faf-expert)*\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Ftree\u002Fmain\u002Fskills\u002Ffaf-context",1782864000000,"Wolfe-Jam\u002Ffaf-skills","community","https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ffaf-context",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill faf-context",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill faf-context",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill faf-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ffaf-context\u002FSKILL.md",true,[],[54,61,68,75,84,92],{"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},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\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},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\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},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\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":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","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\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","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.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]