SkillFoxx

claude_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

  • 35 ★ on the repository
  • Last commit
Workflow

Extended access

Why this level

  • The 1c-developer subagent writes and changes BSL code per project standards without a separate confirmation for every file
  • The rlm-tools-bsl MCP server runs code in a Python sandbox to explore the configuration
All reasons and checks
Russian stack

dach-coin/claude_rules_1cAuthor:Dach-Coin

Install

Works in

In your terminal, with SkillFoxx CLI

npx skillfoxx add workflows/claude-rules-1c

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The 1c-developer subagent writes and changes BSL code per project standards without a separate confirmation for every file
  • The rlm-tools-bsl MCP server runs code in a Python sandbox to explore the configuration

This is third-party code. Review the repository files before installing.

What it does

The repository is copied into the root of a 1C project and adds 12 specialized Claude Code subagents (developer, architect, code and architecture reviewer, analyst, planner, tester, doc writer, metadata manager, performance optimizer, refactoring, quick error fixer), three layers of rules (auto-core loaded every session, profile-based rules chosen per task, and path-scoped rules for form modules) and a skill set imported wholesale from cc-1c-skills. A PowerShell SessionStart hook injects the profile catalog into the session context. The project wires up three external MCP servers: rlm-tools-bsl for code exploration through a Python sandbox, 1c-syntax-mcp for platform reference, and bsl-language-server for BSL diagnostics. Project parameters (prefix, company, platform version) and the infobase registry live in uncommitted .dev.env and .v8-project.json files.

Who it is for. For teams of 1C developers who want one shared set of Claude Code roles and rules for the whole project, rather than each developer's own personal setup.

Good fit when

  • A team works in Claude Code on a 1C project and wants shared rules and subagents for everyone
  • You need different rule profiles for different task classes (forms, SKD, integrations and others)
  • You already use or are ready to connect rlm-tools-bsl, 1c-syntax-mcp and bsl-language-server

Not a fit when

  • You do not use Claude Code: the rules and subagents are specific to it
  • You are not ready to connect three separate MCP servers that some capabilities depend on
  • You need a minimal setup without 12 roles and a three-layer rule system

Example request

Use the 1c-code-reviewer subagent and check my changes to the form module for anti-patterns and standards compliance

Limitations

The skills are borrowed wholesale from cc-1c-skills with no own logic changes beyond path parameterization and a metadata knowledge map. Full functionality depends on three external MCP servers that must be installed separately. The README explicitly lists what the stack does not cover: semantic search over BSP, natural-language metadata search, automatic performance analysis and more.

How to disable. Remove the .claude folder, the CLAUDE.md and rus_CLAUDE.md files from the project, and remove the MCP entries from .mcp.json.

FAQ

Do you have to pick a rule profile manually?

Not necessarily; if no profile is set, the agent suggests 1-3 options after the first prompt and loads the files on confirmation.

Where are a developer's personal settings stored?

In .dev.env, .v8-project.json and .claude/profile.local.json, all three excluded from git.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A Claude Code starter template for 1C: 16 skills, 6 role subagents and a protocol for checking against a live base via MCP

WorkflowExtended access22
Russian stack

Rules, subagents, skills and MCP integrations for 1C:Enterprise 8 development with Cursor, Claude Code, Codex and other agents

PluginBroad access539
Russian stack

A set of skills, rules and MCP servers for 1C Enterprise 8.3 development where the agent works from real code and docs, not from memory

SkillBroad access35

1C AI development environment

1C AI Development Environment

Russian stack

1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C

MCP serverBroad access18
Russian stack

A large set of skills, rules and commands that let an agent build and parse 1C sources in the platform's format, without the Designer

SkillExtended access93
Russian stack

A Claude Code plugin with an MCP server of 1C development rules, where every rule names its source bug and how it is checked

PluginExtended access2

README in short

The README describes in detail the .claude directory structure (agents, rules, lib, skills), step-by-step installation and a table of what goes into the project's git versus stays local, the three external MCP servers and their purpose plus the boundaries of what the stack does not cover, tables of the 12 subagents by group with their models, the three-layer rule system, SDD framework integrations, and the skills' origin in cc-1c-skills.

README badge

Report a problem