johantor/zion
19 skills
$npx skills add johantor/zionSkillInstalls
backend-dotnet.NET backend stack conventions — MVC controllers, Razor server-side ownership, dotnet build specifics. Load when the resolved backend stack is dotnet.backend-nodeNode backend stack conventions — service framework conventions (NestJS/Express/Fastify), headless CMS/Graph client usage, npm/pnpm/yarn workspace awareness.cms-optimizelyOptimizely CMS conventions — content types, blocks, IContentRepository, scheduled jobs, init modules.context-disciplineToken/context discipline — process large data with code and surface only the answer, never read raw bulk output into context.debt-taxonomyStack-neutral core for the keymaker crew — stack detection, classification rubric, blast-radius gate, upgrade tiers, batch commit shape, and handoff-outline…debt-taxonomy-dotnet.NET / C# suppression mechanisms, safe-removal recipes, NuGet package-manager variance, and upgrade-tier examples for the keymaker crew.debt-taxonomy-typescriptTypeScript / JavaScript suppression mechanisms, safe-removal recipes, npm/pnpm/yarn package-manager variance, and upgrade-tier examples for the keymaker crew.engineering-principlesCore code-quality rules — YAGNI, KISS, DRY with judgment, small single-purpose units, clear naming, minimal-scope diffs.frontend-headlessConventions for decoupled/headless frontends — a React SPA (or Next.js) consuming Optimizely's Content Delivery API / Optimizely Graph (GraphQL) rather than…frontend-nextjsNext.js frontend stack conventions — App Router, Server/Client Components, data fetching (e.g. Optimizely Graph), npm build specifics.frontend-reactReact frontend stack conventions — React, Redux (slices/selectors), vanilla JS, HTML, SCSS/CSS, Vite/npm build specifics.frontend-server-renderedConventions for server-rendered frontends — a server template renders the page shell, with a client-side framework layered in as islands/widgets rather than a…loop-engineeringLoop-mode discipline for orchestrated runs — recognize loop intent ("keep going until done", "loop this", "finish it", "clear all the stale ones", "bump…tests-cypressCypress test conventions — e2e spec writing and component testing.tests-jest-frontendJest frontend component/unit test conventions — test authoring with React Testing Library, mocking patterns, and running.tests-nodeNode backend test conventions — Vitest or Jest, detected by config file (vitest.config.* vs jest.config.*/package.json "jest" key).tests-playwrightPlaywright e2e test conventions — spec writing, fixture/mock patterns, and running. Load when the resolved frontend e2e tool is playwright.tests-vitestVitest component/unit test conventions — test authoring with React Testing Library, mocking patterns, and running.tests-xunit.NET backend test conventions — xUnit test authoring and running, integration tests for the .NET layer. Load when the resolved backend stack is dotnet.