init-project

Name: init-project
Author: neuromechanist

37stars7forks

How to install init-project?

neuromechanist/research-skills/init-project

$npx -y skills add neuromechanist/research-skills --skill init-project

Installs into the current project.

Summary

Use this skill for \"initialize project\", \"set up project\", \"scaffold project\", \"create AGENTS.md\", \"create CLAUDE.md\", \"set up rules\", \"create context directory\", \"vibe rules\", \"project templates\", \"init new project\", \"set up development structure\", \"create

Files · 1

View on GitHub

SKILL.md

1	# Project Initialization with Vibe Rules Templates
2
3	Initialize new projects with a structured development environment for Codex, Claude Code, Copilot, and optionally Cursor. The templates enforce consistent development practices: real testing (no mocks), atomic commits, documentation-driven development, and continuous rule improvement.
4
5	## When to Use
6
7	- Starting a new project from scratch
8	- Adding cross-agent structure to an existing project
9	- Setting up .rules/ and .context/ directories for a project that lacks them
10	- Migrating a project to vibe-rules conventions
11
12	Partial-init detection: if AGENTS.md or .rules/ already exists, this is not a
13	fresh init. Inventory what exists first; scaffold only the missing pieces
14	(never overwrite an existing AGENTS.md or customized rule), and use the
15	update-rules skill instead when the ask is to refresh existing files against
16	newer templates. For understanding an existing codebase before documenting
17	it, run codebase-onboarding first and reuse its report for the architecture
18	map in Step 4.
19
20	## Template Structure
21
22	The plugin bundles all templates under `templates/`:
23
24	```
25	templates/
26	agents/ # Shared agent templates
27	AGENTS.md # Main cross-agent instructions file
28	claude/ # Claude Code adapter templates
29	CLAUDE.md # Imports AGENTS.md, then holds Claude-only guidance
30	rules/ # Detailed rule references
31	testing.md # NO MOCK testing policy
32	git.md # Version control standards
33	python.md # Python/UV standards
34	code_review.md # PR review toolkit
35	documentation.md # MkDocs standards
36	ci_cd.md # GitHub Actions setup
37	self_improve.md # Rule evolution
38	serena_mcp.md # Code intelligence tools
39	context/ # Documentation scaffolding
40	plan.md # Task tracking with phases
41	ideas.md # Design concepts
42	research.md # Technical explorations
43	scratch_history.md # Failed attempts and lessons
44	decisions/ # Architecture Decision Records
45	README.md # ADR convention (numbering, statuses, when to write one)
46	0000-template.md # Template for new ADRs (do not edit)
47	config/ # Development configuration
48	pre-commit # Ruff pre-commit hook (Python)
49	pyproject.toml # Python project config
50	pytest.ini # Pytest config
51	mkdocs.yml # Documentation config
52	gitignore-template # Common ignores
53	github/ # CI/CD templates
54	workflows/
55	test.yml # Test pipeline
56	docs.yml # Documentation deployment
57	release.yml # Release automation
58	cursor/ # Cursor IDE templates (optional)
59	.cursorrules # Main cursor config
60	core_rules/ # Modular .mdc rule files
61	planning/
62	default/ # Plan-based development workflow
63	advanced-taskmaster/ # Complex project task management
64	```
65
66	## Initialization Workflow
67
68	### Step 1: Detect project type
69
70	Scan the current directory for language markers:
71	- `pyproject.toml`, `requirements.txt`, `setup.py` -> Python project
72	- `package.json` -> Node.js/JavaScript/TypeScript project
73	- `Cargo.toml` -> Rust project
74	- `go.mod` -> Go project
75
76	### Step 2: Copy core templates
77
78	Copy with safety checks (never overwrite existing files):
79	1. AGENTS.md from `templates/agents/AGENTS.md`
80	2. CLAUDE.md from `templates/claude/CLAUDE.md` (contains `@AGENTS.md`, then Claude-only guidance)
81	3. .rules/ from `templates/claude/rules/` (all .md files)
82	4. .context/ from `templates/context/` (plan, ideas, research, scratch_history)
83	5. .context/decisions/ from `templates/context/decisions/` (ADR template and README). Created separately so existing projects that already have `.context/` still pick it up on re-run.
84
85	### Step 3: Language-specific setup
86
87	Python projects:
88	- Install pre-commit hook from `templates/config/pre-commit` (runs ruff on staged files)
89	- Reference `templates/config/pyproject.toml` and `templates/config/pytest.ini` for configuration examples
90
91	All projects:
92	- Offer GitHub Actions workflows from `templates/github/workflows/` if `.github/workflows/` does not exist
93
94	### Step 4: Customize AGENTS.md and keep CLAUDE.md as an adapter
95
96	Replace template placeholders with project-specific value

People who liked this also viewed

6 picks

Type

init-project

37stars7forks

View on GitHub

How to install init-project?

neuromechanist/research-skills/init-project

$npx -y skills add neuromechanist/research-skills --skill init-project

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Project Initialization with Vibe Rules Templates
2
3	Initialize new projects with a structured development environment for Codex, Claude Code, Copilot, and optionally Cursor. The templates enforce consistent development practices: real testing (no mocks), atomic commits, documentation-driven development, and continuous rule improvement.
4
5	## When to Use
6
7	- Starting a new project from scratch
8	- Adding cross-agent structure to an existing project
9	- Setting up .rules/ and .context/ directories for a project that lacks them
10	- Migrating a project to vibe-rules conventions
11
12	Partial-init detection: if AGENTS.md or .rules/ already exists, this is not a
13	fresh init. Inventory what exists first; scaffold only the missing pieces
14	(never overwrite an existing AGENTS.md or customized rule), and use the
15	update-rules skill instead when the ask is to refresh existing files against
16	newer templates. For understanding an existing codebase before documenting
17	it, run codebase-onboarding first and reuse its report for the architecture
18	map in Step 4.
19
20	## Template Structure
21
22	The plugin bundles all templates under `templates/`:
23
24	```
25	templates/
26	agents/ # Shared agent templates
27	AGENTS.md # Main cross-agent instructions file
28	claude/ # Claude Code adapter templates
29	CLAUDE.md # Imports AGENTS.md, then holds Claude-only guidance
30	rules/ # Detailed rule references
31	testing.md # NO MOCK testing policy
32	git.md # Version control standards
33	python.md # Python/UV standards
34	code_review.md # PR review toolkit
35	documentation.md # MkDocs standards
36	ci_cd.md # GitHub Actions setup
37	self_improve.md # Rule evolution
38	serena_mcp.md # Code intelligence tools
39	context/ # Documentation scaffolding
40	plan.md # Task tracking with phases
41	ideas.md # Design concepts
42	research.md # Technical explorations
43	scratch_history.md # Failed attempts and lessons
44	decisions/ # Architecture Decision Records
45	README.md # ADR convention (numbering, statuses, when to write one)
46	0000-template.md # Template for new ADRs (do not edit)
47	config/ # Development configuration
48	pre-commit # Ruff pre-commit hook (Python)
49	pyproject.toml # Python project config
50	pytest.ini # Pytest config
51	mkdocs.yml # Documentation config
52	gitignore-template # Common ignores
53	github/ # CI/CD templates
54	workflows/
55	test.yml # Test pipeline
56	docs.yml # Documentation deployment
57	release.yml # Release automation
58	cursor/ # Cursor IDE templates (optional)
59	.cursorrules # Main cursor config
60	core_rules/ # Modular .mdc rule files
61	planning/
62	default/ # Plan-based development workflow
63	advanced-taskmaster/ # Complex project task management
64	```
65
66	## Initialization Workflow
67
68	### Step 1: Detect project type
69
70	Scan the current directory for language markers:
71	- `pyproject.toml`, `requirements.txt`, `setup.py` -> Python project
72	- `package.json` -> Node.js/JavaScript/TypeScript project
73	- `Cargo.toml` -> Rust project
74	- `go.mod` -> Go project
75
76	### Step 2: Copy core templates
77
78	Copy with safety checks (never overwrite existing files):
79	1. AGENTS.md from `templates/agents/AGENTS.md`
80	2. CLAUDE.md from `templates/claude/CLAUDE.md` (contains `@AGENTS.md`, then Claude-only guidance)
81	3. .rules/ from `templates/claude/rules/` (all .md files)
82	4. .context/ from `templates/context/` (plan, ideas, research, scratch_history)
83	5. .context/decisions/ from `templates/context/decisions/` (ADR template and README). Created separately so existing projects that already have `.context/` still pick it up on re-run.
84
85	### Step 3: Language-specific setup
86
87	Python projects:
88	- Install pre-commit hook from `templates/config/pre-commit` (runs ruff on staged files)
89	- Reference `templates/config/pyproject.toml` and `templates/config/pytest.ini` for configuration examples
90
91	All projects:
92	- Offer GitHub Actions workflows from `templates/github/workflows/` if `.github/workflows/` does not exist
93
94	### Step 4: Customize AGENTS.md and keep CLAUDE.md as an adapter
95
96	Replace template placeholders with project-specific value

People who liked this also viewed

6 picks

Type