burgan-tech

Use when adding query parameter filters to a monitor list endpoint. Covers the 3-class pattern (FilterInput / FilterDescriptor / Filter), bracket-notation binding with [eq]/[contains] operators, conflict validation, type-discriminated 400 validation, and in-memory LINQ apply — all derived from the component filter implementation.

Scope is repo-wide domain knowledge (not bound to a single workspace). vNext Runtime platform referansı. Workflow, state, transition, task, schema, view, function ve extension kavramlarını, JSON tanım yapılarını ve C# mapping/rule pattern'lerini kapsar. vNext bileşenleri oluşturulurken veya düzenlenirken bu skill'i kullanın. Trigger this skill whenever vNext workflow/task/schema/view/function/extension JSON or `.csx` mapping/rule files are being created or edited anywhere in the monorepo (or in target vnext domain repositories).

Creates a structured English GitHub issue using gh CLI based on a user-provided scope description. Translates the scope to English, optionally scans the codebase to enrich the technical description, shows the draft for user approval, then opens the issue. Use when the user asks to open an issue, create a GitHub issue, report a bug/task/feature, or says "issue aç", "issue oluştur", or "scan project" / "projeyi tara".

Creates an English GitHub Pull Request using gh CLI by analyzing commits on the current branch compared to the base branch. Generates a structured PR title and body, shows it for user approval, then creates the PR. Use when the user asks to create a PR, open a pull request, push and create PR, or mentions "gh pr", "pull request", or "open PR".

Generates a Conventional Commits-style English commit message by analyzing staged git changes. Use when the user asks for a commit message, wants to commit changes, mentions "commit", "git commit", or asks for help writing a commit message.

Generate or update vNext platform documentation for the vnext-docs Docusaurus site. Use when the user says "döküman oluştur", "create docs", "document this feature", or asks to update/sync documentation after a code change.

Generates a comprehensive matrix report from vnext-meta JSON files. Outputs a markdown table showing features, deprecations, known issues, components, and limits by version. Use when the user says "meta matrix", "meta rapor", "feature matrix", "meta ozet", or "meta tablo".

Validates vnext-meta package JSON files for schema compliance, version consistency, and codebase alignment. Use when the user says "validate meta", "meta check", "meta kontrol", "vnext-meta validate", or after modifying vnext-meta JSON files.

Create, edit, and validate vNext workflow domain components (Schemas, Workflows, Tasks, Views, Functions, Extensions) in a @burgan-tech/vnext-template project. Use whenever the user wants to add or change a component JSON file under the domain directory, asks about the required component fields (key/version/domain/ flow/flowVersion/tags/attributes), or hits schema-validation errors from `npm run validate`.

Use when the user wants to create a vNext Function — a REST endpoint exposed by the runtime. Fetches function.json schema first, walks scope (D/F/I) and task composition (single-task vs multi-task), scaffolds the IMapping or IOutputHandler .csx using contracts from csx-contracts.md.

Use when the user wants to create a vNext Mapping (sys-mappings) component — a reusable C# helper/code class (e.g. a crypto or JSON helper) that other components reference via scripts.helpers or encoding REF. Fetches mapping-definition.schema.json first, scaffolds the Mappings/{key}.json envelope + the .csx static class, and explains wiring it into consumers.

Use when the user wants to create or modify a vNext Schema component. Interactively gathers fields, types, validation rules, localization (x-labels), field-level access (x-roles), and query metadata (x-filterOperators/x-sortable/x-displayFormat) before producing JSON Schema draft 2020-12 at the path resolved from vnext.config.json.

Use when the user asks to validate components or fix validation errors, or before committing. Runs `npm run validate`, categorizes failures, queries the docs for the relevant rule, and proposes targeted fixes with user approval before applying.

Use when the user wants to create a new vNext Workflow end-to-end. Plans the state/transition graph, scaffolds the workflow JSON + .csx mapping files + .http test file, and chains to view-design / schema-design as needed.

Use when the user wants to create a vNext Extension — automatic instance data enrichment on workflow reads. Fetches extension.json schema first, walks the type × scope matrix from the schema, warns on performance impact (especially Global × Everywhere).

Use when the user wants to create a new vNext Task component (HTTP, Script, SOAP, Dapr, Notification, GetInstances, etc.). Fetches task.json schema first, drives type and config selection from the schema enum, scaffolds a .csx mapping if needed, suggests a matching MockLab seed.

Scope is repo-wide. Enforces the cross-package import direction policy (apps depend on packages; packages depend only on packages of equal or lower role; apps never depend on each other). Trigger this skill when adding a new import that crosses workspace boundaries, modifying `package.json` `dependencies`, adding/changing barrel files, or editing ESLint `no-restricted-imports`. See `docs/architecture/dependency-policy.md`.

Scope is repo-wide. Authoritative guide for the error contract built around `ERROR_CODES`, `VnextForgeError`, `ApiResponse<T>`, and `error-presentation`. Trigger this skill whenever throwing, catching, mapping, displaying, or testing errors anywhere in the monorepo (apps/*, packages/*). See ADR 005.

Scope is the entire monorepo (root + all workspaces under apps/* and packages/*). Update the monorepo ESLint configuration in vnext-forge-studio. Use when changing shared lint rules, workspace-specific ESLint behavior, runtime globals, or logger/no-console overrides. Trigger this skill for any ESLint config work in `eslint.config.mjs` at the repo root or in any workspace.

Scope is the host-agnostic notification port in packages/designer-ui plus its shell adapters in apps/web (sonner toast) and apps/extension/webview-ui (VS Code native). Guidelines for emitting and routing transient user feedback (toast / native notification / status-bar pill). Use when calling showNotification(...), wiring a new shell sink, deciding between transient feedback and inline screen state, or working on status-bar notification chrome.

Scope is apps/web (web frontend). Optional guidance for theming and color tokens in the web app. Use only when the task is explicitly about visual system work; do not treat theme token migration as a required part of the architecture refactor. Trigger this skill for any theming or color token work under `apps/web`.

Scope is repo-wide. Implements the `trace-v1` contract for `X-Trace-Id` and `traceparent` correlation. Trigger this skill whenever editing HTTP middleware, transports, RPC clients, runtime-proxy, or anything that reads/writes trace headers anywhere in the monorepo. See ADR 002.

Scope is repo-wide domain knowledge (not bound to a single workspace). vNext Runtime platform referansı. Workflow, state, transition, task, schema, view, function ve extension kavramlarını, JSON tanım yapılarını ve C# mapping/rule pattern'lerini kapsar. vNext bileşenleri oluşturulurken veya düzenlenirken bu skill'i kullanın. Trigger this skill whenever vNext workflow/task/schema/view/function/extension JSON or `.csx` mapping/rule files are being created or edited anywhere in the monorepo (or in target vnext domain repositories).

Generate a detailed component constraint matrix document from a vNext schema file. Analyzes required/optional/conditional fields, type-based constraints, if/then rules, and enum restrictions. Outputs to docs/components/. Use when the user asks for a component matrix, constraint documentation, field reference, or says a component name like "workflow", "task", "view", "function", "extension", "schema".

Generate a component-based feature matrix from features.json after schema changes. Use after modifying schema files, running generate-features, or when the user asks for a feature catalog summary, matrix, or support table.