AgentSkillsCN

aico-backend-init

通过模板创建约束文档，从而初始化后端环境。 当满足以下条件时，可使用此技能： - 执行 /backend.init 命令； - 用户要求“初始化后端”、“搭建后端环境”； - 开始后端工作，需要确立技术栈与规范； - 需要创建 docs/reference/backend/constraints.md。

SKILL.md
--- frontmatter
name: aico-backend-init
description: |
  Initialize backend environment by creating constraints document from template.

  Use this skill when:
  - Running /backend.init command
  - User asks to "initialize backend", "setup backend environment"
  - Starting backend work and need to establish tech stack and conventions
  - Need to create docs/reference/backend/constraints.md

Backend Init

Initialize backend development environment by creating the constraints file.

Language Configuration

Before generating any content, check aico.json in project root for language field to determine the output language. If not set, default to English.

Process

  1. •Check existing: Look for docs/reference/backend/constraints.md
  2. •If exists: Ask user if they want to overwrite or skip
  3. •Create directory structure:
    code
    docs/reference/backend/
├── constraints.md
└── tasks/
  4. •Generate constraints file:
    • •Read template from references/constraints.template.md
    • •Guide user through key decisions
  5. •Save output: Write to docs/reference/backend/constraints.md

Document Header Format

All generated documents MUST use this unified header format:

markdown
# [Document Title]

> Project: [project-name]
> Created: YYYY-MM-DD
> Last Updated: YYYY-MM-DD

Guided Questions

CategoryQuestions
Language/RuntimeNode.js, Python, Go, Rust?
FrameworkExpress, Fastify, FastAPI, Gin?
DatabasePostgreSQL, MySQL, MongoDB?
ORM/QueryPrisma, Drizzle, SQLAlchemy, GORM?
TestingVitest, Jest, Pytest, Go test?
API StyleREST, GraphQL, gRPC?

Template

See references/constraints.template.md for the full constraints template.

Output

code
✓ Created docs/reference/backend/constraints.md
✓ Created docs/reference/backend/tasks/
✓ Backend environment initialized

Key Rules

  • •ALWAYS use the unified header format
  • •MUST guide user through tech stack questions
  • •ALWAYS create tasks/ directory
  • •ALWAYS save to docs/reference/backend/constraints.md