Guides through standardized project initialization following team conventions
Guides developers through creating standardized project structures with essential configuration files, testing frameworks, and CI/CD pipelines. Use this when starting new projects to ensure consistent team conventions and best practices.
/plugin marketplace add natifridman/claude-plugins/plugin install project-setup-standards@team-standards-marketplaceYou are helping set up a new project following our team's standardized conventions. Guide the developer through the following setup steps:
Create a well-organized project structure based on the project type:
project-name/
├── src/
│ ├── api/
│ ├── services/
│ ├── models/
│ ├── utils/
│ └── config/
├── tests/
│ ├── unit/
│ └── integration/
├── docs/
├── .github/
│ └── workflows/
├── .gitignore
├── README.md
├── package.json (or equivalent)
└── .env.example
project-name/
├── src/
│ ├── components/
│ ├── pages/
│ ├── hooks/
│ ├── utils/
│ ├── styles/
│ └── assets/
├── tests/
├── public/
├── docs/
├── .github/
│ └── workflows/
├── .gitignore
├── README.md
├── package.json
└── .env.example
Include standard ignores for:
# Project Name
## Description
Brief description of what this project does
## Prerequisites
- List required software/tools
- Minimum versions
## Installation
Step-by-step installation instructions
## Usage
How to run the project
## Testing
How to run tests
## Contributing
Link to contribution guidelines
## License
License information
npm init or yarn initstart, dev, build, test, lintSet up the following tools:
Initialize testing framework:
Create .github/workflows/ci.yml with:
Example workflow:
name: CI
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Setup
uses: actions/setup-node@v3
with:
node-version: '18'
- run: npm ci
- run: npm test
- run: npm run lint
Create .env.example with:
Set up:
Apply team-specific standards:
.github/pull_request_template.mdAfter gathering project requirements, guide the developer through each applicable section, creating necessary files and configurations. Explain the reasoning behind each standard to promote understanding.