[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CM26PBC203P6CCEQRJVYEC":3,"skill-same:01M7CM26PBC203P6CCEQRJVYEC":47},{"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":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7CM26PBC203P6CCEQRJVYEC","frontend-architecture",null,"How to organize frontend code — separation of concerns (UI \u002F logic \u002F data \u002F type), file responsibility, state tiers, API services, schema validation, and framework conventions for React\u002FNext and Vue. Structural rules, not visual design.","haliltek\u002Fdev.tr","haliltek","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31656259?v=4","01M7CKZCVHYRZ5CFNDBMFT5S7Q","Halil TEK","01M7CKZCWH3RX91D93NHE4DP2J",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-architecture\ndescription: How to organize frontend code — separation of concerns (UI \u002F logic \u002F data \u002F type), file responsibility, state tiers, API services, schema validation, and framework conventions for React\u002FNext and Vue. Structural rules, not visual design.\nwhen_to_use: \"When structuring a frontend codebase or reviewing how frontend code is organized — where logic, API calls, state, types, and validation should live; component vs hook\u002Fcomposable boundaries; Next.js server\u002Fclient split; Vue Composition API. NOT for visual design (use frontend-design) and NOT for React\u002FNext performance rules (use nextjs-react-expert).\"\nallowed-tools: Read, Write, Edit, Glob, Grep\nversion: 1.0.0\n---\n\n# Frontend Architecture\n\n> How to organize frontend code so it scales. Separation of concerns over file-type folders.\n> Applies to React\u002FNext and Vue. For directory layout, follow [app-builder](..\u002Fapp-builder\u002Fscaffolding.md). For visual design, see [frontend-design](..\u002Ffrontend-design\u002FSKILL.md). For React\u002FNext performance, see [nextjs-react-expert](..\u002Fnextjs-react-expert\u002FSKILL.md).\n\n---\n\n## 1. Separation of Concerns — the core rule\n\nSplit code into four layers by responsibility. A unit of code does ONE of these, not several:\n\n| Layer | Holds | Lives in |\n|-------|-------|----------|\n| **UI** | Rendering, markup, presentational state | `components\u002F` |\n| **Logic** | State, effects, data transforms, reusable UI logic | `hooks\u002F` (React) · `composables\u002F` (Vue) |\n| **Data** | API calls, fetch\u002Faxios, cache keys | `lib\u002F` \u002F service files (`*.api.ts`) |\n| **Type** | TypeScript types, domain models | `types.ts` \u002F `*.types.ts` |\n| **Validation** | Form\u002Fdata schemas | `*.schema.ts` (zod\u002Fyup\u002Fvalibot) |\n\n> **Directory layout** (top-level folders) follows the project's scaffolding skill — do not invent a competing structure here. This skill is about *which layer code belongs to*, not where the folders sit.\n\n---\n\n## 2. File Responsibility & Size\n\nOne clear responsibility per file. Size is a **signal, not a hard limit** — a clear 230-line file beats a 90-line file that fetches, validates, renders, and juggles modals + toasts.\n\n| File type | Comfortable range |\n|-----------|-------------------|\n| UI component | 80–180 lines |\n| Page \u002F screen | 100–220 lines |\n| Hook \u002F composable | 40–150 lines |\n| API service | 50–200 lines |\n| Type \u002F schema | flexible |\n\nSplit a file when it mixes UI + API + business logic + validation + state. Don't split a coherent file just to hit a number.\n\n---\n\n## 3. Components render UI; logic goes elsewhere\n\nComponents should primarily render. Push fetching\u002Fstate\u002Ftransforms into a hook or composable.\n\n```tsx\n\u002F\u002F ❌ Component owns the data layer\nfunction ProductList() {\n  const [products, setProducts] = useState([])\n  useEffect(() => { fetch('\u002Fapi\u002Fproducts').then(r => r.json()).then(setProducts) }, [])\n  return \u003Cdiv>{\u002F* render *\u002F}\u003C\u002Fdiv>\n}\n\n\u002F\u002F ✅ Component renders; logic lives in a hook\nfunction ProductList() {\n  const { products, isLoading } = useProducts()\n  if (isLoading) return \u003CLoading \u002F>\n  return \u003Cdiv>{\u002F* render *\u002F}\u003C\u002Fdiv>\n}\n```\n\n- Custom hooks must start with `use`.\n- A component calling an API directly is acceptable only for the smallest one-off cases.\n\n---\n\n## 4. Next.js — Server Components by default\n\nIn the App Router, `page.tsx` and `layout.tsx` are Server Components. Reach for `\"use client\"` only when you actually need the client.\n\n| Server Component | Client Component |\n|------------------|------------------|\n| Fetch data, read DB\u002FAPI | Form, modal, dropdown |\n| Handle secret tokens | Event handlers, animation |\n| Render static\u002Fsemi-static layout | `useState`\u002F`useEffect`, browser APIs (`window`, `localStorage`) |\n\nKeep client components small. Don't `\"use client\"` a whole page for one interactive button — extract the button into its own client component and keep the page a Server Component.\n\n---\n\n## 5. Vue — Composition API + composables\n\nFor full production apps, prefer the Composition API with `\u003Cscript setup>` Single File Components. (Options API is fine for simple cases \u002F progressive enhancement.)\n\n- `components\u002F` → UI\n- `composables\u002F` → reusable pure logic (`useX`)\n- service files → API calls\n\nUse a composable for reusable pure logic; use a component when reusing both logic and layout.\n\n---\n\n## 6. State — start local, escalate only when needed\n\n| Need | Use |\n|------|-----|\n| Component-internal state | `useState` \u002F `ref` |\n| Reusable state\u002Flogic in one feature | custom hook \u002F composable |\n| Shared UI state in a subtree | Context (React) \u002F `provide`-`inject` (Vue) |\n| Cross-app, complex, persisted | Zustand \u002F Pinia \u002F Redux |\n| Server state \u002F API cache | TanStack Query (react-query) \u002F similar |\n\nDon't reach for global state (or Redux) on day one of a small app. Server state belongs in a query library, not a global store.\n\n---\n\n## 7. API in service files\n\nNever scatter raw `fetch`\u002F`axios` across components.\n\n```ts\n\u002F\u002F user.api.ts\nexport async function getUsers() {\n  const res = await http.get('\u002Fusers')\n  return res.data\n}\n\n\u002F\u002F useUsers.ts\nexport function useUsers() {\n  return useQuery({ queryKey: ['users'], queryFn: getUsers })\n}\n```\n\nAlways handle loading, error, and empty states explicitly.\n\n---\n\n## 8. Forms validate against a schema\n\nDon't inline long validation inside a component.\n\n- React\u002FNext: react-hook-form + zod (or yup)\n- Vue: vee-validate + zod\u002Fyup\n\nKeep schemas in `*.schema.ts` next to the form they validate.\n\n---\n\n## 9. Naming\n\nDescriptive, not cryptic. Context from the folder is allowed, but lean explicit.\n\n| Prefer | Avoid |\n|--------|-------|\n| `UserProfileCard.tsx` | `Card.tsx` |\n| `useCreateBooking.ts` | `handle.ts` |\n| `booking.api.ts` | `api.ts` (bare) |\n| `booking.schema.ts` | `data.ts` |\n\n---\n\n## 10. Props\n\nType props explicitly. When a component takes many related fields, pass the object, not a scatter of primitives.\n\n```tsx\n\u002F\u002F ✅\ntype ProductCardProps = { product: Product; onSelect?: (p: Product) => void }\n\n\u002F\u002F ❌ seven loose props\n\u003CProductCard id={id} name={name} price={price} image={image} discount={discount} stock={stock} \u002F>\n```\n\n---\n\n## 11. Anti \"god component\"\n\nSplit a component when it shows these tells:\n\n- longer than ~200 lines\n- more than ~3 `useEffect`\u002F`watch`\n- many `useState`\u002F`ref`\n- renders UI **and** fetches API\n- many `if\u002Felse` business branches\n- multiple modals\u002Ftables\u002Fforms in one file\n\nDecompose along the page seams:\n\n```\nPage\n ├─ Header\n ├─ Filter\n ├─ Table \u002F List\n ├─ Pagination\n └─ Modal \u002F Form\n```\n\n---\n\n## 12. Tailwind class hygiene\n\n- If a `className` runs past ~5–8 logical groups, extract a component.\n- Repeated patterns → a reusable component or variant helper.\n- No complex conditional logic inline in `className` — use `cn()`.\n\n```tsx\n\u002F\u002F ✅\nconst cardClassName = cn(\n  'rounded-xl border p-4',\n  isActive && 'bg-blue-500 text-white',\n  isError && 'border-red-500',\n)\n```\n\n---\n\n## 13. TypeScript\n\n- Enable `strict: true`.\n- Avoid `any`.\n- Type props, API responses, and domain models explicitly.\n- Prefer union types over enums when a union suffices.\n- Validate external data with schemas (zod) — types alone don't guard runtime input.\n\n---\n\n## 14. Minimum testing\n\nDon't test everything up front; do cover:\n\n- utilities → unit tests\n- important hooks\u002Fcomposables → unit tests\n- main forms → validation tests\n- critical flows → e2e\n\nColocate (`useBooking.test.ts` next to `useBooking.ts`) or keep `tests\u002Funit` + `tests\u002Fe2e` — pick one and stay consistent.\n\n---\n\n## 15. Accessibility floor\n\n- Use `\u003Cbutton>` for actions, not `\u003Cdiv onClick>`.\n- Every input has a label; every image has `alt`.\n- Modals support keyboard escape + focus trap.\n- Forms surface errors clearly.\n\n---\n\n> **Remember:** one file = one responsibility · UI doesn't own logic · logic → hook\u002Fcomposable · API → service · validation → schema · types separate · Next is server-first · Vue is composable-first. Directory structure comes from the scaffolding skill, not from here.\n","# Frontend Architecture\n\n> How to organize frontend code so it scales. Separation of concerns over file-type folders.\n> Applies to React\u002FNext and Vue. For directory layout, follow [app-builder](..\u002Fapp-builder\u002Fscaffolding.md). For visual design, see [frontend-design](..\u002Ffrontend-design\u002FSKILL.md). For React\u002FNext performance, see [nextjs-react-expert](..\u002Fnextjs-react-expert\u002FSKILL.md).\n\n---\n\n## 1. Separation of Concerns — the core rule\n\nSplit code into four layers by responsibility. A unit of code does ONE of these, not several:\n\n| Layer | Holds | Lives in |\n|-------|-------|----------|\n| **UI** | Rendering, markup, presentational state | `components\u002F` |\n| **Logic** | State, effects, data transforms, reusable UI logic | `hooks\u002F` (React) · `composables\u002F` (Vue) |\n| **Data** | API calls, fetch\u002Faxios, cache keys | `lib\u002F` \u002F service files (`*.api.ts`) |\n| **Type** | TypeScript types, domain models | `types.ts` \u002F `*.types.ts` |\n| **Validation** | Form\u002Fdata schemas | `*.schema.ts` (zod\u002Fyup\u002Fvalibot) |\n\n> **Directory layout** (top-level folders) follows the project's scaffolding skill — do not invent a competing structure here. This skill is about *which layer code belongs to*, not where the folders sit.\n\n---\n\n## 2. File Responsibility & Size\n\nOne clear responsibility per file. Size is a **signal, not a hard limit** — a clear 230-line file beats a 90-line file that fetches, validates, renders, and juggles modals + toasts.\n\n| File type | Comfortable range |\n|-----------|-------------------|\n| UI component | 80–180 lines |\n| Page \u002F screen | 100–220 lines |\n| Hook \u002F composable | 40–150 lines |\n| API service | 50–200 lines |\n| Type \u002F schema | flexible |\n\nSplit a file when it mixes UI + API + business logic + validation + state. Don't split a coherent file just to hit a number.\n\n---\n\n## 3. Components render UI; logic goes elsewhere\n\nComponents should primarily render. Push fetching\u002Fstate\u002Ftransforms into a hook or composable.\n\n```tsx\n\u002F\u002F ❌ Component owns the data layer\nfunction ProductList() {\n  const [products, setProducts] = useState([])\n  useEffect(() => { fetch('\u002Fapi\u002Fproducts').then(r => r.json()).then(setProducts) }, [])\n  return \u003Cdiv>{\u002F* render *\u002F}\u003C\u002Fdiv>\n}\n\n\u002F\u002F ✅ Component renders; logic lives in a hook\nfunction ProductList() {\n  const { products, isLoading } = useProducts()\n  if (isLoading) return \u003CLoading \u002F>\n  return \u003Cdiv>{\u002F* render *\u002F}\u003C\u002Fdiv>\n}\n```\n\n- Custom hooks must start with `use`.\n- A component calling an API directly is acceptable only for the smallest one-off cases.\n\n---\n\n## 4. Next.js — Server Components by default\n\nIn the App Router, `page.tsx` and `layout.tsx` are Server Components. Reach for `\"use client\"` only when you actually need the client.\n\n| Server Component | Client Component |\n|------------------|------------------|\n| Fetch data, read DB\u002FAPI | Form, modal, dropdown |\n| Handle secret tokens | Event handlers, animation |\n| Render static\u002Fsemi-static layout | `useState`\u002F`useEffect`, browser APIs (`window`, `localStorage`) |\n\nKeep client components small. Don't `\"use client\"` a whole page for one interactive button — extract the button into its own client component and keep the page a Server Component.\n\n---\n\n## 5. Vue — Composition API + composables\n\nFor full production apps, prefer the Composition API with `\u003Cscript setup>` Single File Components. (Options API is fine for simple cases \u002F progressive enhancement.)\n\n- `components\u002F` → UI\n- `composables\u002F` → reusable pure logic (`useX`)\n- service files → API calls\n\nUse a composable for reusable pure logic; use a component when reusing both logic and layout.\n\n---\n\n## 6. State — start local, escalate only when needed\n\n| Need | Use |\n|------|-----|\n| Component-internal state | `useState` \u002F `ref` |\n| Reusable state\u002Flogic in one feature | custom hook \u002F composable |\n| Shared UI state in a subtree | Context (React) \u002F `provide`-`inject` (Vue) |\n| Cross-app, complex, persisted | Zustand \u002F Pinia \u002F Redux |\n| Server state \u002F API cache | TanStack Query (react-query) \u002F similar |\n\nDon't reach for global state (or Redux) on day one of a small app. Server state belongs in a query library, not a global store.\n\n---\n\n## 7. API in service files\n\nNever scatter raw `fetch`\u002F`axios` across components.\n\n```ts\n\u002F\u002F user.api.ts\nexport async function getUsers() {\n  const res = await http.get('\u002Fusers')\n  return res.data\n}\n\n\u002F\u002F useUsers.ts\nexport function useUsers() {\n  return useQuery({ queryKey: ['users'], queryFn: getUsers })\n}\n```\n\nAlways handle loading, error, and empty states explicitly.\n\n---\n\n## 8. Forms validate against a schema\n\nDon't inline long validation inside a component.\n\n- React\u002FNext: react-hook-form + zod (or yup)\n- Vue: vee-validate + zod\u002Fyup\n\nKeep schemas in `*.schema.ts` next to the form they validate.\n\n---\n\n## 9. Naming\n\nDescriptive, not cryptic. Context from the folder is allowed, but lean explicit.\n\n| Prefer | Avoid |\n|--------|-------|\n| `UserProfileCard.tsx` | `Card.tsx` |\n| `useCreateBooking.ts` | `handle.ts` |\n| `booking.api.ts` | `api.ts` (bare) |\n| `booking.schema.ts` | `data.ts` |\n\n---\n\n## 10. Props\n\nType props explicitly. When a component takes many related fields, pass the object, not a scatter of primitives.\n\n```tsx\n\u002F\u002F ✅\ntype ProductCardProps = { product: Product; onSelect?: (p: Product) => void }\n\n\u002F\u002F ❌ seven loose props\n\u003CProductCard id={id} name={name} price={price} image={image} discount={discount} stock={stock} \u002F>\n```\n\n---\n\n## 11. Anti \"god component\"\n\nSplit a component when it shows these tells:\n\n- longer than ~200 lines\n- more than ~3 `useEffect`\u002F`watch`\n- many `useState`\u002F`ref`\n- renders UI **and** fetches API\n- many `if\u002Felse` business branches\n- multiple modals\u002Ftables\u002Fforms in one file\n\nDecompose along the page seams:\n\n```\nPage\n ├─ Header\n ├─ Filter\n ├─ Table \u002F List\n ├─ Pagination\n └─ Modal \u002F Form\n```\n\n---\n\n## 12. Tailwind class hygiene\n\n- If a `className` runs past ~5–8 logical groups, extract a component.\n- Repeated patterns → a reusable component or variant helper.\n- No complex conditional logic inline in `className` — use `cn()`.\n\n```tsx\n\u002F\u002F ✅\nconst cardClassName = cn(\n  'rounded-xl border p-4',\n  isActive && 'bg-blue-500 text-white',\n  isError && 'border-red-500',\n)\n```\n\n---\n\n## 13. TypeScript\n\n- Enable `strict: true`.\n- Avoid `any`.\n- Type props, API responses, and domain models explicitly.\n- Prefer union types over enums when a union suffices.\n- Validate external data with schemas (zod) — types alone don't guard runtime input.\n\n---\n\n## 14. Minimum testing\n\nDon't test everything up front; do cover:\n\n- utilities → unit tests\n- important hooks\u002Fcomposables → unit tests\n- main forms → validation tests\n- critical flows → e2e\n\nColocate (`useBooking.test.ts` next to `useBooking.ts`) or keep `tests\u002Funit` + `tests\u002Fe2e` — pick one and stay consistent.\n\n---\n\n## 15. Accessibility floor\n\n- Use `\u003Cbutton>` for actions, not `\u003Cdiv onClick>`.\n- Every input has a label; every image has `alt`.\n- Modals support keyboard escape + focus trap.\n- Forms surface errors clearly.\n\n---\n\n> **Remember:** one file = one responsibility · UI doesn't own logic · logic → hook\u002Fcomposable · API → service · validation → schema · types separate · Next is server-first · Vue is composable-first. Directory structure comes from the scaffolding skill, not from here.\n",{"name":5,"version":24,"description":7,"when_to_use":25,"allowed-tools":26},"1.0.0","When structuring a frontend codebase or reviewing how frontend code is organized — where logic, API calls, state, types, and validation should live; component vs hook\u002Fcomposable boundaries; Next.js server\u002Fclient split; Vue Composition API. NOT for visual design (use frontend-design) and NOT for React\u002FNext performance rules (use nextjs-react-expert).","Read, Write, Edit, Glob, Grep","main","35fc33da79b31d7f8dadfc704083baff1b5672a0",".agents\u002Fskills\u002Ffrontend-architecture","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr","https:\u002F\u002Fgithub.com\u002Fhaliltek","2026-11-13 01:38:48",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add haliltek\u002Fdev.tr --skill frontend-architecture",{"tool":39,"command":40},"bunx","bunx skills add haliltek\u002Fdev.tr --skill frontend-architecture",{"tool":42,"command":43},"pnpm","pnpm dlx skills add haliltek\u002Fdev.tr --skill frontend-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-architecture\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CM8JAC0X6HVS8VCHH51KPZ","respectfully","Wraps any prompt with a reminder to respect CLAUDE.md files","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frespectfully\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CM8FPHK4J5EP607Y77XHA4","recruiter","Think like a skeptical technical recruiter when working on the daily.dev Recruiter platform. Use when reviewing UI\u002FUX, features, or code in webapp\u002Fpages\u002Frecruiter.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frecruiter\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CM8CB9XR2W46XJ3T2X0245","changelog","Generate a daily.dev changelog post for a new feature or update. Use when a team member needs to write a changelog announcement.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CM88HKHZP4S2H9GYKWCBPB","webapp-testing","Web application testing principles. E2E, Playwright, deep audit strategies.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CM831R2XYCHFNRGXD6NYS1","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CM7XTJ13ZQFZ9Y5SRYF8CP","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvulnerability-scanner\u002FSKILL.md",[],[]]