From sjh-skills
Initializes Claude Code for new projects: runs skeleton script for directories/boilerplate, interactively generates AGENTS.md sections via user prompts, optional research profile. Triggered by 'init project'.
npx claudepluginhub jiahao-shao1/sjh-skills --plugin sjh-skillsThis skill uses the workspace's default tool permissions.
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).
Guides project setup through 6 phases: detects tech stack from package.json/requirements.txt/etc., creates CLAUDE.md, configures MCP memory and auto-loop hooks. For new/existing Claude Code projects.
Generates Claude Code project setups including CLAUDE.md, hooks, permissions, commands, and agents. Analyzes stack (TypeScript, JavaScript, Python, Go, Rust, etc.) to create minimal/standard/full configs.
Bootstraps new projects from scratch: gathers requirements for frontend SPAs, full-stack apps, APIs, CLI tools, libraries; researches latest best practices via WebSearch; creates blueprint; confirms; initializes with official CLI; sets up Claude Code agent system.
Share bugs, ideas, or general feedback.
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).
Phase 1: Generate Skeleton (deterministic script)
→ Run scripts/init-skeleton.sh to 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 in details/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 in details/research-profile.md
Output Summary → List all generated/modified files → Suggest next steps: review content, git add, start developing
| 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?" |
| 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 |
<!-- init-project: 待填充 --> placeholders are touchedinit-skeleton.sh and init-research-profile.sh work independently of the skilldetails/skeleton-manifest.mddetails/agents-md-sections.mddetails/agent-templates.mddetails/research-profile.md