1C AI DevStart workflow
A Claude Code starter template for 1C: 16 skills, 6 role subagents and a protocol for checking against a live base via MCP
- 22 ★ on the repository
- Last commit
Extended access
Why this level
- Batch scripts can export and import the configuration through the real Configurator
- Agent permissions are configured by the user and cautious by default, but can be widened to direct writes to source files
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add workflows/1c-ai-devstartDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Batch scripts can export and import the configuration through the real Configurator
- Agent permissions are configured by the user and cautious by default, but can be widened to direct writes to source files
This is third-party code. Review the repository files before installing.
What it does
The template is copied into a 1C project and set up with a /setup-project command that connects to the database and MCP, exports source files, fills in the CLAUDE.md project passport, and configures agent permissions (what it can change on its own, what needs an explicit request, what is read-only). It provides 16 skills covering topics like queries, SKD reports, managed forms, object lifecycle, EnterpriseData exchanges and batch Configurator operations, plus 6 narrow role subagents: architect, code explorer, developer, reviewer, simplifier, documenter. The key principle: coding rules live in one 1c-rules.md file, and the agent pulls metadata and data from a live base through the third-party 1c_mcp MCP server by Vladimir Kharin, rather than guessing from memory. A /1c-feature-dev command drives the full task cycle, while /new-brief plus /new-plan cover simpler tasks.
Who it is for. For Windows-based 1C developers who want a systematic Claude Code framework instead of a pile of disconnected prompts.
Good fit when
- You are starting a 1C project with Claude Code and want ready roles, skills and rules from the start
- You need explicit control over the agent's permissions for each source folder
- You are ready to connect the 1c_mcp MCP server to your base for checking against real metadata
Not a fit when
- You do not have Windows or PowerShell: the template's batch scripts are built for them
- You do not use Claude Code
- You need tools for directly editing XML metadata structure: the template deliberately leaves those out
Example request
Run /1c-feature-dev to add a service desk API integration and take the task through the review and simplification subagentsLimitations
There is no license file in the repository. Full functionality requires installing the third-party 1c_mcp MCP server by Vladimir Kharin into the infobase and publishing its HTTP service; without it the agent loses access to metadata and data. Batch export and import of the configuration go through the real Configurator and can take noticeable time on large bases. The template has no tools for editing XML metadata structure directly, recommending the separate cc-1c-skills project for that.
How to disable. Remove the .claude folder and the CLAUDE.md file from the project, along with entries in .mcp.json if MCP servers were connected.
FAQ
Does the template work without MCP?
Yes, but the agent relies only on source files and honestly flags that it could not check against the live base.
How do you update the template in an existing project?
Copy the .claude folder over your own, leaving CLAUDE.md, .mcp.json and other already configured root files untouched.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsclaude_rules_1c: Claude Code rules and agents for 1C
claude_rules_1c
A set of 12 subagents, profile-based rules and MCP configuration for 1C development in Claude Code, with a three-layer rule loading system
1C AI Development Kit: 1C skill collection
1C AI Development Kit
A set of 52 Claude Code skills and agents, plus Cursor rules, for the full 1C:Enterprise 8.3 development cycle, assembled from several community projects
A kit of skills, agents and rules for 1C development in Claude Code and Cursor: metadata, forms, DCS, extensions, infobases and web client
1C AI development environment
1C AI Development Environment
1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C
A Copier project template for 1C with a bundle of SKILL.md files for Claude Code and Codex: dump, load, tests and extension builds via stable scripts
cc-1c-init: 1C project init prompt
cc-1c-init
A Claude Code prompt that sets up a 1C project structure with coding standards, role agents, skills and MCP
README in short
The README describes the template's features (BSL norms, MCP as source of truth, 16 skills, 6 subagents, permission control, batch operations), a step-by-step quick start via /setup-project, updating the template, working on tasks in full and light cycles, tables of all skills and subagents, the WHAT/HOW separation principle, the connected MCP servers (1c_mcp and v8std), and credits to the source projects: 1c_mcp, v8std.ru and 1c-ai-feature-dev-workflow.