[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75952YBBD5SW8R6FN7BDD2P":3,"skill-same:01M75952YBBD5SW8R6FN7BDD2P":57},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M75952YBBD5SW8R6FN7BDD2P","react-composition-patterns",null,"React composition patterns that scale — compound components, state lifting, context interfaces, and avoiding boolean prop proliferation. Includes React 19 API changes. Use when refactoring components with many boolean props or building flexible component libraries.","lukemcqueen\u002Fsteadfaste-fleet","lukemcqueen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F405240?v=4","01M757MHPAGRXTJAT46SKZP98R","Luke McQueen","01M757MHPZ573KP8DT9GB8SBQ7",4,"MIT","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Freact-composition-patterns\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: react-composition-patterns\ndescription: \"React composition patterns that scale — compound components, state lifting, context interfaces, and avoiding boolean prop proliferation. Includes React 19 API changes. Use when refactoring components with many boolean props or building flexible component libraries.\"\nversion: 1.0.0\nauthor: Steadfaste Fleet (incorporating vercel-labs\u002Fagent-skills)\nmetadata:\n  tags: [react, composition, patterns, component-architecture, vercel]\n  source: https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills\n---\n\n# React Composition Patterns — Vercel Engineering\n\n**Source:** Vercel Labs agent-skills (MIT). Composition patterns for building flexible, maintainable React components. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals.\n\n## When to Apply\n\n- Refactoring components with many boolean props\n- Building reusable component libraries\n- Designing flexible component APIs\n- Reviewing component architecture\n- Working with compound components or context providers\n- Code review feedback on component interfaces\n\n## Rule Categories (by priority)\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | Component Architecture | HIGH | `architecture-` |\n| 2 | State Management | MEDIUM | `state-` |\n| 3 | Implementation Patterns | MEDIUM | `patterns-` |\n| 4 | React 19 APIs | MEDIUM | `react19-` |\n\n---\n\n## 1. Component Architecture (HIGH)\n\n### architecture-avoid-boolean-props\nDon't add boolean props to customize behavior — use composition instead.\n\n```tsx\n\u002F\u002F INCORRECT — boolean prop proliferation\ninterface CardProps {\n  title: string\n  content: string\n  showFooter?: boolean\n  showHeader?: boolean\n  isCompact?: boolean\n  isBordered?: boolean\n  isElevated?: boolean\n}\n\n\u002F\u002F CORRECT — compound components let consumers compose exactly what they need\n\u003CCard>\n  \u003CCard.Header>\n    \u003CCard.Title>Title\u003C\u002FCard.Title>\n    \u003CCard.Actions>\n      \u003CButton>Edit\u003C\u002FButton>\n    \u003C\u002FCard.Actions>\n  \u003C\u002FCard.Header>\n  \u003CCard.Body>\n    \u003Cp>Content\u003C\u002Fp>\n  \u003C\u002FCard.Body>\n  \u003CCard.Footer>\n    \u003Csmall>Last updated: today\u003C\u002Fsmall>\n  \u003C\u002FCard.Footer>\n\u003C\u002FCard>\n```\n\n**When you reach 3+ boolean props on a component, it's time to extract compound components.**\n\n### architecture-compound-components\nStructure complex components with shared context. The parent creates context, children read from it:\n\n```tsx\nconst CardContext = createContext\u003C{ variant: 'default' | 'compact' } | null>(null)\n\nfunction Card({ variant = 'default', children }: CardProps) {\n  return (\n    \u003CCardContext.Provider value={{ variant }}>\n      \u003Cdiv className={`card card--${variant}`}>{children}\u003C\u002Fdiv>\n    \u003C\u002FCardContext.Provider>\n  )\n}\n\nCard.Header = function CardHeader({ children }: { children: ReactNode }) {\n  return \u003Cheader className=\"card__header\">{children}\u003C\u002Fheader>\n}\n\nCard.Title = function CardTitle({ children }: { children: ReactNode }) {\n  const ctx = useContext(CardContext)\n  const size = ctx?.variant === 'compact' ? 'text-sm' : 'text-lg'\n  return \u003Ch3 className={size}>{children}\u003C\u002Fh3>\n}\n```\n\n---\n\n## 2. State Management (MEDIUM)\n\n### state-decouple-implementation\nThe Provider is the only place that knows how state is managed. Consumers don't care if it's useState, useReducer, or Zustand:\n\n```tsx\nconst ThemeContext = createContext\u003CThemeContextValue | null>(null)\n\nfunction ThemeProvider({ children }: { children: ReactNode }) {\n  const [theme, setTheme] = useState\u003C'light' | 'dark'>('light')\n  \u002F\u002F Consumers never know this is useState — could swap to useReducer\n  return (\n    \u003CThemeContext.Provider value={{ theme, setTheme }}>\n      {children}\n    \u003C\u002FThemeContext.Provider>\n  )\n}\n```\n\n### state-context-interface\nDefine a generic interface with `state`, `actions`, and `meta` for dependency injection:\n\n```typescript\ninterface Store\u003CT, A, M = {}> {\n  state: T\n  actions: A\n  meta?: M\n}\n\ninterface NotificationStore extends Store\u003C\n  NotificationState,          \u002F\u002F state\n  { add: (n: Notification) => void; dismiss: (id: string) => void },  \u002F\u002F actions\n  { count: number }           \u002F\u002F meta\n> {}\n```\n\n### state-lift-state\nMove state into provider components for sibling access. If two sibling components share state, the common parent should host it:\n\n```tsx\nfunction Sidebar() {\n  const { setActiveSection } = useSectionContext()\n  return \u003Cbutton onClick={() => setActiveSection('profile')}>Profile\u003C\u002Fbutton>\n}\n\nfunction MainPanel() {\n  const { activeSection } = useSectionContext()\n  return \u003Cdiv>{renderSection(activeSection)}\u003C\u002Fdiv>\n}\n```\n\n---\n\n## 3. Implementation Patterns (MEDIUM)\n\n### patterns-explicit-variants\nCreate explicit variant components instead of boolean modes:\n\n```tsx\n\u002F\u002F INCORRECT — mode prop\n\u003CButton mode=\"primary\" \u002F>\n\u003CButton mode=\"secondary\" \u002F>\n\u003CButton mode=\"danger\" \u002F>\n\n\u002F\u002F CORRECT — explicit variant components\n\u003CPrimaryButton \u002F>\n\u003CSecondaryButton \u002F>\n\u003CDangerButton \u002F>\n```\n\nEach variant wraps the shared base with pre-applied styles\u002Fprops:\n```tsx\nfunction PrimaryButton(props: ButtonProps) {\n  return \u003CBaseButton variant=\"primary\" {...props} \u002F>\n}\n```\n\n### patterns-children-over-render-props\nUse `children` for composition instead of render props:\n\n```tsx\n\u002F\u002F INCORRECT — renderX props\n\u003CList\n  renderItem={(item) => \u003Cli>{item.name}\u003C\u002Fli>}\n  renderEmpty={() => \u003Cp>No items\u003C\u002Fp>}\n\u002F>\n\n\u002F\u002F CORRECT — children composition\n\u003CList>\n  \u003CList.Items>\n    {items.map(item => \u003CList.Item key={item.id}>{item.name}\u003C\u002FList.Item>)}\n  \u003C\u002FList.Items>\n  {items.length === 0 && \u003CList.Empty>No items\u003C\u002FList.Empty>}\n\u003C\u002FList>\n```\n\n---\n\n## 4. React 19 APIs (MEDIUM)\n\n**⚠️ React 19+ only.** Skip this section if using React 18 or earlier.\n\n### react19-no-forwardref\nDon't use `forwardRef` in React 19 — ref is now a regular prop:\n\n```tsx\n\u002F\u002F INCORRECT — React 19 still works but unnecessary\nconst MyInput = forwardRef\u003CHTMLInputElement, Props>((props, ref) => (\n  \u003Cinput ref={ref} {...props} \u002F>\n))\n\n\u002F\u002F CORRECT — ref is just a prop\nfunction MyInput({ ref, ...props }: Props & { ref?: Ref\u003CHTMLInputElement> }) {\n  return \u003Cinput ref={ref} {...props} \u002F>\n}\n```\n\n### react19-use-over-usecontext\nUse `use()` instead of `useContext()` — it works with promises too:\n```tsx\nimport { use } from 'react'\n\nfunction Card() {\n  \u002F\u002F Instead of useContext(CardContext)\n  const ctx = use(CardContext)\n  return \u003Cdiv>{ctx.title}\u003C\u002Fdiv>\n}\n\n\u002F\u002F Also works with promises (integrates with Suspense)\nfunction Comments({ commentsPromise }: { commentsPromise: Promise\u003CComment[]> }) {\n  const comments = use(commentsPromise)  \u002F\u002F Suspends until resolved\n  return \u003Cul>{comments.map(c => \u003Cli key={c.id}>{c.text}\u003C\u002Fli>)}\u003C\u002Ful>\n}\n```\n\n---\n\n## Verification\n\nAfter refactoring, check:\n1. Count boolean props on each component — target ≤2 per component\n2. Compound components have clear, documented sub-components\n3. State providers are at the right level in the tree (not too high, not duplicated)\n4. Consumers don't import implementation details from state providers","# React Composition Patterns — Vercel Engineering\n\n**Source:** Vercel Labs agent-skills (MIT). Composition patterns for building flexible, maintainable React components. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals.\n\n## When to Apply\n\n- Refactoring components with many boolean props\n- Building reusable component libraries\n- Designing flexible component APIs\n- Reviewing component architecture\n- Working with compound components or context providers\n- Code review feedback on component interfaces\n\n## Rule Categories (by priority)\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | Component Architecture | HIGH | `architecture-` |\n| 2 | State Management | MEDIUM | `state-` |\n| 3 | Implementation Patterns | MEDIUM | `patterns-` |\n| 4 | React 19 APIs | MEDIUM | `react19-` |\n\n---\n\n## 1. Component Architecture (HIGH)\n\n### architecture-avoid-boolean-props\nDon't add boolean props to customize behavior — use composition instead.\n\n```tsx\n\u002F\u002F INCORRECT — boolean prop proliferation\ninterface CardProps {\n  title: string\n  content: string\n  showFooter?: boolean\n  showHeader?: boolean\n  isCompact?: boolean\n  isBordered?: boolean\n  isElevated?: boolean\n}\n\n\u002F\u002F CORRECT — compound components let consumers compose exactly what they need\n\u003CCard>\n  \u003CCard.Header>\n    \u003CCard.Title>Title\u003C\u002FCard.Title>\n    \u003CCard.Actions>\n      \u003CButton>Edit\u003C\u002FButton>\n    \u003C\u002FCard.Actions>\n  \u003C\u002FCard.Header>\n  \u003CCard.Body>\n    \u003Cp>Content\u003C\u002Fp>\n  \u003C\u002FCard.Body>\n  \u003CCard.Footer>\n    \u003Csmall>Last updated: today\u003C\u002Fsmall>\n  \u003C\u002FCard.Footer>\n\u003C\u002FCard>\n```\n\n**When you reach 3+ boolean props on a component, it's time to extract compound components.**\n\n### architecture-compound-components\nStructure complex components with shared context. The parent creates context, children read from it:\n\n```tsx\nconst CardContext = createContext\u003C{ variant: 'default' | 'compact' } | null>(null)\n\nfunction Card({ variant = 'default', children }: CardProps) {\n  return (\n    \u003CCardContext.Provider value={{ variant }}>\n      \u003Cdiv className={`card card--${variant}`}>{children}\u003C\u002Fdiv>\n    \u003C\u002FCardContext.Provider>\n  )\n}\n\nCard.Header = function CardHeader({ children }: { children: ReactNode }) {\n  return \u003Cheader className=\"card__header\">{children}\u003C\u002Fheader>\n}\n\nCard.Title = function CardTitle({ children }: { children: ReactNode }) {\n  const ctx = useContext(CardContext)\n  const size = ctx?.variant === 'compact' ? 'text-sm' : 'text-lg'\n  return \u003Ch3 className={size}>{children}\u003C\u002Fh3>\n}\n```\n\n---\n\n## 2. State Management (MEDIUM)\n\n### state-decouple-implementation\nThe Provider is the only place that knows how state is managed. Consumers don't care if it's useState, useReducer, or Zustand:\n\n```tsx\nconst ThemeContext = createContext\u003CThemeContextValue | null>(null)\n\nfunction ThemeProvider({ children }: { children: ReactNode }) {\n  const [theme, setTheme] = useState\u003C'light' | 'dark'>('light')\n  \u002F\u002F Consumers never know this is useState — could swap to useReducer\n  return (\n    \u003CThemeContext.Provider value={{ theme, setTheme }}>\n      {children}\n    \u003C\u002FThemeContext.Provider>\n  )\n}\n```\n\n### state-context-interface\nDefine a generic interface with `state`, `actions`, and `meta` for dependency injection:\n\n```typescript\ninterface Store\u003CT, A, M = {}> {\n  state: T\n  actions: A\n  meta?: M\n}\n\ninterface NotificationStore extends Store\u003C\n  NotificationState,          \u002F\u002F state\n  { add: (n: Notification) => void; dismiss: (id: string) => void },  \u002F\u002F actions\n  { count: number }           \u002F\u002F meta\n> {}\n```\n\n### state-lift-state\nMove state into provider components for sibling access. If two sibling components share state, the common parent should host it:\n\n```tsx\nfunction Sidebar() {\n  const { setActiveSection } = useSectionContext()\n  return \u003Cbutton onClick={() => setActiveSection('profile')}>Profile\u003C\u002Fbutton>\n}\n\nfunction MainPanel() {\n  const { activeSection } = useSectionContext()\n  return \u003Cdiv>{renderSection(activeSection)}\u003C\u002Fdiv>\n}\n```\n\n---\n\n## 3. Implementation Patterns (MEDIUM)\n\n### patterns-explicit-variants\nCreate explicit variant components instead of boolean modes:\n\n```tsx\n\u002F\u002F INCORRECT — mode prop\n\u003CButton mode=\"primary\" \u002F>\n\u003CButton mode=\"secondary\" \u002F>\n\u003CButton mode=\"danger\" \u002F>\n\n\u002F\u002F CORRECT — explicit variant components\n\u003CPrimaryButton \u002F>\n\u003CSecondaryButton \u002F>\n\u003CDangerButton \u002F>\n```\n\nEach variant wraps the shared base with pre-applied styles\u002Fprops:\n```tsx\nfunction PrimaryButton(props: ButtonProps) {\n  return \u003CBaseButton variant=\"primary\" {...props} \u002F>\n}\n```\n\n### patterns-children-over-render-props\nUse `children` for composition instead of render props:\n\n```tsx\n\u002F\u002F INCORRECT — renderX props\n\u003CList\n  renderItem={(item) => \u003Cli>{item.name}\u003C\u002Fli>}\n  renderEmpty={() => \u003Cp>No items\u003C\u002Fp>}\n\u002F>\n\n\u002F\u002F CORRECT — children composition\n\u003CList>\n  \u003CList.Items>\n    {items.map(item => \u003CList.Item key={item.id}>{item.name}\u003C\u002FList.Item>)}\n  \u003C\u002FList.Items>\n  {items.length === 0 && \u003CList.Empty>No items\u003C\u002FList.Empty>}\n\u003C\u002FList>\n```\n\n---\n\n## 4. React 19 APIs (MEDIUM)\n\n**⚠️ React 19+ only.** Skip this section if using React 18 or earlier.\n\n### react19-no-forwardref\nDon't use `forwardRef` in React 19 — ref is now a regular prop:\n\n```tsx\n\u002F\u002F INCORRECT — React 19 still works but unnecessary\nconst MyInput = forwardRef\u003CHTMLInputElement, Props>((props, ref) => (\n  \u003Cinput ref={ref} {...props} \u002F>\n))\n\n\u002F\u002F CORRECT — ref is just a prop\nfunction MyInput({ ref, ...props }: Props & { ref?: Ref\u003CHTMLInputElement> }) {\n  return \u003Cinput ref={ref} {...props} \u002F>\n}\n```\n\n### react19-use-over-usecontext\nUse `use()` instead of `useContext()` — it works with promises too:\n```tsx\nimport { use } from 'react'\n\nfunction Card() {\n  \u002F\u002F Instead of useContext(CardContext)\n  const ctx = use(CardContext)\n  return \u003Cdiv>{ctx.title}\u003C\u002Fdiv>\n}\n\n\u002F\u002F Also works with promises (integrates with Suspense)\nfunction Comments({ commentsPromise }: { commentsPromise: Promise\u003CComment[]> }) {\n  const comments = use(commentsPromise)  \u002F\u002F Suspends until resolved\n  return \u003Cul>{comments.map(c => \u003Cli key={c.id}>{c.text}\u003C\u002Fli>)}\u003C\u002Ful>\n}\n```\n\n---\n\n## Verification\n\nAfter refactoring, check:\n1. Count boolean props on each component — target ≤2 per component\n2. Compound components have clear, documented sub-components\n3. State providers are at the right level in the tree (not too high, not duplicated)\n4. Consumers don't import implementation details from state providers",{"name":5,"author":24,"version":25,"metadata":26,"description":7},"Steadfaste Fleet (incorporating vercel-labs\u002Fagent-skills)","1.0.0",{"tags":27,"source":33},[28,29,30,31,32],"react","composition","patterns","component-architecture","vercel","https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills","main","2e6aa8d15ab0a366c90be54f61bf9c6e97015e83","skills\u002Fsoftware-development\u002Freact-composition-patterns",1,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet","steadfaste.com","https:\u002F\u002Fgithub.com\u002Flukemcqueen","AI Architect | Building Hermes Cortex: governed multi-agent AI for autonomous software engineering | Enterprise Tech Consultant","2026-11-14 22:33:34",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add lukemcqueen\u002Fsteadfaste-fleet --skill react-composition-patterns",{"tool":49,"command":50},"bunx","bunx skills add lukemcqueen\u002Fsteadfaste-fleet --skill react-composition-patterns",{"tool":52,"command":53},"pnpm","pnpm dlx skills add lukemcqueen\u002Fsteadfaste-fleet --skill react-composition-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Freact-composition-patterns\u002FSKILL.md",true,[],[58,66,73,80,87,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"01M7DXY4G8NSVB59K8B6S2AQNP","macbook-linux-maintenance","Legacy MacBook Linux fixes: GPU wedge, reboot hang, thermal.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fmacbook-linux-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":65},"01M7DXXYJCXFJ3TGB84ZQ8KFE6","governance-regression-triage","Triage a host's governance issues: what changed.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fgovernance-regression-triage\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":65},"01M7DXXSAP1G8FDRJAMXQGBBMK","enforcement-immutability","Use when enforcement files lose their immutable flag.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fenforcement-immutability\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":65},"01M78SSDQVRYX64Y16X32TC0NS","steadfaste-fleet-repo-deploy","Use when committing to the steadfaste-fleet repo.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-repo-deploy\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":65},"01M78SS928F3R2RJAYVW4E30CE","steadfaste-fleet-maintenance","Maintain an installed Steadfaste Fleet instance — update both the upstream Hermes Agent and the fleet repo layer, merge diverged histories, sync skills safely, and troubleshoot common issues. Covers the dual-update workflow (hermes update + fleet-update.sh), encrypted brain data backup, mycortex import, and recovery techniques.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-maintenance\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":65},"01M78SP1CHW0T0BWE5ZT6JBPX8","fleet-preflight","DEPRECATED alias — merged into survey-before-action (2026-08-20). Load survey-before-action instead; its \"Repo-Specific Pre-Flight\" section covers git search, Hermes boundary, and deployment verification.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ffleet-preflight\u002FSKILL.md",[],[]]