[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DCT97035JRTZHV50WVAVSP":3,"skill-same:01M7DCT97035JRTZHV50WVAVSP":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DCT97035JRTZHV50WVAVSP","fumadocs",null,"Set up a documentation site with Fumadocs. Use when scaffolding a new docs app or adding documentation to a project using Next.js, Waku, React Router, or TanStack Start.","Marvellbrazil\u002Fmy-agentic-skills","Marvellbrazil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184349613?v=4","01M7DCJPCRHP7SZS0T5H1GJZ8F","Marvello Faisal","01M7DCJPDCZDB94VG0QXGC6RC3",5,"MIT","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Farchive\u002Fniche-tools\u002Ffumadocs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fumadocs\ndescription: Set up a documentation site with Fumadocs. Use when scaffolding a new docs app or adding documentation to a project using Next.js, Waku, React Router, or TanStack Start.\n---\n\n# Set up a Fumadocs site\n\nInstructions for AI coding agents, follow them in order. Fumadocs docs: https:\u002F\u002Ffumadocs.dev\u002Fdocs, append `.mdx` to any docs page URL to get it as Markdown, https:\u002F\u002Ffumadocs.dev\u002Fllms.txt lists all pages.\n\n## 1. Keep the docs site separate\n\nCreate the docs as its own app: a new directory or repository, or a new workspace package (e.g. `apps\u002Fdocs`) in a monorepo.\n\nDon't add Fumadocs to an existing marketing or product app unless the user explicitly asks for it: Fumadocs UI ships global styles and its own layouts, mixing them into an unrelated app leads to style conflicts, coupled deployments and harder upgrades. If the user does want it inside an existing app, skip step 2 and run `npx @fumadocs\u002Fcli@latest init --yes` in the app (adds the docs in a dedicated route group, supports Next.js, Waku, React Router and Tanstack Start), or follow the manual installation guide of the framework:\n\n- Next.js: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Fnext.mdx (Recommended)\n- Waku: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Fwaku.mdx (Recommended if user prefer Vite)\n- React Router: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Freact-router.mdx\n- Tanstack Start: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Ftanstack-start.mdx\n- Astro: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Fastro.mdx (Not recommended, some features and syntax are not supported due to framework limitations)\n\n## 2. Scaffold with create-fumadocs-app\n\nUse the official scaffolder, it produces the reference project structure with search, `llms.txt` and OG images configured. Templates:\n\n- `+next+fuma-docs-mdx` (Next.js): the default, use it unless the user prefers another framework.\n- `waku`, `react-router`, `tanstack-start`: when the user already uses that framework.\n- `+next+fuma-docs-mdx+static`, `react-router-spa`, `tanstack-start-spa`: when the site must be fully static (hosted on a CDN).\n\nRun it non-interactively (requires Node.js 22+), `--yes` uses defaults for unspecified options and `--pm` selects the package manager:\n\n```bash\nnpx create-fumadocs-app@latest my-docs --template +next+fuma-docs-mdx --install --yes\n```\n\nAll options: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fcli\u002Fcreate-fumadocs-app.mdx\n\nDon't hand-write the setup from memory or pin older versions, the generated project is the source of truth. Don't edit the `.source\u002F` folder, it is generated by Fumadocs MDX.\n\n## 3. Verify\n\nRun `npm run dev`, open http:\u002F\u002Flocalhost:3000\u002Fdocs and make sure pages render. Run `npm run build` before you finish, fix build errors by reading the docs of the relevant feature rather than removing it.\n\n## 4. Add content\n\n- Pages are MDX files in `content\u002Fdocs`, the folder structure defines the URLs. Every page needs a `title` in its frontmatter, and ideally a `description`.\n- `meta.json` files order pages and folders: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fpage-conventions.mdx and https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fnavigation.mdx\n- When migrating existing Markdown docs, move them as-is and keep their content, only adjust frontmatter and links. Supported syntax and components: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmarkdown.mdx\n- Site name and links live in `lib\u002Flayout.shared.tsx`, GitHub info in `lib\u002Fshared.ts` (Next.js template; other templates put app code under `src\u002F`, check the generated README).\n\n## 5. Deploy separately\n\nDeploy the docs app as its own project on the hosting provider: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fdeploying.mdx\n\nTo serve it under the main domain, use a subdomain like `docs.example.com`, or route `\u002Fdocs\u002F*` from the main site to the docs deployment (e.g. Next.js Multi-Zones). Keep the docs under the default `\u002Fdocs` route so both options work.\n","# Set up a Fumadocs site\n\nInstructions for AI coding agents, follow them in order. Fumadocs docs: https:\u002F\u002Ffumadocs.dev\u002Fdocs, append `.mdx` to any docs page URL to get it as Markdown, https:\u002F\u002Ffumadocs.dev\u002Fllms.txt lists all pages.\n\n## 1. Keep the docs site separate\n\nCreate the docs as its own app: a new directory or repository, or a new workspace package (e.g. `apps\u002Fdocs`) in a monorepo.\n\nDon't add Fumadocs to an existing marketing or product app unless the user explicitly asks for it: Fumadocs UI ships global styles and its own layouts, mixing them into an unrelated app leads to style conflicts, coupled deployments and harder upgrades. If the user does want it inside an existing app, skip step 2 and run `npx @fumadocs\u002Fcli@latest init --yes` in the app (adds the docs in a dedicated route group, supports Next.js, Waku, React Router and Tanstack Start), or follow the manual installation guide of the framework:\n\n- Next.js: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Fnext.mdx (Recommended)\n- Waku: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Fwaku.mdx (Recommended if user prefer Vite)\n- React Router: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Freact-router.mdx\n- Tanstack Start: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Ftanstack-start.mdx\n- Astro: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmanual-installation\u002Fastro.mdx (Not recommended, some features and syntax are not supported due to framework limitations)\n\n## 2. Scaffold with create-fumadocs-app\n\nUse the official scaffolder, it produces the reference project structure with search, `llms.txt` and OG images configured. Templates:\n\n- `+next+fuma-docs-mdx` (Next.js): the default, use it unless the user prefers another framework.\n- `waku`, `react-router`, `tanstack-start`: when the user already uses that framework.\n- `+next+fuma-docs-mdx+static`, `react-router-spa`, `tanstack-start-spa`: when the site must be fully static (hosted on a CDN).\n\nRun it non-interactively (requires Node.js 22+), `--yes` uses defaults for unspecified options and `--pm` selects the package manager:\n\n```bash\nnpx create-fumadocs-app@latest my-docs --template +next+fuma-docs-mdx --install --yes\n```\n\nAll options: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fcli\u002Fcreate-fumadocs-app.mdx\n\nDon't hand-write the setup from memory or pin older versions, the generated project is the source of truth. Don't edit the `.source\u002F` folder, it is generated by Fumadocs MDX.\n\n## 3. Verify\n\nRun `npm run dev`, open http:\u002F\u002Flocalhost:3000\u002Fdocs and make sure pages render. Run `npm run build` before you finish, fix build errors by reading the docs of the relevant feature rather than removing it.\n\n## 4. Add content\n\n- Pages are MDX files in `content\u002Fdocs`, the folder structure defines the URLs. Every page needs a `title` in its frontmatter, and ideally a `description`.\n- `meta.json` files order pages and folders: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fpage-conventions.mdx and https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fnavigation.mdx\n- When migrating existing Markdown docs, move them as-is and keep their content, only adjust frontmatter and links. Supported syntax and components: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fmarkdown.mdx\n- Site name and links live in `lib\u002Flayout.shared.tsx`, GitHub info in `lib\u002Fshared.ts` (Next.js template; other templates put app code under `src\u002F`, check the generated README).\n\n## 5. Deploy separately\n\nDeploy the docs app as its own project on the hosting provider: https:\u002F\u002Ffumadocs.dev\u002Fdocs\u002Fdeploying.mdx\n\nTo serve it under the main domain, use a subdomain like `docs.example.com`, or route `\u002Fdocs\u002F*` from the main site to the docs deployment (e.g. Next.js Multi-Zones). Keep the docs under the default `\u002Fdocs` route so both options work.\n",{"name":5,"description":7},"main","42203fde5eb692ba254e058168ee1af75855fcb4","archive\u002Fniche-tools\u002Ffumadocs",0,"https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills","skills.marvellofaisal.me","https:\u002F\u002Fgithub.com\u002FMarvellbrazil","marvellofaisal.me","Software Engineering Student | Backend & API Developer | Tech Enthusiast | Homelabber","2026-10-23 22:23:52",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Marvellbrazil\u002Fmy-agentic-skills --skill fumadocs",{"tool":40,"command":41},"bunx","bunx skills add Marvellbrazil\u002Fmy-agentic-skills --skill fumadocs",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Marvellbrazil\u002Fmy-agentic-skills --skill fumadocs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Farchive\u002Fniche-tools\u002Ffumadocs\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"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},"01M7DDQP2F4E42AMTGY0VCJ6G2","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\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":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7DDQM00XGSGT8V797C89R2E","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7DDQEF1HP9CMH88HMN9MCBA","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DDQA32ZAG7J4PMRXRSQ3NQ","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7DDQ5482QSC0FC4NX107FVY","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\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":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7DDQ1GZ7Z2Y67460SJJEMC0","using-agent-skills","Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fusing-agent-skills\u002FSKILL.md",[],[]]