project-setup
Skill1 starsChanged 11 months agoMITView on GitHub
Project initialization and setup patterns. Use when starting new projects, setting up development environments, or configuring tooling.
- Reads credentials
- Installs packages
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 37 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when initializing new projects or setting up development environments.
“Common” is measured: kept by at least 6 in 10 of the 37 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
Project Setup
Use this skill when initializing new projects or setting up development environments.
Node.js/TypeScript Project
Initialize
mkdir my-project && cd my-project
npm init -y
npm install typescript @types/node -D
npx tsc --initRecommended Dependencies
# TypeScript essentials
npm install -D typescript @types/node ts-node
# Linting & Formatting
npm install -D eslint prettier @typescript-eslint/parser @typescript-eslint/eslint-plugin
# Testing
npm install -D jest @types/jest ts-jest
# Environment
npm install dotenvPackage.json Scripts
{
"scripts": {
"dev": "ts-node src/index.ts",
"build": "tsc",
"start": "node dist/index.js",
"test": "jest",
"lint": "eslint src --ext .ts",
"format": "prettier --write src/**/*.ts"
}
}Folder Structure
my-project/
├── src/
│ ├── index.ts
│ ├── routes/
│ ├── services/
│ ├── models/
│ └── utils/
├── tests/
├── .env.example
├── .gitignore
├── package.json
├── tsconfig.json
└── README.mdPython Project
Initialize
mkdir my-project && cd my-project
python -m venv venv
source venv/bin/activate # or venv\Scripts\activate on Windows
pip install --upgrade pipProject Structure
my-project/
├── src/
│ └── my_project/
│ ├── __init__.py
│ └── main.py
├── tests/
│ └── test_main.py
├── .env.example
├── .gitignore
├── requirements.txt
├── requirements-dev.txt
├── pyproject.toml
└── README.mdRequirements Files
# requirements.txt
fastapi>=0.100.0
uvicorn>=0.23.0
pydantic>=2.0.0
# requirements-dev.txt
-r requirements.txt
pytest>=7.0.0
black>=23.0.0
mypy>=1.0.0
ruff>=0.0.280Essential Config Files
.gitignore
# Dependencies
node_modules/
venv/
__pycache__/
# Build
dist/
build/
*.pyc
# Environment
.env
.env.local
# IDE
.vscode/
.idea/
# OS
.DS_Store
Thumbs.db
# Logs
*.log.env.example
# Database
DATABASE_URL=postgres://user:pass@localhost:5432/dbname
# API Keys
API_KEY=your-api-key-here
# App Config
PORT=3000
NODE_ENV=developmentESLint (.eslintrc.js)
module.exports = {
parser: '@typescript-eslint/parser',
extends: [
'eslint:recommended',
'plugin:@typescript-eslint/recommended'
],
rules: {
'@typescript-eslint/explicit-function-return-type': 'off',
'@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }]
}
};Prettier (.prettierrc)
{
"semi": true,
"singleQuote": true,
"tabWidth": 2,
"trailingComma": "es5",
"printWidth": 100
}TypeScript (tsconfig.json)
{
"compilerOptions": {
"target": "ES2022",
"module": "NodeNext",
"moduleResolution": "NodeNext",
"strict": true,
"esModuleInterop": true,
"skipLibCheck": true,
"outDir": "./dist",
"rootDir": "./src"
},
"include": ["src/**/*"],
"exclude": ["node_modules", "dist"]
}README Template
# Project Name
Brief description.
## Prerequisites
- Node.js 20+
- PostgreSQL 15+
## Installation
\`\`\`bash
npm install
cp .env.example .env
\`\`\`
## Development
\`\`\`bash
npm run dev
\`\`\`
## Testing
\`\`\`bash
npm test
\`\`\`
## License
MITSetup Checklist
- Initialize version control (git init)
- Create .gitignore
- Set up package manager
- Configure linting/formatting
- Set up testing framework
- Create environment template
- Write README with setup instructions
- Add CI/CD configuration
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- karrioapi/karrio★ 799same name
- haowjy/creative-writing-skills★ 555same name
- Resgrid/Core★ 235same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- fltman/project-scaffolder★ 88same name
- markshust/hcf★ 79same name
- dleerdefi/claude-code-construction★ 53same name
- vaayne/agent-kit★ 53same name
- wolverin0/claude-skills★ 41same name
34 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.
Used alongsideProjects with it also use creative-writing-craft, creative-writing-muse and 9 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.
Abdullokh-NSkillcreative-writing-craft
Справочник ремесла: проза, сцена, стиль, голос. Загружать, когда нужно знание "как писать", а не режим производства.
Also in 3 projects that use this
Abdullokh-NSkillcreative-writing-muse
Точка входа в набор скилов для длинной прозы. Включается, когда автор просит спланировать, написать, продолжить, переписать или разобрать художественный текст — роман, повесть, цикл рассказов. Ведёт маршрут от замысла к готовому куску и держит базу знаний проекта.
Also in 3 projects that use this
badgidsSkillcharacter-sim
Pressure-test a character by speaking or reasoning strictly from that character's current voice, goals, relationships, emotional pressure, and knowledge boundary without creating canon by accident.
Also in 3 projects that use this
jpsweeney97Skillwriting-principles
Enforces writing principles for instruction documents (SKILL.md, skill supporting files, subagents, CLAUDE.md). Use when writing, reviewing, or editing any file in **/skills/**/*.md, **/agents/*.md, or **/CLAUDE.md. Triggers on skill creation, skill file updates, CLAUDE.md changes, subagent authoring, or instruction document review.
Also in 3 projects that use this
ItsSidharthaSkillstory-planning
Collaborative planning skill for a GitHub issue. Takes issue content and codebase context as input. Runs an iterative clarification loop until the user explicitly agrees to a plan, then saves it to docs/<story_number>/plan.md. Used by the user-story-implementation skill — load this skill at the start of Phase 1 and follow it completely before returning to the orchestrator.
Also in 3 projects that use this
badgidsSkillstory-review
Diagnose existing prose at a chosen editorial level, from whole-story and developmental problems through scene, line, copy, and proof passes, without rewriting until the diagnosis is accepted.
Also in 3 projects that use this
- +4 more from Abdullokh-N
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- api-integrationSkill
- authenticationSkill
- caching-strategiesSkill
- ci-cd-pipelinesSkill
- clean-architectureSkill
- code-patternsSkill
- database-designSkill
- docker-composeSkill
- error-handlingSkill
- frontend-designSkill
- git-workflowSkill
- logging-monitoringSkill
- microservicesSkill
- performance-tuningSkill
- security-best-practicesSkill
- systematic-debuggingSkill
- tddSkill
- testing-strategiesSkill
- websockets-realtimeSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

