init-project
Skill43 starsChanged 7 months agoMITView on GitHub
初始化新项目的 Claude Code 配置。用户说"初始化项目"、"init project"、"配置 Claude Code"时触发。
- Reads credentials
53 other projects use a version of this.
Adopted by
Most recently taken up by
- morochena/skillstheir own version, first seen Nov 15, 2026
- kratocz/skillstheir own version, first seen Nov 15, 2026
- upamune/skillstheir own version, first seen Nov 15, 2026
- vlad-ryzhkov/ai-context-engineering-for-frontendtheir own version, first seen Nov 15, 2026
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 15, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 15, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions53 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 53
- southliu/south-admin-react★ 582same name
- wataru-maeda/react-native-boilerplate★ 521same name
- flonat/flonat-research★ 150same name
- huangwb8/skills★ 50same name
- eugenelim/agent-ready-repo★ 31same name
- freemty/labmate★ 25same name
- ice-lfernandes/claude-spring-architect★ 11same name
- nerviz-ai/nerviz★ 11same name
- eranw2000/multi-phase-skills-framework★ 10same name
- luiseiman/dotforge★ 8same name
43 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bibtex-fetchSkill
- context-auditSkill
- daily-summarySkill
- experiment-registrySkill
- handoffSkill
- notion-lifeosSkill
- paper-analyzerSkill
- paper-self-reviewSkill
- project-reviewSkill
- remote-cluster-agentSkill
- research-leadSkill
- session-teamSkill
- sync-docsSkill
- team-digestSkill
- web-fetcherSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 51
No existing content modification: only <!-- init-project: 待填充 --> placeholders are touched
“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Init Project
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

