All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 65,763
- 2,741
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse development skills
Showing 11,857–11,880 of 65,763 skills
- Frontend V2 ComponentsBuilding or modifying components in the RomM v2 frontend (frontend/src/v2/). Use when creating/editing v2 primitives (R* components in src/v2/lib/), shared composites, or feature composites. Covers the three-tier model, file/folder conventions, SFC structure, import order, barrels, Storybook requirements, and v2 anti-patterns. Trigger on any work under frontend/src/v2/.Votes: 0GitHub stars: 13,244
- Frontend I18nInternationalization for the RomM frontend (both v1 and v2). Use whenever adding, renaming, or removing any user-visible string / translation key under frontend/src/locales/. Covers the en_US-is-source rule, the requirement to add every new key to ALL locale directories in the same change, namespace layout, and the check_i18n_locales.py validator enforced in CI. Trigger on any change to frontend/src/locales/**.Votes: 0GitHub stars: 13,244
- Address Bot ReviewsWork through the Greptile and Copilot review comments on a RomM PR. Triage each finding (valid, introduced by this PR, consistent with what the PR intends), fix the ones that hold up, then reply on every thread with the fix or the reason for declining and resolve it. Use after the review bots have commented on an open PR.Votes: 0GitHub stars: 13,244
- Perf LoadtestRun the L2 k6 load harness against the live Aspire-hosted backend and produce a summary + optional dotnet-counters CSV. Use to answer "how does the running system behave under load" — throughput, p95 latency, GC pressure — as opposed to L1 (BenchmarkDotNet, code-level) or L3 (dotnet-trace, attribution).Votes: 0GitHub stars: 2
- Vue Unit Test[Development] Reproduce a Virto Commerce vc-frontend storefront bug as a failing vitest test (red), then prove the fix turns it green — without modifying existing tests or stories. Used by the fullstack-frontend developer agent in the /qa-fix pipeline (Gate 2/G3).Votes: 0GitHub stars: 2
- Vue Fix[Development] Implement a minimal, idiomatic Vue 3 / TypeScript fix in the vc-frontend storefront that turns the reproduction test green while preserving BL-UI invariants and component contracts and leaving existing tests/stories untouched. Used by the fullstack-frontend developer agent in /qa-fix (Gate 3).Votes: 0GitHub stars: 2
- Vc Shell Fix[Development] Fix a Virto Commerce module's embedded Vue 3 \"shell\" sub-app (@vc-shell/framework, e.g. vc-module-pagebuilder's src/VirtoCommerce.PageBuilderModule.Web/Apps/page-builder-shell/) declared in skills/qa-fix-routing/fix-repos.json moduleFrontendSubApps. State/logic bugs (composable/store/service function) are proven red→green with the sub-app's OWN real `tsx --test` runner + plain Vue reactivity (ref/computed/watch/effectScope) — no stubbing needed, unlike angular-admin's scratch ...Votes: 0GitHub stars: 2
- Vc Docs[VC Knowledge] Documentation lookup via VirtoOZ MCP (primary) or Context7 (fallback): architecture, modules, APIs, deployment, B2B.Votes: 0GitHub stars: 2
- Qa Fix RoutingRepo/tracker routing library for the vc-fix plugin — decides which external product repo owns a bug (client vs platform), whether the fix delivers as a direct PR, a fork-PR, or an upstream issue, and which VCS/tracker host to talk to. Used by /qa-fix and /project-init. Self-contained — no dependency on the ci/ directory.Votes: 0GitHub stars: 2
- Qa Evidence[QA Method] Evidence capture & report formatting: screenshot rules, 3-tier verbosity, output paths.Votes: 0GitHub stars: 2
- Dotnet Unit Test[Development] Reproduce a Virto Commerce backend bug as a failing xUnit test (red), then prove the fix turns it green — without modifying existing tests. Used by the fullstack-backend developer agent in the /qa-fix pipeline (Gate 2/G3).Votes: 0GitHub stars: 2
- Dotnet Fix[Development] Implement a minimal, idiomatic .NET 10 / C# fix in a single Virto Commerce module (or vc-platform) that turns the reproduction test green while preserving BL-* invariants and leaving existing tests untouched. Used by the fullstack-backend developer agent in /qa-fix (Gate 3).Votes: 0GitHub stars: 2
- Angular Admin[Development] Fix a Virto Commerce module's Admin SPA (AngularJS) UI that ships inside the module's own vc-module-* repo — blade/widget/service anatomy + idiomatic AngularJS 1.x. Two proof paths, because module repos have NO JS test harness and there is NO Storybook: logic bugs (save/payload, computed value, wrong endpoint) are proven red→green with a throwaway Node scratch harness; layout/CSS/visual bugs (overlap, misalignment, wrong width, clipping) are fixed by mirroring the platform's can...Votes: 0GitHub stars: 2
- Vc Self CheckOn-demand self-diagnostician for the vc-fix plugin (Tier 2 of the client→vendor feedback loop). Reads the passive session-telemetry jsonl (observation records + span records) + the session transcript + the skill-expectations oracle, and emits a per-finding verdict (OK / DEGRADED / BROKEN) with severity, evidence, a root-cause hypothesis, and a concrete proposed fix (which plugin file/line). THIS is the layer that decides what matters: the collector captures every anomaly signal however minor ...Votes: 0GitHub stars: 2
- Vc Docs[VC Knowledge] Documentation lookup via VirtoOZ MCP (primary) or Context7 (fallback): architecture, modules, APIs, deployment, B2B.Votes: 0GitHub stars: 2
- Qa Hotfix[QA Methodology] Release a hotfix of an already-merged-and-released fix into the stable bundles the operator names, as patch releases cut from support/<X.Y> branches. Use when asked to 'выпустить хотфикс для релиза' / release a hotfix, backport a fix to a stable bundle, or cut a patch on a support line. Not for finding bundles that miss a patch (/qa-bundle-check) or delivering a released hotfix onto environments (/qa-hotfix-check). Gated writes; never auto-merges.Votes: 0GitHub stars: 2
- Qa Hotfix Check[QA Methodology] DELIVER an already-released hotfix onto the deployed vcptcore-stable + vcptcore-regression environments (bump the module/Platform version in vc-deploy-dev's backend/packages.json, commit \"VCST-XXXX: title\"), WAIT for the deploy to land (deploy Action green → /api/platform/modules reports the new version), VERIFY the fix works live, comment on the JIRA task, transition the per-env subtasks (Check on regression/stable) + the parent to Done (live transition discovery, never Ca...Votes: 0GitHub stars: 2
- Qa Evidence[QA Method] Evidence capture & report formatting: screenshot rules, 3-tier verbosity, output paths.Votes: 0GitHub stars: 2
- Watch PrWatch the current branch's PR — reply to and resolve review threads, fix failing checks, and optionally merge when readyVotes: 0GitHub stars: 178
- Triage IssuesReview and assess every issue in the TMDb project board's Backlog column — re-verify each against current main with a read-only fan-out, close the mechanically dead, promote the actionable to Ready with priority, size and execution order, and leave the rest in Backlog naming the decision they need. Use to groom the backlog, before planning a release, or on a schedule. Runs headless: it decides for itself within the rules below.Votes: 0GitHub stars: 178
- TestRun all TMDb unit tests (Swift Testing, the TMDb test plan). Use after code changes and before a PR to verify unit tests pass — delegates the run to the tooling-runner agent (Haiku) and returns total/passed/failed counts plus each failure as Suite/test with file:line. For the live-API suite, use /integration-test.Votes: 0GitHub stars: 178
- Review Pr ThreadsResolve the currently-unresolved review threads on the current branch's PR in one sweep — assess each, fix it (test-first, verified) or reply-only, then reply and resolve — and return a summary. Use standalone to address PR review feedback, or as the thread-handling step invoked by /watch-pr. Repo is adamayoung/TMDb.Votes: 0GitHub stars: 178
- Review PlanAdversarially review the current implementation plan with three independent critic subagents, reconcile their findings into a consensus, and apply the agreed feedback to the plan. Use after drafting a plan (in plan mode or a plan/design doc) and before starting implementation, or whenever the user asks to pressure-test, critique, or harden a plan.Votes: 0GitHub stars: 178
- Review KnowledgeAudit the knowledge/ base and the .claude/ skills, agents and workflows for staleness, self-contradiction, and drift from their own stated rules — four independent adversarial auditors (two lenses over two trees) verify every load-bearing claim against the current tree, cross-examine each other within their tree, and reach a consensus on if/what needs changing. Use periodically, after a run of deliveries that changed build config, target layout or the skills themselves, or whenever you suspec...Votes: 0GitHub stars: 178