SkillFoxx

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

  • 16 ★ on the repository
  • Last commit
  • MIT
Prompt

Extended access

Why this level

  • Clones and installs external skills and rules repositories during initialization
  • The prompt gives the agent access to 1C database connection parameters, including the password
All reasons and checks
Russian stack

sheverdinp/cc-1c-initAuthor:sheverdinp

Install

Manual install

Text for your agent

Выполни инструкции из promt_new_project.md

Copy the prompt into the project root before running it.

Access and checks

How we review

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

  • Clones and installs external skills and rules repositories during initialization
  • The prompt gives the agent access to 1C database connection parameters, including the password

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

What it does

The promt_new_project.md prompt sets up a full 1C project structure in an empty folder in one run: folders for configuration snapshots, tasks, a knowledge base, a sandbox and scripts, a CLAUDE.md file with filesystem and database boundaries, and a .dev.env template for connection parameters. It clones and installs the external cc-1c-skills skills and cursor_rules_1c rules, converting the latter from Cursor format to Claude Code format, and adds 12 role agents such as analyst, architect and reviewer. A second prompt, patch_codex.md, ports the already set up project to Codex: config, skills, rules and a check script, without touching the user's global settings. Separate targeted patches exist for projects already set up by an earlier version.

Who it is for. For 1C developers starting a new project with Claude Code or Codex who want a standard structure and agent safety rules from day one, without manual setup.

Good fit when

  • You are starting a new 1C project and want structure, coding standards and agent boundaries from the start
  • You need predefined roles (analyst, architect, reviewer) for different tasks
  • You want to work in both Claude Code and Codex with the same setup

Not a fit when

  • The project already has an established structure you do not want to change
  • You do not use Claude Code or Codex

Example request

Follow the instructions in promt_new_project.md and set up a new 1C project structure

Limitations

The prompt clones the external cc-1c-skills and cursor_rules_1c repositories from the internet during setup; their content is not controlled by the cc-1c-init author. Writing to a production infobase is forbidden by the CLAUDE.md rules, but that is an instruction to the agent, not a technical restriction. The database password ends up in a local .dev.env that must be manually excluded from git.

How to disable. Remove the .claude/skills folder, the kb/1c-rules folder and the CLAUDE.md file the prompt created from the project.

FAQ

Does the prompt only work with Claude Code?

The main prompt does, and patch_codex.md separately ports the same setup to Codex.

What happens to the database password?

It goes into a local .dev.env, which is listed in .gitignore and should not be committed.

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

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

SkillExtended access2

1C project template with rules and MCP

Шаблон проекта 1С (1c-rules + Platform Tools)

Russian stack

A portable starter for a new 1C:Enterprise project in Cursor, with 1c-rules, an OpenSpec skeleton, and updates via the /updaterules command

WorkflowMinimal access

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

README in short

The README describes the directory structure the prompt creates, key files like CLAUDE.md and .dev.env.example, the agent's filesystem and database boundaries, the list of external dependencies (cc-1c-skills, cursor_rules_1c), the order of running the two prompts, and 12 role agents with a purpose table. It also covers targeted patches for already set-up projects and tooling update scripts.

README badge

Report a problem