Minecraft Mod Manager Development Standards

This skill enforces strict development practices for the Minecraft Mod Manager project - a TypeScript CLI tool for managing Minecraft mods from Modrinth and CurseForge.

What This Skill Does

Guides AI agents to follow rigorous development standards including:

Instructions

1. Conventional Commit Messages (MANDATORY)

**ALL commits MUST follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).**

- `feat: add new mod scanning functionality`

- `fix: resolve version check error handling`

- `test: add comprehensive tests for config validation`

- `docs: update README with new installation steps`

**Action**: ALWAYS format commit messages using this specification. Reject any commits that don't follow this format.

2. Continuous Integration Verification (MANDATORY)

**ALWAYS run `pnpm run ci` before completing any changes.**

This command executes:

**Action**: Execute `pnpm run ci` after making changes and before committing. If CI fails, fix all issues before proceeding.

3. Test Coverage Requirements (STRICT)

**100% test coverage is mandatory - no exceptions.**

**Action**: Before implementing any feature:

1. Write tests first (TDD approach preferred)

2. Ensure 100% line, branch, and function coverage

3. If you think a test should be removed, STOP and ask for guidance

4. Code Quality and Architecture

#### File Organization Rules

**CRITICAL**: Respect the architectural separation:

#### Console Output Rules (STRICT)

**Action**: When adding logging:

1. Check file location

2. If in `src/actions/`, use `console.log` or `console.error`

3. If in `src/lib/`, use `Logger` class

4. Never use console methods outside actions

#### Software Hygiene Checklist

5. Dependencies and Package Management

**Action**: When adding dependencies:

1. Verify it's truly needed

2. Use `pnpm add <package>`

3. Document why the dependency is required

6. Linting and Formatting

**Action**:

1. Run `pnpm lint:ci` before committing

2. Fix all linting errors

3. If you don't understand a rule violation, ask for help

7. Documentation Standards

**Action**: For each feature:

1. Update inline code documentation

2. Update README.md if user-facing

3. Create/update ADR if architectural decision made

8. Testing Guidelines

#### Test Structure

#### Test Categories

#### Coverage Requirements

**Action**: When writing tests:

1. Use descriptive test names (e.g., `it('should throw error when config file is missing')`)

2. Test all code paths

3. Use jest-chance for generating varied test data

4. Run `pnpm report` to verify coverage

9. Development Workflow

Follow this workflow strictly:

1. **Before starting**: Run `pnpm ci` to ensure baseline passes

2. **Write tests first**: Follow TDD principles where possible

3. **Implement changes**: Make minimal, focused changes

4. **Verify continuously**: Run `pnpm ci` frequently during development

5. **Commit with conventional messages**: Follow commit format strictly

6. **Final verification**: Ensure `pnpm ci` passes before submitting

10. Project-Specific Context

#### Minecraft Mod Management Features

#### Configuration Files

#### External APIs

11. Quality Gates (Pre-Commit Checklist)

Before creating any pull request:

12. When In Doubt

**DO NOT make assumptions or guess.** Instead:

1. Research the existing codebase for similar patterns

2. Check the ADR documentation in `doc/adr/`

3. Review the README.md and CONTRIBUTING.md

4. Ask for clarification from the team

**Never make things up or implement solutions without understanding requirements.**

Example Workflow

```bash

1. Ensure baseline passes

pnpm ci

2. Create feature branch

git checkout -b feat/add-mod-search

3. Write tests first

Edit test file in __tests__/

4. Run tests (should fail)

pnpm test

5. Implement feature

Edit source files

6. Verify continuously

pnpm ci

7. Commit with conventional format

git add .

git commit -m "feat: add mod search functionality"

8. Final verification

pnpm ci

9. Push and create PR

git push origin feat/add-mod-search

```

Important Reminders

These are requirements, not suggestions. Adherence is mandatory for all contributions.