1C project template with rules and MCP
Шаблон проекта 1С (1c-rules + Platform Tools)
A portable starter for a new 1C:Enterprise project in Cursor, with 1c-rules, an OpenSpec skeleton, and updates via the /updaterules command
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- The template itself is just project structure and rules, performing no operations on a production infobase
- The MCP helper and DEV server need their own separately configured 1C infobase access
Install
Manual install
git clone https://github.com/mikhailchuklay/1c-project-template.git my-1c-projectClones the template under the new project's name, then configure per TEMPLATE.md.
This is third-party code. Review the repository files before installing.
What it does
The template gives a ready starter for a new 1C:Enterprise development project with an AI agent in Cursor: rules, skills, agents and slash commands built on 1c-rules with extensions, an OpenSpec skeleton, a standalone DEV server, and an MCP helper. It separately bundles OneMCP for 1c-data-mcp with a ready .cfe extension and an XML for development tools. The key idea: the /updaterules command runs tools/update-from-template.ps1 to pull rule updates into clones already created from the template, using this repository as the source of truth. The configuration sources themselves, secrets and the project's memory files are not part of the template and are created fresh in every clone.
Who it is for. For 1C developers on Cursor starting a new project who want configured rules, skills and MCP from day one instead of assembling the environment from scratch.
Good fit when
- You are starting a new 1C project and want a ready rule and skill set for Cursor
- You need a single source of rules that can be pulled into several projects via /updaterules
- You want a ready OpenSpec skeleton and MCP helper without configuring from scratch
Not a fit when
- The project already has its own setup and switching to someone else's rule template is not worth it
- Cursor is not your main development environment
Example request
Update the project's rules from the template with /updaterules and show what changedLimitations
Direct pushes to master are allowed only for the repository owner; changes go through a pull request from a fork or a feature branch. Platform Tools skills are installed as a separate VS Code or Cursor extension, not part of the template itself. Secrets like .dev.env and env.json are explicitly excluded from the template and created fresh in every project.
How to disable. Remove the .cursor, openspec and tools folders from the project if the rules and MCP helper are no longer needed.
Security check
- The template itself is just project structure and rules, performing no operations on a production infobase
- The MCP helper and DEV server need their own separately configured 1C infobase access
README in short
The README describes a portable 1C project starter built on 1c-rules with extensions, explains the pull-request change model, and lists the contents: rules, skills, agents and slash commands, an OpenSpec skeleton, vanessa-bootstrap tooling, a standalone DEV server, an MCP helper, and OneMCP for 1c-data-mcp. It separately states what is not included: configuration sources, secrets, and Platform Tools skills.
FAQ
How do I update the rules in an already created project?
The /updaterules command runs tools/update-from-template.ps1, which pulls the current rules from this repository.
Are the configuration sources part of the template?
No, src/cf and src/cfe start empty and are exported from your infobase separately.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything