Fullstack Search Development Standards

This skill configures Aider to follow specific development conventions and quality standards for fullstack search applications, with automatic linting on every change.

What This Skill Does

Instructions

When working on this fullstack search project:

1. **Read and internalize conventions**: Always reference the conventions defined in `prompts/conventions.md` before making changes. These conventions are critical to maintaining codebase consistency.

2. **Follow the linting workflow**:

- After making any code changes, the lint script `./scripts/aider-lint.sh` will automatically run

- If linting fails, fix all reported issues before proceeding

- Do not bypass or ignore linting errors

- Common checks include TypeScript type errors, ESLint violations, and project-specific rules

3. **Commit control**:

- Auto-commits are disabled, so you control when changes are committed

- Review all changes thoroughly before committing

- Ensure linting passes before making commits

4. **Code quality standards**:

- Write type-safe TypeScript code

- Follow ESLint rules defined in the project

- Adhere to conventions in `prompts/conventions.md`

- Maintain consistency with existing codebase patterns

5. **Model usage**:

- Use Claude Sonnet 4.5 (anthropic/claude-sonnet-4-5-20250929) for all code generation

- This model provides optimal balance of quality and performance for fullstack development

Example Usage

When asked to add a new search feature:

1. First, review `prompts/conventions.md` to understand naming conventions, file structure, and coding patterns

2. Implement the feature following those conventions

3. Wait for `./scripts/aider-lint.sh` to run automatically

4. Fix any linting errors that appear

5. Once linting passes, review the changes

6. Commit manually when satisfied

Important Notes