initialize-project
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Initialize a new project from the TypeScript template by renaming packages, updating metadata, and cleaning up documentation. Use when starting a new project, "bootstrapping" from this template, or setting up a fresh repository.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- zdnemz/claude-teamtheir own version, first seen Jul 5, 2026
- yu-iskw/skill-inspectorword for word, first seen Jan 23, 2026
Other versions2 projects use a version of this.
Word for word · 1
- yu-iskw/skill-inspector★ 2100% same
Edited · 0
None found.
Wrote their own version · 1
- zdnemz/claude-team★ 1same name
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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- build-and-fixSkill
- bumpup-versionsSkill
- clean-projectSkill
- fix-issueSkill
- improve-claude-configSkill
- lint-and-fixSkill
- manage-adrSkill
- manage-changelogSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- setup-dev-envSkill
- sync-readmeSkill
- test-and-fixSkill
- test-integration-dockerSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Gather Information: Ask the user for:
- Very specific: line 23
Update README Placeholders: Use the StrReplace tool to replace the placeholders in README.md with the gathered information:
- Very specific: line 27
Install Dependencies: Run pnpm install to update the lockfile with the new package names.
- Distinctive: line 28
Final Cleanup: Remove the initialization skill and its related files once bootstrapping is complete, if requested by the user.
- Very specific: line 38
Update package.json with the new metadata.
- Very specific: line 39
Use StrReplace on README.md to swap {PROJECT_NAME}, {PROJECT_DESCRIPTION}, and {LICENSE} with the actual values.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Initialize Project
Purpose
This skill automates the initial setup of a new project derived from this template. It leverages AI capabilities to directly modify project metadata and documentation by replacing placeholders, ensuring a clean start for a new repository.
Instructions
- Gather Information: Ask the user for:
- New project name (e.g.,
my-awesome-app) - Project description
- Author name
- (Optional) GitHub repository URL
- New project name (e.g.,
- Update Project Metadata: Directly update the following files using the
WriteorStrReplacetools:package.json: Updatename,description, andauthor.packages/common/package.json: Update the package name to match the new scope (e.g.,@new-name/common)..trunk/trunk.yaml: If there are template-specific references, update them.
- Update README Placeholders: Use the
StrReplacetool to replace the placeholders inREADME.mdwith the gathered information:{PROJECT_NAME}-> New project name{PROJECT_DESCRIPTION}-> Project description{LICENSE}->ISC(or other preferred license)
- Install Dependencies: Run
pnpm installto update the lockfile with the new package names. - Final Cleanup: Remove the initialization skill and its related files once bootstrapping is complete, if requested by the user.
Examples
Example 1: Initializing a new CLI tool
Input: User says "Initialize this project as 'json-fixer', a CLI tool to fix broken JSON files." Action:
- Gather details from the user (Name: json-fixer, Description: A CLI tool to fix broken JSON files, Author: [Author Name]).
- Update
package.jsonwith the new metadata. - Use
StrReplaceonREADME.mdto swap{PROJECT_NAME},{PROJECT_DESCRIPTION}, and{LICENSE}with the actual values. - Run
pnpm install.
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.

