1c-devtools-cursor

Integrates 1C:Enterprise 8 configuration, extension, and debugging workflows into Cursor.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/Aradotso/devtools-skills --skill 1c-devtools-cursor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-devtools-cursor
Source: https://github.com/Aradotso/devtools-skills/tree/main/skills/1c-devtools-cursor
Command: npx skills add https://github.com/Aradotso/devtools-skills --skill 1c-devtools-cursor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing a 1C:Enterprise 8 development workflow across Configurator, exports/imports, extensions, and debugging is slow and error-prone when you have to juggle many tools and file formats outside your editor.

Core Features & Use Cases

  • Command palette workflow for 1C Dev: Exposes common 1C operations in Cursor through a dedicated panel and command palette so you can stay in one place.
  • Project configuration & connection setup: Uses an env.json file to define database, v8 platform paths, locale/language, and debug server settings for repeatable launches.
  • Source-based load/export (incremental updates): Supports loading and exporting configurations and extensions from src/cf and src/cfe, including incremental updates driven by build/commit/Commit.txt.
  • Extension and external artifact handling: Helps build/disassemble external reports and processors and manage packagedef dependencies.
  • BSL debugging support: Provides a debugger attachment workflow (including server management expectations like dbgs.exe) plus variable inspection and call stack navigation.

Quick Start

Create a Cursor project folder with a packagedef file in the root, add an env.json with your --ibconnection and --v8-platform-root, then use the command palette to run “1C: Launch with background jobs” and debug your BSL with breakpoints.

Frequently Asked Questions about 1c-devtools-cursor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug 1C BSL code inside Cursor?

Debugging 1C BSL code inside Cursor requires configuring debug server host and port settings in an env.json file, then launching background jobs to set breakpoints, inspect variables, and navigate the call stack.

How do I set up a 1C:Enterprise 8 project for Cursor development?

Setting up a 1C:Enterprise 8 project requires creating a project folder with a packagedef file in the root and configuring an env.json file with your --ibconnection and --v8-platform-root parameters for repeatable launches.

Can I perform incremental updates when exporting 1C configurations?

Yes, you can perform incremental updates when exporting 1C configurations by loading and exporting sources from the src/cf and src/cfe directories, driven by the build/commit/Commit.txt file.

Does 1C DevTools in Cursor support building external reports and processors?

Yes, Cursor-based 1C DevTools supports building and disassembling external reports and processors, while also managing your packagedef dependencies for extension builds.

Do I need OneScript to run 1C operations in Cursor?

Yes, OneScript execution is expected for operational commands, as the workflow integrates infobase, configuration, and extension operations directly into the Cursor environment.

Why are my 1C configuration loading commands not working in Cursor?

1C configuration loading commands may fail if your project lacks a packagedef-activated layout or a properly configured env.json file defining database, v8 platform paths, locale, and debug server settings.