Init Project
SkillAI & modelsInitialize Claude Code configuration for a new project. Triggered when the user says "初始化项目", "init project", or "配置 Claude Code".
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Init Project skill
What this skill tells your AI
The instructions your AI receives, as published by jiahao-shao1/sjh-skills in skills/init-project/SKILL.md and read by ahel’s review.
Automatically configure Claude Code best practices for new projects: directory skeleton, general-purpose agents, hooks, and AGENTS.md (with CLAUDE.md as a thin @AGENTS.md stub).
Execution Flow
-
Phase 1: Generate Skeleton (deterministic script) → Run
scripts/init-skeleton.shto create directory structure + boilerplate files → Output which files were created -
Phase 2: Interactive AGENTS.md Fill (LLM + AskUserQuestion) → Process
<!-- init-project: 待填充 -->placeholders section by section → For each section: read codebase → generate draft → AskUserQuestion to confirm → write → User can reply "skip" to skip any section → CLAUDE.md is just a stub (@AGENTS.md+ write-routing rule); never edited in Phase 2 → Detailed guide templates indetails/agents-md-sections.md -
Phase 3: Profile Overlay (optional) → AskUserQuestion: "Want to overlay an additional profile? Currently supported: research" → If research selected → run
scripts/init-research-profile.sh→ Profile details indetails/research-profile.md -
Output Summary → List all generated/modified files → Suggest next steps: review content, git add, start developing
Phase 2 Section Processing Strategy
| Section | Auto-exploration | User prompt |
|---|---|---|
| Project overview | Read README, pyproject.toml, package.json | "One-line description of this project's core goal?" |
| Models / Key dependencies | Detect imports, API keys, model configs | "What models or external services does this project depend on?" |
| Directory structure | ls + read key file docstrings | "Does this directory layout look correct? Anything to adjust?" |
| Dev workflow | Detect CI, Makefile, scripts/ | "Use the default brainstorming→plans→dev→verify flow?" |
| Dev guide | Detect venv, .env, Dockerfile | "Any special environment setup steps?" |
| Context Loading (routing table) | List .claude/rules/*.md + scan opening summaries | "Confirm (task domain → rule) mapping — entry point for Codex / external agents" |
| Always Do (project-specific) | Read rules/, lint config | "Any cross-module consistency requirements?" |
| Ask First | Scan core files (interfaces, config) | "Which files/dirs require confirmation before modifying?" |
| Never Do | Detect third_party/, .env | "Any absolute don't-touch conventions?" |
| Progressive disclosure setup | Scan docs/knowledge/ + .claude/rules/ | Ensure rules reference knowledge files inline; ask about missing refs |
Constraints
- Idempotent: existing files are never overwritten, only gaps are filled
- No auto git add/commit: user decides when to commit
- No existing content modification: only
<!-- init-project: 待填充 -->placeholders are touched - Scripts run standalone:
init-skeleton.shandinit-research-profile.shwork independently of the skill
References
- Skeleton file manifest:
details/skeleton-manifest.md - AGENTS.md section guide:
details/agents-md-sections.md - Agent templates:
details/agent-templates.md - Research profile:
details/research-profile.md
Signals
- GitHub stars
- 38
- Forks
- 1
- Last commit
- Sep 2026
ahel review
K6low
bundled executables the agent is told to runK1binfo
installs-packages (in scripts/init-research-profile.sh)K1binfo
installs-packages (in README.md)K1binfo
installs-packages (in README.zh-CN.md)K1binfo
installs-packages (in details/research-profile.md)
Automated review, not a security audit. Ruleset v1+k2.
Advanced
- Item type
- skill
- Key
init-project-jiahao-shao1- Source
- github.com/jiahao-shao1/sjh-skills