Navigation:

northseadl

Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.

samarv

Frame customer opportunities as unmet needs, pain points, and desires rather than solutions. Use when writing opportunities for an Opportunity Solution Tree, validating opportunity statements, or training teams to distinguish problems from solutions. CRITICAL for avoiding the #1 OST failure - 98% of people write opportunities as solutions (Teresa Torres). Triggers when user asks to frame opportunities, write opportunities, validate opportunity statements, or check if this is a need vs solution.

SpacePlushy

Follow project structure standards, environment variable management, Content Collections setup, version control practices, and build/deployment conventions. Use this skill when setting up project structure, managing configuration files, organizing dependencies, or establishing development workflows. When working on project directory structure and organization, environment variable files (.env, .env.local, .env.production), Content Collections configuration (src/content/config.ts), package.json and dependency management, git commit messages and branching strategy, configuration files (astro.config.mjs, tsconfig.json), build and deployment setups, or documentation files (README.md, ADRs).

Trimud

Storefront Next frontend development assistant for the React 19 + React Router 7 + Tailwind CSS 4 e-commerce app in frontend/. Use this skill whenever working on files under frontend/ — React components, routes, hooks, providers, adapters, Page Designer decorators, extensions, configuration, Storybook stories, unit tests (Vitest), or any SCAPI integration code. Also trigger when the user references SCAPI, React Server Components in this project, the adapter pattern, Page Designer metadata generation, the config system (config.server.ts), file-based routing, Radix UI primitives, Zustand stores, or the extension system — even without saying frontend explicitly. Covers: RSC data loading patterns, adapter registry, decorator-based metadata generation, environment-overridable config, Tailwind design tokens, i18n with react-i18next, form validation (React Hook Form + Zod), Storybook 10 stories and tests, and Vitest unit testing. Do NOT use for backend/ directory files (SFRA, ISML, dw.* APIs, cartridge code, npm commands).