[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EPSHYWX3T482P36MPNEZD2":3,"skill-same:01M7EPSHYWX3T482P36MPNEZD2":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7EPSHYWX3T482P36MPNEZD2","expo-project-structure",null,"Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Fexpo-project-structure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: expo-project-structure\ndescription: Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.\nversion: 1.0.0\nlicense: MIT\n---\n\n# Expo Project Structure\n\nA starting skeleton for a **new** Expo app — one with no committed folder structure yet.\n\n**Apply only to new projects.** If the app already has a layout, follow its existing conventions and leave files where they are — a default to start from, never a standard to enforce or migrate toward. When unsure whether a project is new, ask before moving anything.\n\nThe whole layout, assembled from the rules below:\n\n```\n├── assets\u002F\n├── scripts\u002F\n├── src\u002F\n│   ├── app\u002F                       # Expo Router routes ONLY — every file is a route\n│   │   ├── api\u002F                   #   server API routes, grouped here\n│   │   │   ├── user+api.ts\n│   │   │   └── settings+api.ts\n│   │   ├── _layout.tsx\n│   │   ├── _layout.web.tsx         #   platform-specific layout\n│   │   ├── index.tsx\n│   │   └── settings.tsx\n│   ├── components\u002F                 # reusable UI: button, card, table…\n│   │   ├── table\u002F                  #   complex component → folder + index.tsx\n│   │   │   ├── cell.tsx\n│   │   │   └── index.tsx\n│   │   ├── bar-chart.tsx\n│   │   ├── bar-chart.web.tsx        #   platform-specific variant\n│   │   └── button.tsx\n│   ├── screens\u002F                    # screen bodies that route files render\n│   │   ├── home\u002F\n│   │   │   ├── card.tsx            #   used only by Home — not shared\n│   │   │   └── index.tsx           #   rendered by src\u002Fapp\u002Findex.tsx\n│   │   └── settings.tsx\n│   ├── server\u002F                     # server-only helpers used by app\u002Fapi\n│   │   ├── auth.ts\n│   │   └── db.ts\n│   ├── utils\u002F                      # standalone helpers + colocated tests\n│   │   ├── format-date.ts\n│   │   └── format-date.test.ts\n│   ├── hooks\u002F                      # reusable hooks: use-theme.ts…\n│   ├── constants.ts\n│   └── theme.ts\n├── app.json\n├── eas.json\n└── package.json\n```\n\n## `src\u002F` and `src\u002Fapp`\n\nKeep app code under `src\u002F` to separate it from config files. Expo Router supports both `app\u002F` and `src\u002Fapp\u002F` out of the box — to switch, move the folder and restart the bundler. The default template aliases `@\u002F*` to `.\u002Fsrc\u002F*` in `tsconfig.json`.\n\n`src\u002Fapp` is **routes-only**: every file there becomes a route, so nothing else belongs in it. Everything below lives in sibling folders.\n\n## components\u002F — reusable UI\n\nGeneric, reused UI (button, card, table) with one named export each. Name files in **kebab-case** (`bar-chart.tsx`), matching the default `create-expo-app` template. When a component grows, give it its own folder with the root in `index.tsx` and **colocate** its private sub-components beside it — the import path (`@\u002Fcomponents\u002Ftable`) stays unchanged.\n\n## screens\u002F — screen bodies\n\nBecause `app\u002F` files must be routes, complex screen UI that isn't reused has no home there. Once a screen grows big enough to need breaking out to separate components, put it in `screens\u002F` and let each route just render its screen:\n\n```tsx\nimport { Home } from \"@\u002Fscreens\u002Fhome\";\n\nexport default function HomeScreen() {\n  \u002F\u002F route-specific concerns only — e.g. read url params here\n  return \u003CHome \u002F>;\n}\n```\n\n**Colocate** a screen's private components inside its folder (`screens\u002Fhome\u002Fcomponents\u002F`). A bonus: the same screen can render under multiple routes.\n\n## server\u002F + app\u002Fapi\u002F — separate server code\n\nAppending `+api` to a file in `app\u002F` makes it a server **API route**. Server code is different from frontend code — it runs in a Node-like server environment (deployed with EAS Hosting or on [third-party services](https:\u002F\u002Fdocs.expo.dev\u002Frouter\u002Fweb\u002Fapi-routes\u002F#hosting-on-third-party-services)) and can read secret env vars (`process.env.X`, not just `EXPO_PUBLIC_*`). Keep it apart:\n\n- Group all routes under `app\u002Fapi\u002F` → `\u002Fapi\u002Fuser`, `\u002Fapi\u002Fsettings`. This colocates them and avoids collisions (e.g. a `\u002Fuser` screen and a `\u002Fuser` route).\n- Put shared server-only helpers in `src\u002Fserver\u002F`.\n- Consider ESLint rules that fence `+api` files and `server\u002F` off from frontend-only checks.\n\n## Platform-specific code\n\nSmall differences: use `Platform.select` \u002F `Platform.OS`. For larger ones, split into platform files instead of inline `if\u002Felse` — `bar-chart.tsx` + `bar-chart.web.tsx`, imported extension-free (`@\u002Fcomponents\u002Fbar-chart`); Metro picks the right file per target.\n\n- Props must be identical across variants.\n- A default file (no platform extension) is always required — make it a no-op if the component is single-platform.\n- Supported extensions: `.ios`, `.android`, `.native`, `.web`.\n\n## Colocate styles and tests\n\n- **Styles:** keep the `StyleSheet.create({ ... })` object at the bottom of the component file rather than in a separate `.styles` file.\n- **Tests:** put `format-date.test.ts` next to `format-date.ts` (preferred over a separate `__tests__\u002F` folder) so tested files are obvious at a glance.\n\n## AI and config files\n\nAgent instructions live at the repo root — `AGENTS.md` \u002F `CLAUDE.md`, with project skills under `.claude\u002F`. Other config and assets stay outside `src\u002F`: `app.json` \u002F `app.config.ts`, `eas.json`, `package.json`, `assets\u002F`, and `scripts\u002F`.\n\n---\n\nBased on [Expo app folder structure best practices](https:\u002F\u002Fexpo.dev\u002Fblog\u002Fexpo-app-folder-structure-best-practices) by Kadi Kraman. For `src\u002F` precedence and alias mechanics, see the [Expo docs](https:\u002F\u002Fdocs.expo.dev\u002Frouter\u002Freference\u002Fsrc-directory\u002F).\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes @expo\u002Fagent-cli@latest feedback --category skills --subject \"expo-project-structure\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.\n","# Expo Project Structure\n\nA starting skeleton for a **new** Expo app — one with no committed folder structure yet.\n\n**Apply only to new projects.** If the app already has a layout, follow its existing conventions and leave files where they are — a default to start from, never a standard to enforce or migrate toward. When unsure whether a project is new, ask before moving anything.\n\nThe whole layout, assembled from the rules below:\n\n```\n├── assets\u002F\n├── scripts\u002F\n├── src\u002F\n│   ├── app\u002F                       # Expo Router routes ONLY — every file is a route\n│   │   ├── api\u002F                   #   server API routes, grouped here\n│   │   │   ├── user+api.ts\n│   │   │   └── settings+api.ts\n│   │   ├── _layout.tsx\n│   │   ├── _layout.web.tsx         #   platform-specific layout\n│   │   ├── index.tsx\n│   │   └── settings.tsx\n│   ├── components\u002F                 # reusable UI: button, card, table…\n│   │   ├── table\u002F                  #   complex component → folder + index.tsx\n│   │   │   ├── cell.tsx\n│   │   │   └── index.tsx\n│   │   ├── bar-chart.tsx\n│   │   ├── bar-chart.web.tsx        #   platform-specific variant\n│   │   └── button.tsx\n│   ├── screens\u002F                    # screen bodies that route files render\n│   │   ├── home\u002F\n│   │   │   ├── card.tsx            #   used only by Home — not shared\n│   │   │   └── index.tsx           #   rendered by src\u002Fapp\u002Findex.tsx\n│   │   └── settings.tsx\n│   ├── server\u002F                     # server-only helpers used by app\u002Fapi\n│   │   ├── auth.ts\n│   │   └── db.ts\n│   ├── utils\u002F                      # standalone helpers + colocated tests\n│   │   ├── format-date.ts\n│   │   └── format-date.test.ts\n│   ├── hooks\u002F                      # reusable hooks: use-theme.ts…\n│   ├── constants.ts\n│   └── theme.ts\n├── app.json\n├── eas.json\n└── package.json\n```\n\n## `src\u002F` and `src\u002Fapp`\n\nKeep app code under `src\u002F` to separate it from config files. Expo Router supports both `app\u002F` and `src\u002Fapp\u002F` out of the box — to switch, move the folder and restart the bundler. The default template aliases `@\u002F*` to `.\u002Fsrc\u002F*` in `tsconfig.json`.\n\n`src\u002Fapp` is **routes-only**: every file there becomes a route, so nothing else belongs in it. Everything below lives in sibling folders.\n\n## components\u002F — reusable UI\n\nGeneric, reused UI (button, card, table) with one named export each. Name files in **kebab-case** (`bar-chart.tsx`), matching the default `create-expo-app` template. When a component grows, give it its own folder with the root in `index.tsx` and **colocate** its private sub-components beside it — the import path (`@\u002Fcomponents\u002Ftable`) stays unchanged.\n\n## screens\u002F — screen bodies\n\nBecause `app\u002F` files must be routes, complex screen UI that isn't reused has no home there. Once a screen grows big enough to need breaking out to separate components, put it in `screens\u002F` and let each route just render its screen:\n\n```tsx\nimport { Home } from \"@\u002Fscreens\u002Fhome\";\n\nexport default function HomeScreen() {\n  \u002F\u002F route-specific concerns only — e.g. read url params here\n  return \u003CHome \u002F>;\n}\n```\n\n**Colocate** a screen's private components inside its folder (`screens\u002Fhome\u002Fcomponents\u002F`). A bonus: the same screen can render under multiple routes.\n\n## server\u002F + app\u002Fapi\u002F — separate server code\n\nAppending `+api` to a file in `app\u002F` makes it a server **API route**. Server code is different from frontend code — it runs in a Node-like server environment (deployed with EAS Hosting or on [third-party services](https:\u002F\u002Fdocs.expo.dev\u002Frouter\u002Fweb\u002Fapi-routes\u002F#hosting-on-third-party-services)) and can read secret env vars (`process.env.X`, not just `EXPO_PUBLIC_*`). Keep it apart:\n\n- Group all routes under `app\u002Fapi\u002F` → `\u002Fapi\u002Fuser`, `\u002Fapi\u002Fsettings`. This colocates them and avoids collisions (e.g. a `\u002Fuser` screen and a `\u002Fuser` route).\n- Put shared server-only helpers in `src\u002Fserver\u002F`.\n- Consider ESLint rules that fence `+api` files and `server\u002F` off from frontend-only checks.\n\n## Platform-specific code\n\nSmall differences: use `Platform.select` \u002F `Platform.OS`. For larger ones, split into platform files instead of inline `if\u002Felse` — `bar-chart.tsx` + `bar-chart.web.tsx`, imported extension-free (`@\u002Fcomponents\u002Fbar-chart`); Metro picks the right file per target.\n\n- Props must be identical across variants.\n- A default file (no platform extension) is always required — make it a no-op if the component is single-platform.\n- Supported extensions: `.ios`, `.android`, `.native`, `.web`.\n\n## Colocate styles and tests\n\n- **Styles:** keep the `StyleSheet.create({ ... })` object at the bottom of the component file rather than in a separate `.styles` file.\n- **Tests:** put `format-date.test.ts` next to `format-date.ts` (preferred over a separate `__tests__\u002F` folder) so tested files are obvious at a glance.\n\n## AI and config files\n\nAgent instructions live at the repo root — `AGENTS.md` \u002F `CLAUDE.md`, with project skills under `.claude\u002F`. Other config and assets stay outside `src\u002F`: `app.json` \u002F `app.config.ts`, `eas.json`, `package.json`, `assets\u002F`, and `scripts\u002F`.\n\n---\n\nBased on [Expo app folder structure best practices](https:\u002F\u002Fexpo.dev\u002Fblog\u002Fexpo-app-folder-structure-best-practices) by Kadi Kraman. For `src\u002F` precedence and alias mechanics, see the [Expo docs](https:\u002F\u002Fdocs.expo.dev\u002Frouter\u002Freference\u002Fsrc-directory\u002F).\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes @expo\u002Fagent-cli@latest feedback --category skills --subject \"expo-project-structure\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.\n",{"name":5,"license":14,"version":23,"description":7},"1.0.0","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Fexpo-project-structure","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill expo-project-structure",{"tool":36,"command":37},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill expo-project-structure",{"tool":39,"command":40},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill expo-project-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Fexpo-project-structure\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",316,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Fexpo-project-structure\u002Fagents\u002Fopenai.yaml",[51,59,67,75,82,89],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7EX495RSHTTCEJVX7C83FA3","design-dna","Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[]]