All authors
Claude Skills by Omega-JS-Stack
github.com/Omega-JS-Stack14 skills0 installs0 views
- AccessibilityUse before finishing any markup, theme, section, or stylesheet change in a website app, packages/web, or a desktop/extension UI surface — or when the ask names accessibility, a11y, aria, alt text, keyboard navigation, focus, contrast, reduced motion, or WCAG.Votes: 0GitHub stars: 2
- AnalyticsUse before finishing any flow, checkout, auth, or backend payment/webhook work — or when the ask names analytics, tracking, an event, a conversion, a pixel, gtag/fbq/ttq, GA4, Meta, TikTok, consent gating, or attribution.Votes: 0GitHub stars: 2
- BackendUse when working on a brand's backend app or on @omega.js/backend itself — Cloud Functions routes, schemas, auth hooks, the emulator harness, usage, payments, email, or anything under targets/backend, functions/, or packages/backend/.Votes: 0GitHub stars: 2
- BrandcheckUse when editing config/omega.json5, theme or default-page copy, section defaults, or any file that names a brand — brand facts belong in config, never as a hardcoded name, url, or hex, and secrets never in config at all.Votes: 0GitHub stars: 2
- BrowserUse when the user wants to open, view, screenshot, test, or debug a page in a real browser, fill or submit forms, inspect live pages, run Lighthouse, attach to a running desktop dev app, or test an unpacked extension.Votes: 0GitHub stars: 2
- ClientUse when working in @omega.js/client or on any frontend behavior it owns: the browser base class, auth and the User, data-omega-bind bindings, the Firestore, storage, notifications and Sentry modules, omega.request(), verts, icons, motion, or anything in packages/client/.Votes: 0GitHub stars: 2
- DesktopUse when working on a brand's desktop app or on @omega.js/desktop itself — Electron main, renderer or preload, windows, tray, menus, ipc, deep links, the auto-updater, or the sign/notarize/release pipeline, in targets/desktop or packages/desktop/.Votes: 0GitHub stars: 2
- ExtensionUse when working on a brand's extension app or on @omega.js/extension itself — the MV3 manifest, background service worker, popup, options, sidepanel, content scripts, cross-context auth, _locales translation, or the package/publish pipeline, in targets/extension or packages/extension/.Votes: 0GitHub stars: 2
- InitUse when someone wants to start a new OMEGA brand, asks what state a folder is in, or runs in a folder that may already hold a brand, a template copy or a half-finished setup.Votes: 0GitHub stars: 2
- MainUse when working across more than one OMEGA framework, in the monorepo itself, or when the right home for a change is not yet known — which package owns a thing, the docs topology, the brand map, or where project state lives.Votes: 0GitHub stars: 2
- ManagerUse when working at a brand monorepo root, on the manage cycle, or on @omega.js/manager itself — the service walk, reconciling a brand to its config/omega.json5, onboarding, deploy and update fan-out, .omega state, disperse, or the agent-docs chain.Votes: 0GitHub stars: 2
- SeoUse before finishing any page work in a website app or in packages/web — or when the ask names SEO, meta title or description, canonical, open graph, structured data, one h1, sitemap, robots.txt, noindex, or search ranking.Votes: 0GitHub stars: 2
- ThemeUse when building or changing a theme or a theme override — packages/web/themes, a brand's own src/themes/<id>, a section folder under src/_sections, or the tier-1 src/assets/css/main.scss — or when the ask names theming, skins, forks, tokens, the cascade, or inherit.Votes: 0GitHub stars: 2
- WebUse when working on a brand's website app or on @omega.js/web itself: Eleventy and Liquid templates, sections and components, themes, blueprints and default pages, the asset pipeline, or the omega CLI, in targets/web or packages/web/.Votes: 0GitHub stars: 2